[Date Prev][Date Next][Thread Prev][Thread Next]
[Search]
[Date Index]
[Thread Index]
macperl-porters-digest V1 #7
macperl-porters-digest Friday, March 19 1999 Volume 01 : Number 007
Re: [MacPerl-Porters] Configure.mpw
Re: [MacPerl-Porters] Configure.mpw
----------------------------------------------------------------------
Date: Fri, 19 Mar 1999 00:03:29 -0800 (PST)
From: Peter Prymmer <pvhp@best.com>
Subject: Re: [MacPerl-Porters] Configure.mpw
On 19 Mar 1999, Matthias Neeracher wrote:
> In article <v04020a12b316dcf66a64@[192.168.0.77]>, Chris Nandor <pudge@pobox.com> writes:
>
> > There is a chance that the build process could be moved over to Metrowerks.
> > I dunno.
>
> I'm sort of torn up over this decision. There are two camps, both of which have
> a plausible claim that moving things their way would simplify the build
> process:
>
> a) There are those who would like to streamline the existing makefile
> infrastructure, and Peter's Configure.mpw work would certainly fit
> in well there.
> b) OTOH, there is the idea of moving to a CodeWarrior IDE based build,
> which is becoming more attractive with the forthcoming XML infrastructure
> for CW Project files and with the improved support for Perl in CW.
For me the most complicated aspect of the build process is assembling the
ingredients. Once they are all there they can pretty much do whatever
they need to automatically.
There is also the "Perl is free, hence should be built with free
tools" aspect of the argument (especially if SC and/or MrC could be
adopted to the task of building perl). On the other hand I
certainly would not mind seeing a good IDE and XML working on
something like this. I don't actually have a strong opinion either way.
I am more interested in making the build process smooth, easy and hopefully
somewhat familiar to folks from other platforms (in this regard take
a look at the "Ask Tim" section at www.ora.com where Tim O'Reilly is
being pummelled with requests for Mac books, including specific
requests for MPW books).
Bear in mind that as a first step something like Configure.mpw is really
only to help out with crossing T's and dotting I's: in particular making
sure that headers, libraries, and compilers are in place. As a
practical matter I'd personally like it too if the configuration and build
on many different platforms was as uniform as possible. Toward that end I
have made the GUI portions of Configure.mpw sort of optional. I think
that the script is a good bit more text based than perhaps it needs to be
to merely work on the Mac, but that was a nod toward the informative
feedback that the Bourne shell version gives (I think Larry Wall has
written on the psychological aspects of running that script).
On specific matters: should sfio be built before perl? BTW what is the
:qnx: folder doing in the MacPerl_Src:macperl: folder anyway (the ar
script uses a tool called `wlib` and the cpp uses `cc`)?
Thanks.
Peter Prymmer
==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-porters-request@macperl.org
------------------------------
Date: Fri, 19 Mar 1999 06:12:07 -0400 (AST)
From: Arved Sandstrom <Arved_37@chebucto.ns.ca>
Subject: Re: [MacPerl-Porters] Configure.mpw
On 19 Mar 1999, Matthias Neeracher wrote:
> In article <Pine.GSO.3.95.iB1.0.990318083430.19354B-100000@halifax.chebucto.ns.ca>, Arved Sandstrom <Arved_37@chebucto.ns.ca> writes:
>
> > 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.
>
> Last time I looked, GUSI was totally incompatible with Apple's MPW
> compilers (in particular SC, I don't think I've looked at MrC). I'd like
> for GUSI 2 to be SC & MrC compatible, though.
>
It would be a nice thing. :-) Me, personally, I'm keeping up with
Codewarrior, but I just _like_ the idea of having a free build process for
MacPerl, and for XS, to go along with the fact that MP is free. Rounds
everything out.
So GUSI is the hitch, is it? Mind you, you say that you looked at SC, not
MrC. Our (Alan Fry and myself) initial evaluation of XS with Apple MPW has
led us to believe that MrC is more or less straightforward - we have
numerous working builds including some MacPerl extensions - but SC is
posing some problems (linking stage). But I think they'll get ironed out.
In any case, my point is that looking at SC first may give a bad
impression. :-)
Are you currently doing GUSI 2 with some kind of intent that it might be
MrC (and SC) buildable? If I can be of any assistance in running some
tests or checking things out, just ask.
Arved
==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-porters-request@macperl.org
------------------------------
End of macperl-porters-digest V1 #7
***********************************
==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe"
==== to macperl-porters-digest-request@macperl.org