Le dimanche 3 janvier 2016 13:40:26 UTC+1, Alexandre Lissy a écrit :
>
> Then do as documented on
> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developing_Firefox_OS/Porting#Create_a_manifest_for_the_new_device
> and GITREPO=... BRANCH=... ./config.sh miata-3g-kk.xml
Thanks again for advice. Unfortunately, I already tried that, as can be seen in
my initial post :-(
But in the meantime, I've found the culprit. From [1], it's said to configure
with:
ANDROIDFS_DIR=my_device_backup ./config.sh <device_id>
'../b2g-manifest/default.xml'
Well, it turns out that the trailing '../b2g-manifest/default.xml' is messing
everything. I've also tried replacing with '../b2g-manifest/miata-3g-kk.xml',
thinking that 'default.xml' was given as an example and should be replaced with
the real manifest filename but this didn't help either.
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?
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
The '-eng' string appended to 'miata-3g' seems to come from the VARIANT
variable in load-config.sh script. What am I supposed to do with this variable?
It's quickly documented in [2] but this doesn't explain what I have to do.
Blank it so that lunch combo becomes 'miata-3g'? Or fix something in my
manifest/device tree so that 'miata-3g-eng' becomes a valid lunch combo?
Émeric
[1]
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developing_Firefox_OS/Porting#Configure_build_and_flash_the_new_device
[2]
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Building#Building_an_official-style_engineering_build
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
