I believe 8250 can run armv5 code generated by android toolchian, because I wrote a simple "hello world" C program compiled by android toolchain can be run on 8250 platform. The way I did was,1. cd ~/mydroid 2. prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/arm-eabi/bin/gcc test.c 3. copy a.out to my platform, and try to run it 4. the result is correct!
But I also try to compile my test.c with android's standard make way, the generated executable can be run on 8250 platform. 1. cd ~/mydroid/system/core 2. cp -a init test 3. cd test 4. edit Android.mk LOCAL_SRC_FILES:= test.c LOCAL_MODULE:= test 5. mm (from envsetup.sh) 6. it will generate test in ~/mydroid/out/target/product/generic/root 7. I tried to run the generated test on my platform, it produces segmentation fault (core dumped) as init did. So I guess the reason may be the linked libraries or it's thumb code? Regards, Mac 2008/11/12 kernel gick <[EMAIL PROTECTED]> > >> Although the gcc version is older than Android toolchain, it generates >> armv6 code instead of armv5 generated by android toolchain. >> >> Did android's toolchain be modified somewhere so you suggest to use this >> one? >> >> Thanks, >> Mac >> > > If MSM8250 can run armv5 code(qualcomm kernel) generated by android > toolchain, it will be easy to run android code on it, but if you try replace > android toolchain inside build with codesourcery toolchain, you can expect > lot of troubles while compiling android build. > > Thanks > Gicky > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
