Rebuilding Specific Parts
If you have made many changes, but only want to rebuild specific parts, you may run the following commands.
C or C++ Files:
./mach build binaries
复制代码
JavaScript or XUL Files (Windows Only):
./mach build path/to/dir
复制代码
Replace path/to/dir with the directory with the files changed.
This is the tricky bit since you need to specify the directory that installs the files, which may be a parent directory of the changed file's directory. For example, to just rebuild the Lightning calendar extension:
In general, change into your objdir, change down to the specific directory where you want to build (the directory structure of the objdir matches the structure of the source dirs), and type just "make" (or "gmake" if necessary). This only works if you find a directory that contains a "Makefile" (the equivalent directory in the source tree will contain a "Makefile.in"). If you want to get even more specific than that, you can try "make <filename>.obj".
If you have changed code of Gecko, e.g. in content/, dom/ or layout/, you also need to build make -C layout/build/
With libxul (all code in one library, which is the default for opt builds now), you need to also build make -C toolkit/library/
On Mac, you will also have to build make -C browser/app
配置文件
confvars.sh : 编译选项存放文件，包括不可用的命令行选项
Note that build options, including options not usable from the command-line, may appear in "confvars.sh" files in the source tree. https://developer.mozilla.org/zh-CN/docs/配置编译选项
cd objxxx
cd toolkit/xre
mozmake
cd toolkit/library
mozmake
复制代码
d 作者: Qter 时间: 2020-8-25 14:44
there's no official recommendation for editors. Amongst Firefox developers who were employees, when we did a survey a while back it was roughly split equally between atom/vscode/sublime, though I don't know about the emacs/vim numbers, I suspect they were lower
The editor isn't important as long as you're comfortable with it. We have things like ESLint/prettier to ensure expected code layouts etc