Thanks, Stuart!
Just a few clarifications, then:
What is this crypto, and what are the instructions for setting it up? Does anyone have detailed instructions for setting up .mozconfig?
This is sort of cruft from the older instructions, which had users make a .mozconfig from scratch. Now that it's mostly just sourcing $topsrcdir/camino/config/mozconfig it's not the sort of thing a casual builder is likely to have to deal with.
In that case, are these .mozconfig instructions up to date? Is there anything wrong or missing? Also, does it matter in what order the flags appear in .mozconfig?
In your mozilla directory, create a plain text file called .mozconfig (note the leading period). This file is where you will set up the options for your Camino build:
* Optimized or Debug Mode Build :
For an optimized build, add the following line to your .mozconfig file:
. $topsrcdir/camino/config/mozconfig
To build in debug mode, add the following two lines instead:
ac_add_options --disable-optimize
ac_add_options --enable-debug[Please note: It's important to be aware of whether you've set up .mozconfig for a debug or optimized build, because you must match that setting when building Camino from Xcode. If the settings are not matched, key build variables won't get set correctly and vtables will be out of alignment. The net result is that either you won't link, or you'll crash at startup.]
* Static or Dynamic Build
By default, Camino is built dynamically. To do a static build of Camino (which means that most of the components are compiled directly into the Camino binary), you can add the following lines to your .mozconfig:
ac_add_options --disable-shared
ac_add_options --enable-staticStatic builds are used for distribution but are not recommended for development.
* Building More Quickly on Dual-CPU Machines
If your machine has two CPUs?, you can take advantage of that while building Camino. Add the following to your .mozconfig:
mk_add_options MOZ_MAKE_FLAGS=-j3
---------------
7) How do you set up Xcode for an optimized vs. a debug build?
Select 'Deployment' or 'Development' as a build style
Where in Xcode (in which menus/dialogs/whatever) is this option found?
8) How does one set up CVS within Xcode to pull code from the Camino repository?
Um... that probably wouldn't be a terribly good idea in most cases, since in general it's good to update general Mozilla code and Camino code at the same time in case something changed in Mozilla that required changes in Camino, and the Camino Xcode project doesn't know about all the other Mozilla code.
So CVS checkout should be done from the command line or another client rather than from Xcode? Are the following instructions accurate?
% setenv CVSROOT :pserver:[EMAIL PROTECTED]:/cvsroot
(or set up graphical client to use "cvs-mirror.mozilla.org" as the server, "cvsroot" as the root directory, and "anonymous" as the username)
% cvs login (Logging in to [EMAIL PROTECTED])
When prompted for password, type "anonymous"
To check out a full copy of the source:
% cvs co mozilla/client.mk
% cvs co mozilla/camino/config/mozconfig
% make -f client.mk checkout MOZ_CO_PROJECT=macbrowser
[I take it this just checks out all required files without actually running a build.]
(or, for update:)
% cvs update mozilla/client.mk % cd mozilla % make -f client.mk update MOZ_CO_PROJECT=macbrowser
----------------
Thanks, again!
-Noemi
_______________________________________________ Camino mailing list [email protected] http://mozdev.org/mailman/listinfo/camino
