mozconfig vs. manual configure
I think these instructions can be cleaned up and made to be much easier for new users. First off, can you explain what the real problem with simply doing:
./configure --enable-application=browser make
Second: the instructions say to "export MOZCONFIG=~/mozilla/mozconfig-firefox". If that is always the case, then it should just be defined as `pwd`/mozconfig-firefox then the instructions should just go away and replaced with instructions on how to set this to something else. Agreed? Thanks for your time, Jeff Carr 14:53, 27 December 2005 (PST)
Manual configuration (without sourcing browser/config/mozconfig) does not work on older branches such as the aviary (Firefox/Thunderbird 1.0.x) branch.
As explained in the instructions, the default location of mozconfig is the root of the source tree, or ~/.mozconfig if not present. You only need to set MOZCONFIG in your environment to override this default.
--bsmedberg 13:32, 28 December 2005 (PST)
fb in fb-opt-static
What does the fb in fb-opt-static for Firefox mean? Doesn't ff-opt-static make more sense?
- It stood for "FireBird", probably a remnance from one of the original authors mozconfig's from back when s/he was working on Firebird (same app, just prior to new name). I have taken the liberty of correcting the article to read
ff-opt-staticnow in its place, for clarity reasons, based on your suggestion. Thanks! --Callek 17:06, 16 February 2006 (PST)
Which branch is this document targetted at? I see things that applied to 1.8 (Gtk (1)? Qt!?) but have no chance on trunk, and things that are trunk (libxul being default). I am attempting to try to use past tense for old information, but it would be nice if this is made clear. --Mook 00:00, 9 April 2008 (PDT)
The reason I made the edit was due to the fact that I had tried building in an objdir outside the 'mozilla' source folder, and I kept getting build errors. Putting the objdir inside 'mozilla', and changing nothing else, resulted in a clean build.