[MacPerl] All-in-one project file

[pudge@pobox.com (Chris Nandor)]

>Path:
server1.news.adelphia.net!router1.news.adelphia.net!remarQ-easT!supernews.com!news.maxwell.syr.edu!newspeer1.nac.net!netnews.com!news-stl.cp.verio.net!news-tpk.cp.verio.net!news.sdsmt.edu!secnews.netscape.com!not-for-mail
>From: Pierre Saslawsky <pierre@netscape.com>
>Newsgroups: netscape.public.mozilla.mac
>Subject: All-in-one project file
>Date: Wed, 27 Jan 1999 23:59:53 -0800
>Organization: Netscape Bazaar
>Lines: 56
>Message-ID: <36B018F2.E3A639FA@netscape.com>
>NNTP-Posting-Host: h-208-12-42-84.netscape.com
>Mime-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>X-Mailer: Mozilla 4.5 (Macintosh; I; PPC)
>X-Accept-Language: fr,   English,   en
>Xref: router1.news.adelphia.net netscape.public.mozilla.mac:310
>
>
>Luigi Lira gave me a copy of his all-in-one project file: a build system
>entirely based on CodeWarrior, without MacPerl nor MANIFEST files.
>
>It rocks. All the projects are accessible from the same window, it scans them
>all at a glance when you modify a header file and especially, it compiles
>almost twice as fast (17 minutes vs. 31 minutes on a G3/300).
>
>Two weeks ago, when Luigi first mentionned that he wanted to work on such a
>solution, Simon rose 2 concerns. Luigi's answers are:
>
>-----
>> Historically, we have had files with duplicate names in the tree;
>> this is probably still true (especially as there might be separate
>> Mac and Windows implementations of the same class in files of
>> the same name).
>
>Only PUBLIC headers need to have unique file names. The rest of the files can
>have duplicated names. 
>
>> Another problem with access paths pointing to the root of the mozilla
>> tree is that it makes opening and building projects extremely slow.
>
>It was slow only because CodeWarrior had to resolve all the aliases. If we
>don't use aliases and set the user access path of all the projects to the
>Mozilla folder, CodeWarrior uses the volume index to find the files and it
>goes fast.
>------
>
>
>Pros:
>- Fast, simple and very convenient for us.
>- Much easier and compelling for people who are getting on board, or for
>those who are just having a look on Mozilla.
>- XP guys no longer have to add and update MANIFEST files.
>- We avoid using a system based on MacPerl that only a few people understand
>and that could never be made stable enough (the script can't be interrupted
>and Tinderbox hangs regularly, especially the Depend one).
>
>Cons:
>- All public header files MUST have a unique name in the repository,
>otherwise we have to deal with access paths to resolve the conflicts (see
>details in a following message).
>- We still need a bit of a script (AppleScript?) for the resources files
>(Luigi suggests that we check them in under "dist/res" but it doesn't sound
>like a good idea). 
>
>Comments? Cheers?
>
>A following post contains the integrality of Luigi's notes.
>
>Pierre
>
>-- 
>Pierre Saslawsky <pierre@netscape.com>
>"Gecko, not Geeko."

***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch