On Thu, Jul 18, 2013 at 10:51:10AM +0900, Mike Hommey wrote: > Hi, > > As it seems there is a trend towards using in-tree mozconfigs for > local developer builds, I think a reminder is in order: > > In-tree mozconfigs are for buildbot consumption. > > For Firefox desktop builds, a mozconfig should be unnecessary for most > people, except if their compiler is not at a standard location. > > If that doesn't work for you, try running ./mach bootstrap at the root > of the mozilla source tree. If that still doesn't build after that, > please try asking on the #build irc channel or file a bug in the > Core::Build Config component. > > For Firefox for Android builds, a mozconfig is necessary, but it only > needs to contain the following: ac_add_options > --enable-application=mobile/android ac_add_options > --target=arm-linux-androideabi ac_add_options > --with-android-ndk=/path/to/ndk ac_add_options > --with-android-sdk=/path/to/sdk > > (the target varies for x86 android builds, and the addition of > "ac_add_options --with-arch=armv6" is required for armv6 builds) > > If the mozconfig above doesn't work for you, double check the > instructions on > https://wiki.mozilla.org/Mobile/Fennec/Android#Building_Fennec > specifically, that you have all the build dependencies installed > (eventually, this should make it into mach bootstrap, see bug 844838), > and if that still doesn't work, please try asking on the #build irc > channel or file a bug in the Core::Build Config component.
As Boris noted on irc, there is room for flexibility. You may require ac_add_options --enable-debug, and you may want to use ac_add_options --with-ccache. There are a few other options you can use in a mozconfig, But the bottom-line is minimalistic mozconfigs should be enough for everyone, and in-tree mozconfigs should be left alone. Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
