On Sun, Jul 22, 2012 at 5:38 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Hey Bero/Paul
Who sets up:
http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2012.07/1/...
and
http://android-build.linaro.org/download/linaro-android_toolchain-4.7-bzr/la...
I'm asking because I'd like to solve a problem our users are running into. The instructions listed on top of each build pages are wrong. They say things like:
$ wget --no-check-certificate http://android-build.linaro.org/download/linaro-android_toolchain-4.7-bzr/la... $ tar -jxvf android-toolchain-eabi-linaro-*
when the build is using
TOOLCHAIN_URL=http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2012.07/1/...
I'd like to fix this so that the builds pull the right thing. I was thinking that we could commit the toolchain tarballs to git and then just pull things as part of the manifest. That would help our local users. We could also take a half step and write a script that would setup the environment and have people (and the build server) also use that.
We have the same issue with:
KERNEL_CONFIG=omap4plus_defconfig
Which should be in the build.
Anyway, I think its time to start making:
MANIFEST_REPO=git://android.git.linaro.org/platform/manifest.git MANIFEST_BRANCH=linaro_android_4.0.4 MANIFEST_FILENAME=tracking-panda.xml TARGET_PRODUCT=pandaboard TARGET_SIMULATOR=false TARGET_BUILD_VARIANT=tests SOURCE_OVERLAY="open/20120716/build-info.tar.bz2" TOOLCHAIN_URL=http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2012.07/1/... TOOLCHAIN_TRIPLET=arm-linux-androideabi REPO_SEED_URL=http://android-build.linaro.org/seed/uniseed.tar.gz LAVA_SUBMIT=1 LAVA_SUBMIT_FATAL=0 TARGET_NO_HARDWAREGFX=1 KERNEL_CONFIG=omap4plus_defconfig LAVA_ANDROID_BINARIES=False LAVA_TEST_PLAN="busybox,0xbench,glmark2,skia,v8,mmtest,monkey,monkey_long_run" MONKEY_RUNNER_URL_1="git://android.git.linaro.org/test/linaro/android/system.git" CTS_TIMEOUT=36000
turn into:
MANIFEST_REPO=git://android.git.linaro.org/platform/manifest.git MANIFEST_BRANCH=linaro_android_4.0.4 MANIFEST_FILENAME=tracking-panda.xml
Personally, I am not against having a toolchain in git, and we probably want to use prebuilt/ directory for that. However, due to the way git stores big binaries we most likely do not want to commit daily toolchains there; just release candidates or even releases.
In that case your doc problems probably wouldn't be going magically away and you would still need to come up with generic instructions on how to build with latest daily toolchain without having that committed to git.