This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Dear list, I build Android ROM from AOSP for mobile device, LG google nexus 4 (armv7-a). With android come several prebuilts/gcc/linux-86/arm toolchains named "arm-eabi-4.7" and "arm-linux-androideabi-4.7". I build my own toolchain which name is "arm-cortexa9_neon-linux-gnueabi" (cortex-a9) as CPU & TUNE and neon as FPU. I am a little confused about all these different names. The out folders from my built toolchaine are roughly similar to the androideabi prebuilt ones. Is the "gnueabi" and "androideabi" only a name specification (I understand android is not gnu) and a licence difference with same binaries/lib, or is there a real difference for the built outputs ? What about the arm-eabi ? Here again folders "look" quite similar to my toolchain, but why arm-eabi AND arm-linux-androideabi ? Thank you for sharing your knowledges. Regards. -- View this message in context: http://sourceware-org.1504.n7.nabble.com/arm-linux-androideabi-arm-eabi-arm-unknow-linux-gnueabi-tp234300.html Sent from the Sourceware - crossgcc list mailing list archive at Nabble.com. -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |