On 3/6/2014, 8:18, Johannes Bauer wrote:
One problem for me is that I cannot tell which components are
proprietary (vendor-specific) and which aren't. During the build process
the phone has to be hooked up so it can fetch these proprietary files.
It's not transparent to me where these files end up and how I can back
them up properly.
This also means that rebuilding a whole tree after a long time is
difficult, because all the fetch-proprietary-things step has to be done
again. Would it maybe be possible that the installer fetches the
proprietary files and creates one single file (proprietary.tar.gz) that
I could download once from my phone and then just drop-in into my build
tree?
That'd be rather cool since I could have my proprietary.tar.gz backed
up, remove the tree after 6 month, reclone everything, drop in the
tar.gz and just rebuild (and end up with a working image).
In general the proprietary files are stored in a backup-* folder inside
the B2G source folder. (For the Alcatel it's probably called
backup-hamachi or backup-buri). You should be able to back this folder
up as you describe and then put it back into place into a new source
tree at some later date. For devices that we are still in the process of
adding support the contents of the folder may change as we add support
for difference pieces of hardware, but for the Alcatel phone that
shouldn't be a problem.
Hope that helps.
Cheers,
kats
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
