Re: [MacPerl-Porters] Configure.mpw

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

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.

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.

> more closely than ever before.  One thing odd that I noted was the
> admonishment on MPP&E to name one's MPW_Shell directory :MPW: since
> the build scripts expect this (step 3 on pg 329).  I have gone over some (not all)
> things and e.g. :MacPerl_Src:perl:BuildRules.mk seems to mention 
> things relative to $(MPW).  My (limited :-) understanding of the default 
> setup of the shell is that {MPW} is set to {Shelldirectory}
> and that neither need be explicitly expanded.  So is the book wrong
> or have I simply failed to find the explcit dependency on path naming convention?
> (I realize that *if* I had a working compoiler I could simply test this
> with a build - alas my budget for such things is somewhat limited :-).
> 

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.

> At any rate I have started working on a Mac port of Configure that I am
> calling Configure.mpw (for lack of a better name) that checks the MANIFEST
> file and the build environment for necessary MPW tools, libs, headers, etc.
> Though I note that Tcl is setup to build using Applescripts it seemed
> advantageous to write Perl's Mac script in MPW - does that sound reasonable?
> 
Well, you could just write it in Perl... :-)

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...)

Arved



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