On 24 July 2012 07:20, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
On Jul 24, 2012 1:59 PM, "Paul Sokolovsky" paul.sokolovsky@linaro.org wrote:
Yes, I wonder if putting toolchain in git will, while solving some problems, create other (delayed) ones. There're other alternatives besides those you mentioned - for example, instead of building toolchain as part of android build, there can be native android makefile to download that toolchain.
Yes, but that would have pretty much the same issues as the current TOOLCHAIN_URL solution. Especially once build configs are in git, that will come down to pretty much the same thing we're doing already.
Okay, so I'd like to propose that we move forward with the git approach since it is part of the standard AOSP flow and will improve build reproducability.
Any other option gets us where we're at today:
Builds don't follow standard Android build procedures Disconnecting the toolchain from the build causes our users confusion and is always a source of problems for our users
Should we spin up a separate git to host the toolchain (and other binaries) so that we can segregate any binary blob effects?
ttyl bero