[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

Re: [MacPerl-Porters] Configure.mpw



In article <199903180724.XAA10127@shell8.ba.best.com>, Peter Prymmer <pvhp@best.com> writes:
> While I have not yet built MacPerl from source yet (actually I don't
> have a copy of MWC :-) I have been going over the build instructions 
> more closely than ever before.

Cool!

> One thing odd that I noted was the
> admonishment on MPP&E to name one's MPW_Shell directory :MPW:

Well, does anybody ever name it differently? :-)

I've never tested with any other name, but offhand I can't recall any
hardcoded references to it anyway.

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

> 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, I'm surprised that you would have the *time* in your budget for such an
enterprise :-) The task seems potentially extremely useful, but doing it in
MPW shell language seems a very difficult way of accomplishing it. On the
other hand, MPW might not be all that much worse than /bin/sh, except that it
doesn't support any here documents.

> So I am curious: where will the Mac specific files wind up in the perl tar ball?
> Will there be a folder :mac: (er, mac/)?

Yes, that's the plan.

> PerlStub         (136k stub lib???)

Sounds about right. It exports more than 100 symbols for 2 different
architectures.

> Does that list look about right?  Would it be OK to assume that a Configure script
> would need to Move or Duplicate those files from the :mac: directory into the
> main perl5.005_5n build directory prior to the build?

That question is not quite settled yet, but it sounds like a reasonable plan.

> While I haven't diffed things yet, some files will obviously need patching in 
> the main perl5* directory (e.g. run.c).

All the Mac specific parts are already conditionalized on "macintosh".

> Also, is it reasonable to assume that the stuff in :MacPerl_Src:macperl: will
> still be distributed separately from the perl tar ball?

Yes, and so will the contents of ext/

Matthias

-- 
Matthias Neeracher   <neeri@iis.ee.ethz.ch>   http://www.iis.ee.ethz.ch/~neeri
  "And that's why I am going to turn this world upside down, and make
   of it a fire so *bright* that someone real will notice"
                                -- Vernor Vinge, _Tatja Grimm's World_

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