Hi Ryan, all, Sorry for taking so long to respond on this one.
Since this sounds like a .userconfig thing, I’ve created a new section here: https://developer.mozilla.org/en-US/Firefox_OS/Customization_with_the_.userconfig_file#Creating_different_build_types I’ve taken some of Dave’s excellent advice from the thread and converted it into a description of the different variants, and also linked some of the existing content from that article together a bit better. I’ve also included link to the make option reference so it is easy to find and reference, and also called out build time-equivalent make options where I know them. Does this look ok? Please suggest or add more details as you deem necessary. Chris Mills Senior tech writer || Mozilla developer.mozilla.org || MDN [email protected] || @chrisdavidmills On 25 Sep 2014, at 04:26, J. Ryan Stinnett <[email protected]> wrote: > Chris - > > I think it would be helpful to document the difference between the > variants, maybe with a table or something. This is something I found > quite confusing when getting started with the project. > > I wasn't sure where to best put this info on MDN. Is there an existing > page this would fit into, or should I dump it into it's own page? > > - Ryan > > On Fri, Sep 12, 2014 at 3:15 AM, Dave Hylands <[email protected]> wrote: >> You can somewhat control things by changing the VARIANT (when build for a >> real device/emulator) >> >> https://developer.mozilla.org/en-US/Firefox_OS/Customization_with_the_.userconfig_file >> >> There are 3 variants: >> >> VARIANT=user >> VARIANT=userdebug >> VARIANT=eng >> >> The eng variant puts the apps in /data and includes many more apps than >> user/userdebug. user/userdebug puts apps in /system >> The eng and userdebug variants have marionetter enabled by default, so you >> can run tests >> The user and userdebug variants have the updater enabled, so you can do >> over-the-air (OTA/FOTA) updates. >> >> make production in gaia sets PRODUCTION=1 >> user and user-debug both imply PRODUCTION=1 when building locally for a real >> device/emulator). >> >> make production is really a way to build a user version of gaia for use with >> nightly or B2G-desktop. Specifying VARIANT is the way to do this when >> building for a device/emulator >> >> Dave Hylands >> >> ________________________________ >> >> From: "Sam Penrose" <[email protected]> >> To: [email protected], [email protected], "Christopher >> Mills" <[email protected]> >> Sent: Thursday, September 11, 2014 3:29:52 PM >> Subject: [b2g] Understanding production vs engineering builds >> >> >> We recently ran into an FxOS bug that only appeared on production builds: >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1058978#c12 >> >> I could not find documentation specifying the differences between >> engineering and production builds of Gecko and Gaia, and more importantly >> how to control them. Does such documentation exist? If not, where should I >> request it? >> >> Are the underlying controls independent, and if not should they be? For >> example, "make production" in Gaia wants to install on device: is there a >> way to create a "production" Gaia target without installing it on device? I >> routinely run custom B2G builds with custom Gaia builds -- are the >> "production" vs "engineering" settings for Gecko and Gaia independent, or >> are there known restrictions in how I can mix and match them? >> >> Thanks, >> Sam >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g >> >> >> >> _______________________________________________ >> dev-gaia mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-gaia >> _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
