Le 03/01/2016 12:45, [email protected] a écrit : > Le samedi 2 janvier 2016 23:57:23 UTC+1, Naoki Hirata a écrit : >> You need the file in the <B2G Project folder for your miata>/.repo/manifests > > Hello Naoki, > > Thanks for the feedback. > > My miata-3g-kk.xml manifest file is indeed in .repo/manifests of my local B2G > clone. And now I understand the error: there's nothing beside my manifest > file in .repo/manifests! Looking at repo_sync() function of config.sh script, > I see that it first wipes everything in .repo/manifest* before sync'ing > again. When I invoke config.sh for e.g. flame-kk, .repo/manifests is > correctly populated by the files that seem to come from b2g-manifest repo. > > Although I now understand the error (there's indeed no base-kk-caf.xml file > in .repo/manifests), I still don't understand the cause :-( I've correctly > commited my miata-3g-kk.xml manifest file in my local b2g-manifest repo, as > instructed in [1]. > > Émeric > > > [1] > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developing_Firefox_OS/Porting
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 > _______________________________________________ > 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
