Closed Bug 58372 Opened 19 years ago Closed 18 years ago
[META] Overview of build system changes
I'm opening this meta bug to deal with the general issue of overhauling the build system. I'd like to actively move to a more modular and user friendly build system.
Adding bug dependencies for: 46775 - Building a statically linked build 56601 - Creating a real install target 53727 - Setting soversions on components 57282 - Selectively building components 58376 - Separating end-user builds from maintainer builds
This bug is mainly for a gathering of thoughts and to keep track of the essential changes needed before the build system is acceptible for casual user use. Some of the changes are specific to the build system, others will require non-trival changes to the codebase to make the idea work. Consider it a "rtm" list from the build maintainers perspective.
Can you describe your goal more detailed? 'More user friendly' is nice, but what do you mean? With "more modular", you man that it is possible to use stable components for all of Mozilla *but* the components you are hacking on? E.g. I develop on Mailnews or rdf and use the trunk only for them and milsltone sources (or even binaries) for all other components? That would rock, and eliminate many problems we have. (BTW: Judging from the FAQ, StarOffice seems to do the same, but I havn't checked out the source yet.)
huh? I thought, my last comment was the first right after the inital description!?! Maybe bugzilla got confused about the time change (summer->winter). Thanks for the deps, though.
Adding dependency: 18352 - Make extensions/ optional
Depends on: 18352
Adding dependency: 87771 - single pass build
Depends on: 87771
this bug doesn't seem to concern any particular embedding customers. minusing to topembed- and adding embed as per edt triage.
Missed the boat. Quite pathetic.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.