Hi there, I'm porting b2g to a TI am335x Starter Kit that is running Android 4.1.2
I forked repositories from https://github.com/mozilla-b2g/B2G.git and https://github.com/mozilla-b2g/b2g-manifest.git Created am335xevm_sk.xml in the b2g-manifest repo. This is based off default.xml with the platform dependent references modeled from the TI configs in the rowboat manifest project git://gitorious.org/rowboat/manifest.git : rowboat-jb-am335x.xml I added: <remote name="jsr38" fetch="https://github.com/jsr38"; /> <remote name="rowboat" fetch="git://gitorious.org/rowboat" /> We also add: <default remote="rowboat" revision="rowboat-jb" sync-j="4"/> <!-- Gonk specific things and forks --> <project path="build" name="build" remote="rowboat" revision="master"> <copyfile src="core/root.mk" dest="Makefile" /> </project> the build system from rowboat contains the build machinery for target am335xevm_sk (I believe!). For the Android dependencies, I plan to look for the same Android dependencies as are in default.xml except source them from Rowboat. I plan to take the device dependent code from the TI Rowboat manifest: rowboat-jb-am335x.xml Am I along the right track? Has anyone ported b2g to this hardware before? Which are the most critical dependency versions to align? For example does the B2G code I'm referencing (master), require a minimum Android version? I understand the B2G build is referencing an Android filesystem tree for some binaries - is the dependency here the critical one in that the referenced Android source version in the B2G build must be in exact agreement with the filesystem tree versions? Regards...Jeremy _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
