Confirmed users
177
edits
DevTools/Hacking: Difference between revisions
→Incremental Builds
(Update build section (no more /* needed)) |
|||
| Line 56: | Line 56: | ||
Once you've already built Firefox once, and you just want to incrementally update your build with your latest DevTools changes, you can run: | Once you've already built Firefox once, and you just want to incrementally update your build with your latest DevTools changes, you can run: | ||
$ ./mach build | $ ./mach build faster | ||
which is much faster than your first build or clobber builds and should only take a few seconds. You can run your build the same way you did before: | which is much faster than your first build or clobber builds and should only take a few seconds. You can run your build the same way you did before: | ||
$ ./mach run -P development | $ ./mach run -P development | ||
If you happen to change any C++ files (which is pretty rare when working on DevTools), you may need a different command for incremental builds: | |||
$ ./mach build binaries | |||
A full `mach build` will work for any type of change, it just takes longer to run than the incremental options above. | |||
Note that whenever you pull the latest changes from <tt>fx-team</tt> into your local repository, you may need to "clobber". A "clobber" is similar to a "<tt>make clean</tt>". You'll know you need to clobber when you get a big error message telling you to do a clobber build after you tried to do an incremental build. To do a clobber build, enter these commands: | Note that whenever you pull the latest changes from <tt>fx-team</tt> into your local repository, you may need to "clobber". A "clobber" is similar to a "<tt>make clean</tt>". You'll know you need to clobber when you get a big error message telling you to do a clobber build after you tried to do an incremental build. To do a clobber build, enter these commands: | ||