Chris Melville wrote:
>
[snip]
> I ended up doing it by writing an NMAKE wrapper (which knew which files were
> required for each executable from a single "database") and a single master
> make file (which knew how to build every possible type of thing given a
> specification of the source files and a few options). Each subsystem
> (executable) then had a tiny little makefile saying what type of thing it
> was and which source files were in it, and including the main makefile (not
> even any nmake spawns). The order of susbsystem definitions in the
> "database" was also the required order for building them all, so my wrapper
> just stepped through them one by one in the right order. Net result - a very
> nice simple build and config mgmt system, even if the master makefile was
> hellishly hard to understand.
>
> Maybe something similar would work for Mozilla
NO GOD NO!!!!! autoconf it all and let sh sort 'em out!
> (there is an open source
> NMAKE, no?), but I'm not familiar enough with the non-WIN32 tools to be able
> to do it alone.
>
> > sure that it wouldn't take too much work to make minimal requirements be
> > Visual C++ and Cygwin (you'd need to disable JAR
>
> Why would Cygwin still be needed ?
>
Cygwin gets you all the GNU build tools, in particular make, automake,
autoconf, etc, not to forget gcc. I'd bet a small sum that at this
point you could even dispense with VC++ and use gcc/mingw instead.
But only a small sum ;-).
> Cheers,
> Chris
> >
