[MacPerl] MacPerl Binary Builds, and Ports

[Arved Sandstrom <Arved_37@chebucto.ns.ca>]

Howdy, all

I figured I'd throw in some of my own Rah-Rah-Rah here. Chris Nandor has
done a yeoman job of getting an easy-to-use interface up and running at

http://pudge.net/mmp

Please use it. :-) This page is meant for the MacPerl community at large.
It's not just for actual porters or builders of binaries (note the
difference). The MMP page (the above URL) is your fast, compact,
one-stop-shopping resource for finding out what modules have been ported
and/or built as binaries, for downloading the same, for being directed to
other sources of information, and for registering your requests to at
least have something looked at.

As the MMP page says, most CPAN modules run under MacOS to start with.
Chris has made scripts available to simplify all or parts of the process
of getting things from CPAN. Iff (the mathematical 'if and only if') you
do get a CPAN module, and it doesn't work, here's what to do:

(1) Is the module a problem because there's XS code involved (look for
files of type .xs and/or .c)? And you've got no compiler, etc etc. 
SOLUTION: Go to the MMP page. See if the module has been built as a
binary. If it hasn't, let us know - check the baby in. Checking in a
module doesn't mean that you now have to build and/or port it. It means
that you want *someone* to take a look at it.

(2) Does the module just plain not work? And there's no XS code?
SOLUTION: check to make sure that it's a real porting problem. That is,
the module may have prerequisites - make sure you've got 'em. If you're
covered at your end, go to MMP (your one-stop resource... :-)) Is it
listed there as a port? No? Follow the link to CPAN-testers: see if the
module has been tested under MacOS, and if it worked. If neither, same
deal as above - check the sucker in. this will let us know that the thing
probably needs porting, and there's a good chance it will be looked at.

We can always use more porters and builders. For that matter, since the
first step is testing, we can use CPAN testers... :-) (I feel guilty
bringing this one up - I can't do it myself because I've got my hands full
about 3 times over). If you're handy with Perl and comfortable with Macs,
you can port modules that need it with the best of them.

Building binaries is different. There may be zero porting involved when
building an XS or SWIG-based binary for MacPerl, but you do need
Codewarrior and/or MPW. There have been a number of posts regarding using
available compilers to build XS, and if you were actually able to follow
those and get stuff built, you're well on your way, and we can certainly
use your help. I anticipate having comprehensive POD/HTML docs available
well before the end of March, which discuss using Codewarrior + MPW, just
MPW, and the CW IDE to build XS extensions for MacPerl. Stay tuned.

Finally, if you're really interested in this stuff, consider subscribing
to the macperl-modules or macperl-porters lists. I'm posting this here in
the main MacPerl M.L. for wide coverage, but most of the issues get hashed
out in the other lists. See you there! :-)

Arved Sandstrom



===== Want to unsubscribe from this list?
===== Send mail with body "unsubscribe" to macperl-request@macperl.org