I should also add:
The version of gcc used to cross compile our TI kernel and in the past, the entire Android stack has been a 4.6 version whereas you guys are recommending a 4.4 version. I understand that the kernel and the C library, particularly targeting non x86 architectures can be sensitive to early adopted gcc changes (I'm building on a Fedora 18 system which by default has gcc 4.7.x which we should steer clear of). Can we build using a mix or will that potentially mess up dynamic linking of the c library (not even sure how this works on Android/B2G - this is bionic, right?) ? Any reason not to stick with 4.6 or is 4.4 a requirement for the B2G stack? Here are the relevant manifests: https://github.com/jsr38/b2g-manifest/blob/master/am335xevm_sk.xml https://gitorious.org/rowboat/manifest/blobs/master/TI-Android-JB-4.1.2-DevKit-4.0.1.xml The TI manifest is based off Android 4.1.2 - is there an equivalent B2G tag/branch/release that we can reference? Some sort of matrix for aligning kernel version, Android version and B2G version ...? Apologies for all the questions but I'm starting from an almost zero Android experience with zero B2G experience... Regards...Jeremy On Wed, Apr 24, 2013 at 11:07:38AM +0200, Jeremy Reeve wrote: > > > Hi there, > > Any pointers? > > Should we be trying to build against B2G v1-train in general? > > Any tips on blob extraction? - I see there is a script in device/common to > generate the required extract-files.sh > > I've created the relevant makefiles and other support scripts > (vendorsetup.sh) so that the build is now "lunch compatible" whereas the TI > Android project used a hand crafted makefile for building the kernel and > wireless drivers. > > It seems that the build repo has diverged a little from Android and therefore > also the TI Rowboat Android. I originally used the TI Rowboat Android build > repo as I thought there might be changes required that relate to building the > device dependent source device/ti/am335xevm_sk and the wireless hardware > support. > > It seems that there is some conflict between certain packages ( > system/bluetooth , platform/bionic, platform/bootable/recovery ) and the > master branch of the build system. The build reports > > "build/core/base_rules.mk:85: * Each module must use a LOCAL_MODULE_TAGS in > its > build/core/base_rules.mk:86: * Android.mk. Possible tags declared by a > module:" > > ... and so on. This was resolved by selecting particular code revisions of > the packages drawn from the pandaboard manifest, for example, from the > git://codeaurora.org/ based repos. > > We have a suitable kernel, u-boot bootloader and init scripts along with a > running Android system present so I would have thought this is entirely > possible. > > We're keen to contribute this work back to the project if that is desirable. > Not certain that it is given the lack of radio telephony hardware on the > board - but it's a cheap and ubiquitous platform for basic app dev work, I > suppose. > > Any help or direction greatly appreciated. > > Regards...Jeremy > > > > On Fri, Apr 19, 2013 at 12:37:32PM +0200, Jeremy Reeve wrote: > > > > 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 > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
