Le 08/01/2016 22:48, [email protected] a écrit : >> So, what did the trick for me was configuring build simply with: >> >> ANDROIDFS_DIR=my_device_backup ./config.sh <device_id> >> >> Is it expected? Is the documentation [1] thus inaccurate? > > Still don't know for this, but since removing the trailing > '../b2g-manifest/default.xml' in the aboce command-line did the trick, I'm > fine with it for now. > >> BTW, don't enjoy to quickly ;-) Trying to build Firefox OS then failed >> within seconds with: >> >> including device/generic/armv7-a-neon/vendorsetup.sh >> including device/qcom/common/vendorsetup.sh >> >> Invalid lunch combo: miata-3g-eng > > Blah, naming <device_id> and thus PRODUCT_NAME and config makefile using '-' > character (i.e. miata-3g) wasn't a good idea ;-) > > Invalid lunch combo was coming from build/envsetup.sh that was fooled at > determining variant variable from PRODUCT_NAME because of '-' character: > > local variant=$(echo -n $selection | sed -e "s/^[^\-]*-//") > > Renaming <device_id> and thus PRODUCT_NAME and config makefile from miata-3g > to miata_3g (note the underscore character) fixed the problem. > > A hint about naming conventions for <device_id> in B2G Porting Guide may be > helpful ;-)
Excellent! Reminds me of https://bugzilla.mozilla.org/show_bug.cgi?id=1183027 > > Émeric > > > [1] > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developing_Firefox_OS/Porting#Configure_build_and_flash_the_new_device > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
