So you want to add something
Akkana Peck, firstname.lastname@example.org
(and not break the build) ...
All platforms are now using the same set of Makefiles for the build, so,
finally, all you have to do are edit Makefile.in files (and possibly
mozilla/allmakefiles.sh if you add new makefiles).
Don't forget to check Tinderbox after you check in!
Adding files to the build
- All platforms use
Makefile.infiles now. Edit these to add new source files, and export header files.
- Dependencies are specified in
- If you add a new directory to the build, you have to add an entry for
its Makefile in the directory list in
mozilla/allmakefiles.sh, as well as adding the directory to the list of subdirs in
Adding new files to the build can cause breakage on tinderbox and to other developers if things aren't checked in the correct order.
- Check in only the new files.
- Check in the patches to existing files that make your new files get used.
Exporting a file makes it get copied to mozilla/dist. C and C++ header
files are exported by including them the
EXPORTS list in
Makefile.in, and IDL files are exported by
including them in the
If you create something that needs to be present in an end-user
distribution then don't forget to add it to the proper xpinstall packages.
Add your file to the appropriate places (depending on where it's needed) in
If your new files are needed by embedders, then also add them to the
appropriate lists in
Neglecting to add your new files to xpinstall packages means that your new feature will work when you run it from your own tree, but will break in packages distributed to actual end users.