On 23.07.2017 01:19, Gregory Szorc wrote:
Yes, the build system is complex. It has evolved organically for over 20 years, accumulating tons of cruft and complexity along the way. Much of the existing complexity can be simplified.
Yeah, I'm already trying some experiments here. IMHO, the underlying problem is the lack of an strict moduarity (lots of interdependencies between different areas - media stuff is one example).
Kbuild is not a viable long-term solution because it is tied to Make,
Sorry, I was a bit imprecise. I'm thinking of Kconfig. And this is quite independent of the actual build system. OTOH, even for large project I'm usually fine w/ plain (g)make. But my projects tend to be strictly modularized, and I take care that they don't grow so huge in the first place. I believe, we could reduce the (actually used) mozilla source size radically and make things much easier. There's a also lot that wouldn't like to have in the browser itself, but entirely separate programs. Well, that's another story ... By the way: I've read some rumors that the whole b2g stuff is going to be dropped - is that correct ?
Bazel is one such modern tool.
hmm, according to the intro, looks pretty much like something I did over 15 years ago (it was called "treebuild", as it modeled the whole project in a tree structure) ... suggested it to several large projects like moz, ooffice, etc - the reaction were, hmm, not entirely friendly. By the way: xorg/xf86 used to have similar problems (anyone still remembers xmkmf ? *brrrr*), but due to modularization, things became quite simple today (okay, Xserver itself is still ugly, but's a whole story of its own :o). That's the way I would like to go. --mtx _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
