[MacPerl-Porters] "adapting" MakeMaker

[Matthew Langford <langfml [at] eng [dot] auburn [dot] edu>]

I'd like to automate some pieces of a non-MPW module build process (eg,
the test dirs and possibly running tests).  The Makefile.PL seems to come
up over and over.  I started rooting around, looking at MakeMaker.pm, and
then found MM_MacOS.pm, which seems to be the perfect place to make my
changes.

However, MM_MacOS.pm probably works just fine for MPW-ers.  Is there some
way to determine if it is running under MPW?  An environment variable,
perhaps?  If so, we could switch implementations accordingly.

Now, someone will surely ask the obvious:  what good is a Makefile without
a make command or even a command-line environment?  Well, the plan is to
approximate the Mac MakeMaker's approximation of a real Makefile.  (say
that three times real fast!)  Instead of commands, perhaps I can use
AppleScript.  If that doesn't work, I could emit Perl (and use AppleEvents
inside this) code, and use a separate runtime executable of Perl (call it
CodeWarriorBuilder) for that code.

In this manner, I can approximate forking off processes for the special
case of only two simultaneous processes--which is all we need.  Let them
call exit(); we don't need no steenking fork!  :)

Any thoughts?


--
MattLangford 


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