3. Source builds and the separate XULRunner dependency

The CF repository builds the CF engine, its Metaproxy module, JavaScript runtime modules and documentation. It consumes an installed XULRunner SDK; it does not download, configure or compile Mozilla as part of the normal build.

After installing the dependency SDKs, follow Section 5, “Compiling CF programs” to compile CF itself. For package builds, debian/control and cf.spec declare CF's dependencies; the cf-xulrunner repository declares the separate dependencies needed to compile Mozilla.

3.1. Building cf-xulrunner separately

The Mozilla sources, compatibility patches, build configuration and dependency packaging belong to the separate cf-xulrunner Git repository. Make changes to Gecko or its build there, build new cf-xulrunner packages, and install those packages before building or testing CF. Refer to that repository's build instructions for the dependency build.

On Debian and Ubuntu the runtime is cf-xulrunner38 and the SDK is cf-xulrunner38-dev. They install under /usr/cf-xulrunner. The SDK includes the private interpreter /usr/cf-xulrunner/bin/python2.7 and its standard library for Mozilla's IDL generators. CF uses those tools to generate its interface headers and type libraries. There is no need to change /usr/bin/python or install an obsolete system Python package.

3.2. Historical build helper

engine/xulrunner.mk is a historical helper for XULRunner 10 and older dependency stacks. It is retained for reference and is not the build procedure for the current cf-xulrunner38 packages. Likewise, engine/README.MacOS describes an older macOS setup rather than the current Debian/Ubuntu package workflow.