Development:Building:Mac OS X 10.6

Building on Mac OS X 10.6 is unfortunately rather complicated. Gecko 1.9.2 is not 10.6-build-friendly (and, alas, becomes less so over time). This page contains a full list of supplemental instructions to help you complete a Cm2.1-M1.9.2 build on Mac OS X 10.6 (please be sure you follow all of the other instructions on Development:Building:Mozilla 1.9.2 Branch).

If you discover a new Cm2.1-M1.9.2 on Mac OS X 10.6 build breakage, please let us know in Bug 514495; once there is a solution to the new breakage, we will update these supplemental instructions.

If you need to hack on about:crashes, you can test your changes by loading chrome://global/content/crashes.xhtml instead.

Local Patches

Currently, additional build failures must be worked around by applying local patches. Apply these patches before beginning your build.

run-mozilla.sh

The run-mozilla.sh script is used in several places during the Gecko build and packaging (regenerating some JavaScript test code, signing NSS libraries), but due to the SQLite linking debacle (Bug 513747), run-mozilla.sh sets an incompatible dyld path.

Note: this is the only patch that is required in all 10.6/1.9.2 build configurations.

unify vs. osacompile and Camino’s feedhandlers

osacompile on Mac OS X 10.6 will only produce 3-way ppc7400-i386-x86_64 binaries, despite being instructed to generate single-architecture binaries when building our feedhandlers. Mozilla’s unify script can only handle ppc and i386 binaries, so it must be patched in order to properly process the feedhandlers in Universal builds.

Building in Xcode

Breakpad may fail to build, complaining about GCC 4.2 not being compatible with the 10.4 SDK. If this happens, open the Breakpad.xcodeproj file in the External Projects folder. Set the Build Configuration to match the Build Configuration set in Camino.xcodeproj. Do a Get Info on the project file in the new project window, and in the Build tab set 'C/C++ Compiler Version' to 'GCC 4.0'.