On 9/4/2014 2:47 PM, Nathan Froyd wrote:
I have been poking at the build system a bit for the last couple of weeks and
feel like I am running out of ideas of things that could be (usefully) fixed.
What are some of the moderately-sized (~1-2 week-ish) things that need doing in
the build system?[1] My perception is that there are many great things that
could be done (some large, some small), but those things have either been
discussed and not written down, or have had bugs filed, but with not enough
context to make them actionable. If that is the state of things, I would like
to change it; if that is not the state of things, please correct me!
Things that I would like to see, in no particular order:
1. A unified toolkit package manifest that is included by the Firefox,
B2G, Fennec, Thunderbird, SeaMonkey, etc. manifest. I've started on this
at least twice, but trying to sort out how much of diffs are due to bad
handling of multiple copies pisses me off and makes me do something else
on my todo list.
2. Anything that helps mach compilation-database. For example, getting
CPPSRCS to be a frozen makefile variable.
3. Cleanups and consolidation in the moz.build fronted/backend logic. I
know Mike Hommey has said he's already working on fixing the sources mess.
4. FINAL_TARGET_FILES moz.build migration. I think that's the single
biggest set of things still in Makefile.in that's relatively easy to port...
5. PREF_JS_EXPORTS as well.
--
Joshua Cranmer
Thunderbird and DXR developer
Source code archæologist
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
