We solved this last night. If you have the environment variable GAIADIR set, it is used in gecko build process to bundle a copy of the gaia profile with it. This only works as expected with B2G desktop and (silently) breaks other targets.
I can update our configure script to ignore GAIADIR for non-B2G desktop builds but does anybody know what the proper switch is to check we are building B2G desktop (or Mulet presumably)? After some digging, I would have thought FXOS_SIMULATOR would be it, as that is set under b2g/config/mozconfigs/*** targets and used in the source. But it appears our instructions for building B2G desktop [1] and Mulet [2] don't mention it. As it turns out, I've never used it myself and it has worked just fine. [1] https://developer.mozilla.org/en-US/Firefox_OS/Building_the_Firefox_OS_simulator#Create_a_mozconfig [2] https://wiki.mozilla.org/Mulet#How_do_I_build_it.3F On Mon, May 11, 2015 at 4:49 PM, Naoki Hirata <nhir...@mozilla.com> wrote: > Did you rebuild your backup-flame directory from the latest > mozilla-central pvt build as per described in the second part? > > It also sounds like you may need to update your gecko directory : > > /Volumes/firefoxos/sandbox/mozilla/B2G/gecko >>> >>> Doing a ./repo sync will not update that directory. Which repo is that > directory pointing to? > > -N. > > On May 11, 2015, at 1:34 PM, Russ Nicoletti <rnicole...@mozilla.com> > wrote: > > I have flashed 18D and the latest mozilla-central pvt build. Same result. > My build is still generating 'b2g-bin' executable in addition to the 'b2g' > executable and flashing my custom gecko causes the device to fail to boot > up. Fabrice mentioned when I pinged him about this the problem was that a > 'b2g-bin' file was being produced by my build but he didn't know why it was > being produced by a "device" build. > > -Russ > > On Mon, May 11, 2015 at 12:09 PM, Naoki Hirata <nhir...@mozilla.com> > wrote: > >> Odd. That should boot up still regards of the other out of date bits on >> the device. >> >> Let's first get you up to date on the other bits though, please download >> and flash the 18D then the flame.zip from >> https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-eng/latest >> >> You will have to rebuild your flame-backup folder is my guess as well. >> It might be that your backup folder is out of date. >> There's couple ways you can go about getting the folder to rebuild, I >> just delete or mv the folder. >> Be sure to have your flame device on, plugged in, with adb access before >> you run the build script. >> >> Regards, >> Naoki >> >> >> On May 11, 2015, at 10:54 AM, Russ Nicoletti <rnicole...@mozilla.com> >> wrote: >> >> Last week I installed the image from >> https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-eng/latest. >> Prior to that I had the v188 image. >> >> -Russ >> >> On Mon, May 11, 2015 at 10:08 AM, Kevin Grandon <kgran...@mozilla.com> >> wrote: >> >>> Which base image did you install on the flame before flashing Gecko? >>> >>> Best, >>> Kevin >>> >>> On Mon, May 11, 2015 at 5:57 PM, <rnicole...@mozilla.com> wrote: >>> >>>> I'm building gecko on OSX 10.9.5 for a flame. My workflow is: >>>> >>>> ./config.sh flame-kk >>>> ./build.sh gecko >>>> ./flash.sh gecko >>>> >>>> The build succeeds yet the flame doesn't boot up after I flash. I >>>> noticed the build produces a 'b2g-bin' file dist/b2g. My understanding is >>>> this should only be produced for desktop builds. I believe the fact that >>>> this file is produced is the source of the startup errors. >>>> >>>> My .userconfig is: >>>> >>>> export MOZ_PROFILING=1 >>>> export DEVICE_DEBUG=1 >>>> export GECKO_PATH=/Volumes/firefoxos/sandbox/mozilla/B2G/gecko >>>> >>>> Any help/hints are appreciated. >>>> >>>> -Russ >>>> _______________________________________________ >>>> dev-b2g mailing list >>>> dev-b2g@lists.mozilla.org >>>> https://lists.mozilla.org/listinfo/dev-b2g >>>> >>> >>> >> _______________________________________________ >> dev-b2g mailing list >> dev-b2g@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-b2g >> >> >> > > > _______________________________________________ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g > >
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
