I mentioned this on IRC and on a mailing list, and got positive responses. We should make --enable-application default to browser, so that simply running "configure && make" from a source tarball gets you a Firefox build that's almost identical to what we ship. This is the only required configure option right now, and since 99% of people want to build Firefox, we might as well just make it easier. This makes us more in line with other open source project builds as well.
(Since client.mk defaults to an objdir, this means you could also make -f client.mk without a mozconfig and get a reasonable build of Firefox in an objdir.)
Created attachment 521749 [details] [diff] [review]
Comment on attachment 521749 [details] [diff] [review]
Looks good, thanks!
This has a note at the top as well as a similar one where it talks about --enable-application.
In addition, I've added information about mozilla-aurora to:
Figured I'd tackle that at the same time since it's somewhat related.
In addition, this change is mentioned on Firefox 5 for developers.
Does the theory that this builds something roughly the same as what we ship include building a universal 32-bit/64-bit binary on Mac?
No, that doesn't. I think that's not quite as useful. Note that you don't get a PGO build by default on Windows either. Both of those options add a lot to your compile time, but don't give you much in return if you just want a build you can run locally. People trying to replicate exactly what we ship are probably a smaller group than just people trying to build Firefox that's close enough to what we ship that they can usefully hack on it.
There's probably some value in an MDN document describing how to more-exactly reproduce what we ship on each platform.
Agreed. I will file a bug to put it on the future roadmap, although realistically it's something that someone in releng might be better suited to produce.