Confirm
431
edits
Changes
→Incremental Builds
Some of these unit tests can be expensive and are disabled by default.
== Incremental Builds Optimizing build time == Electrolysis requires libxul, which means any changes you make while developing require rebuilding libxul, which can be quite slow. If you're on Linux and ld takes enough memory (it needs 2 GB+) while linking libxul to cause swapping on your machine, consider adding the following to your mozconfig file (you will also need to rerun configure, which may require deleting '$SRCDIR/configure' and/or $OBJDIR/config.cache): export LDFLAGS="-Wl,--no-keep-memory" You may also be able to avoid doing a full, top-level make by building only certain directories:
If you have made any changes to any protocol files (*.ipdl), then you must run
make -C [BLD_DIR]/dom/ipc
You'll need to rebuild in any directories that have other .ipdl files you've modified, too. Finally, since e10s requires libxul, you must re-build rebuild libxul each time you compile (at least if you want your changes to actually show up in the browser :). You do this by running
make -C [BLD_DIR]/toolkit/library
The libxul build takes by far the longest of these three, so I just dump all three commands (plus a make for whatever directory I'm working in) in a script and run it each time to rebuild. Sometimes it doesn't work :(
Consider building on a faster machine if linking libxul is slowing your productivity. Some of us are allegedly on boxes where it takes only around 5 seconds...
