New directory structure and build system
The mozilla project has produced a set of stable top-level libraries that are used by many outside projects, and its is time for its directory structure and build system to evolve to match this reality. In particular, the Gecko Runtime Engine (GRE) is being embedded in multiple projects but it is still inexplicably necessary to build SeaMonkey (its main embedder) to get the GRE.
We propose to create a set of top-level directories that represent first-order libraries (like gre). /mozilla becomes a sort of hosting directory, and the top-level libraries each have their own make systems (most of which would use our current autoconf build system) instead of having a top-level make that makes multiple libraries at once.
Unfortunately the drivers said "it's not worth the effort."... Damn!
Those changes are definitely needed. I'm not a developer but even I can figure out the benefits of this.Comment by Chris Gonyea at July 26, 2003 07:12 AM | Permalink
Do I understand correctly that this is the way for multiple applications to take advantage of the GRE without having to install a duplicate? Isn't this the point of having the GRE?!Comment by Mark at July 26, 2003 07:38 AM | Permalink
I found an interesting read about why not to use recursive make! Many projects like Mozilla, OpenOffice,... would definitely benefit from faster and cleaner building.Comment by Rene at July 31, 2003 08:38 AM | Permalink
I can appreciate that. It's the same sort of concept gambling online as in recording, when a mistake, or an incidental, gambling can sometimes be noticed and played up in the mix online poker to great effect. I'll attest to all of the above poker room from experience. I can think of another particularly web casino helpful exercise, though I wasn't aware of it at casino the time: I was, some years back, even MORE hypercritical internet poker of my own writing and composing than I am now, and video pokerComment by slot at May 16, 2004 07:09 AM | Permalink