On 21 April 2011 05:54, Michael Hope <michael.h...@linaro.org> wrote:
> Hi Jim. Good effort. The Android patch set will be included in
> gcc-linaro-4.5-2011.04 which is due out today.
>
hi Michael,
Thanks!
Look forward to new release.
> We need to discuss toolchain build scripts at the summit. There's a
> want for builds of pretty much every combination of
> {Android,Linux,bare metal?} target, crossed with {Native,Cross}
> builds, crossed with {Ubuntu,Generic Linux,Windows?} hosts. I'll talk
> with Alexander and Steve and see about a session.
After checking the build scripts of Google compiler team[1] and
NDK[2], the targets are as following:
(1) arm-eabi : bare metal, used for compiling Android kernel and
(older) userspace
(2) arm-linux-androideabi : the primary target in Android
We should migrate to use arm-linux-androideabi since
gcc-linaro-2011.04 is expected to include the Android specific patches
such as bionic libc linkage.
In my opinion, Android team of Linaro should follow the
methods/instructions how Google engineers built toolchain and NDK (the
"superset" of toolchain) and continue sending patches to AOSP for
merging generic features or improvements.
Yes, I agree with ideas to unify build scripts, but it hard to decide
the working items because of uncertainty of AOSP development model.
Sincerely,
-jserv
[1] http://android.git.kernel.org/?p=toolchain/build.git;a=summary
NOTE: for unknown reasons, I encountered some problems with the
original build script written by Google engineers. Maybe due to merge
failure between internal tree and AOSP.
[2] http://android.git.kernel.org/?p=platform/ndk.git;a=summary
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
