Re: [MacPerl-Porters] Configure.mpw

[Peter Prymmer <pvhp@best.com>]

On Thu, 18 Mar 1999, Arved Sandstrom wrote:

> On Wed, 17 Mar 1999, Peter Prymmer wrote:
> 
> > While I have not yet built MacPerl from source yet (actually I don't
> > have a copy of MWC :-)
> 
> I have reason to believe that you are as likely to be able to build
> MacPerl with MrC under Apple MPW (all free) as you are with CW Pro 3 or 4.

Interesting.  I was wondering what prevented the use of MrC or SC.
Of course the build*.mk files would need tweaking (yet another job
for the Makefile extraction process of Configure.mpw :-)
 
> For anyone interested in doing XS stuff, and potentially being able to
> build MP also, I recommend getting Apple MPW. The XS process certainly
> works, with tweaks. Alan Fry has been doing most of the "proof of concept"
> work with MrC, and when we come out with the MacPerl XS tutorial, using
> Apple MPW will be in it.

Cool.
 
> Well, $(MPW) is a dmake variable, and {MPW} is the Shell variable. By the
> time you finish setting up Codewarrior MPW, {MPW} is properly set, but
> that doesn't mean that $(MPW) is.
> 
> As you say, the first build you ever do with any of the BuildRules stuff
> will show you whether or not your paths are OK, and they're easy fixes.

OK.  It turns out it is also an easy thing to check for from within
an MPW script such as Configure.mpw.  I guess I'll put it in on a
condition that will make it easy to override.

> Well, you could just write it in Perl... :-)

Nah.  It is interesting to see how different shells handle the stuff 
that Configure does.  I suppose Applescript would have been more "native"
but MPW is impressive, and a requisite for the build.  Of course it helps
matters quite a bit that it's freely downloadable.  I've stumbled across
several "missing tool" problems that I now check for in Configure.mpw.
 
> As far as the rest of the post, I'd be as interested as you are in finding
> out how a MacPerl upgrade to 5.005 is coming along. If I download one more
> module that I can't use because it's using qr, or things like that, I
> won't be held accountable. :-) (Things aren't so bad - I get my 5.005
> jollies over on MkLinux...)

Well I was not trying to push things.  Actually I thought that 5.006 would
be the great Mac integration release.

Peter Prymmer
 


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