Now,I have download "vexpress-linaro-13.09-release",next I want to build it.But I donot want to rebuild "native-toolchain",can I use the toolchain from "http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2013.09" instead of it ? The followings are my operations: 1. download the toolchain from "http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2013.09" 2. mv the toolchain to "<android code directory>/prebuilts/gcc/linux-x86/arm/" , then "tar xvf android-toolchain-eabi-4.7-2013.09-x86.tar.bz2" 3. gedit <android code directory>/native-toolchain/Android.mk comment out the two lines: native-toolchain: $(GCC_FILE_NAME) $(GCC_FILE_NAME): $(TARGET_CRTBEGIN_DYNAMIC_O) $(TARGET_CRTEND_O) / $(TARGET_OUT_SHARED_LIBRARIES)/libm.so $(TARGET_OUT_SHARED_LIBRARIES)/libc.so / $(TARGET_OUT_SHARED_LIBRARIES)/libdl.so $(TARGET_OUT_SHARED_LIBRARIES)/libstlport.so 4. gedit "linaro_android_build_cmds.sh" modify line:export TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86... to export TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86/arm/android-toolchain-eabi/bin/arm-linux-androideabi- 5 . build/envsetup.sh make boottarball systemtarball userdatatarball so is it right to build the code with a prebuild toolchain ? Looking forward to your answer.
Hi,
On 3 April 2014 09:33, dcv muzhendenglu@126.com wrote:
Now,I have download "vexpress-linaro-13.09-release",next I want to build it.But I donot want to rebuild "native-toolchain",can I use the toolchain from " http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2013.09
You can just remove the native-toolchain component from the manifest to avoid building it. The toolchain is built to be used on the target and not to build android so you can omit it. Android would still build using the Linaro's 13.09 toolchain that is pulled by repo sync in "prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8-linaro" .
" instead of it ? The followings are my operations
- download the toolchain from "
http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2013.09" 2. mv the toolchain to "<android code directory>/prebuilts/gcc/linux-x86/arm/" , then "tar xvf android-toolchain-eabi-4.7-2013.09-x86.tar.bz2" 3. gedit <android code directory>/native-toolchain/Android.mk comment out the two lines: native-toolchain: $(GCC_FILE_NAME) $(GCC_FILE_NAME): $(TARGET_CRTBEGIN_DYNAMIC_O) $(TARGET_CRTEND_O) / $(TARGET_OUT_SHARED_LIBRARIES)/libm.so $(TARGET_OUT_SHARED_LIBRARIES)/libc.so / $(TARGET_OUT_SHARED_LIBRARIES)/libdl.so $(TARGET_OUT_SHARED_LIBRARIES)/libstlport.so 4. gedit "linaro_android_build_cmds.sh" modify line:export TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86... to export TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86/arm/android-toolchain-eabi/bin/arm-linux-androideabi- 5 . build/envsetup.sh make boottarball systemtarball userdatatarball so is it right to build the code with a prebuild toolchain ? Looking forward to your answer.
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
Can I think the relationship among Ubuntu、native-toolchain、arm-linux-androideabi-4.8-linaro is: Ubuntu-gcc compile <android-directory>/native-toolchain to generate ".so" file about ARM,then when arm-linux-androideabi-4.8-linaro builds android,it will use .so file.
And ,you say "The toolchain is built to be used on the target",I want to know what is the target, the target is "system.tar.bz userdata.tar.bz boot.tar.bz "or "system.img"?
在 2014-04-03 13:05:44,"Vishal Bhoj" vishal.bhoj@linaro.org 写道:
Hi,
On 3 April 2014 09:33, dcv muzhendenglu@126.com wrote:
Now,I have download "vexpress-linaro-13.09-release",next I want to build it.But I donot want to rebuild "native-toolchain",can I use the toolchain from "http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2013.09
You can just remove the native-toolchain component from the manifest to avoid building it. The toolchain is built to be used on the target and not to build android so you can omit it. Android would still build using the Linaro's 13.09 toolchain that is pulled by repo sync in "prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8-linaro" .
" instead of it ? The followings are my operations 1. download the toolchain from "http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2013.09" 2. mv the toolchain to "<android code directory>/prebuilts/gcc/linux-x86/arm/" , then "tar xvf android-toolchain-eabi-4.7-2013.09-x86.tar.bz2" 3. gedit <android code directory>/native-toolchain/Android.mk comment out the two lines: native-toolchain: $(GCC_FILE_NAME) $(GCC_FILE_NAME): $(TARGET_CRTBEGIN_DYNAMIC_O) $(TARGET_CRTEND_O) / $(TARGET_OUT_SHARED_LIBRARIES)/libm.so $(TARGET_OUT_SHARED_LIBRARIES)/libc.so / $(TARGET_OUT_SHARED_LIBRARIES)/libdl.so $(TARGET_OUT_SHARED_LIBRARIES)/libstlport.so 4. gedit "linaro_android_build_cmds.sh" modify line:export TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86... to export TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86/arm/android-toolchain-eabi/bin/arm-linux-androideabi- 5 . build/envsetup.sh make boottarball systemtarball userdatatarball so is it right to build the code with a prebuild toolchain ? Looking forward to your answer.
_______________________________________________ linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-android@lists.linaro.org