Re: moz-modular - splitting the tree

Enrico Weigelt wrote:
> * Benjamin Smedberg <[email protected]> schrieb:
> 
>> What do you mean by "doesn't get compiled"? The mozilla tree is compiled 
> 
> Dozens of missing include files, missing makefiles, etc.
> 
> The whole build structure is too complicated for someone who didn't 
> spend several month of deeply hacking in it, to look throught.

If you are building with the autoconf+makefile build system that mozilla 
uses, you shouldn't be having any problems. I don't understand what you mean 
in general: are you trying to build mozilla (minimo/etc) itself, or are you 
trying to compile additional code on top of mozilla?

In most cases missing include files are simply a matter of setting REQUIRES 
correctly in your makefile (and building in the correct tier).

> I have to go that way, even if it means, going alone.

This is a very bad, even stupid idea. There are hundreds or thousands of 
volunteer hackers who build the Mozilla products on a regular basis, and 
help fix bugs and test. "Going your own way" is a recipe for poor quality, 
and unless you have a large team of highly qualified programmers there is 
not a chance that you could keep up with merging all of the bugfixes from 
the Mozilla codebase.

Why don't you actually propose a solution that solves whatever modularity 
issues you see (which you haven't identified yet!) and still allows you to 
benefit from the large and diverse community that already exists around the 
codebase?

As owner of the Mozilla build system, I urge you to deal with small 
incremental improvements to the existing code, instead of dooming yourself 
to futility by attempting to fix everything at once in a forked codebase.

--BDS