mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-03-03 07:01:19 +00:00
8d8b8115f8
Build system developers commonly need to see what changes have on the generated build files. We often put our objdir under version control and diff commits before and after running config.status. This patch adds a --diff option to config.status that will print diffs of changes made during config.status. This functionality is implemented on top of FileAvoidWrite, using Python's built-in diffing library. While display of diffs is opt-in, diffs are always being captured when config.status runs. There could be an unwanted performance regression from this. Because diffs are only computed if files change and most files don't change during most config.status runs, this greatly reduces the surface area of the concern. The area for largest concern is clobber builds. On my machine, I measured an increase of 0.2 to 0.3s from 2.0s. While this is 10-15%, the total time is so small that I don't feel snaking a "capture diff" flag through the build system is worth the effort. This would make a decent followup bug if this turns out to be a problem in the future. I also snuck in a change to reindent all-tests.json because displaying diffs for this massive 11MB all-in-one-line JSON file results in an extremely large string being printed to my terminal. --HG-- extra : rebase_source : c0f7ff69cad282e63a050e67f156dbe96b49a142
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
http://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/