On Wed, Jul 29, 2009 at 1:35 PM, Prasanth Kammampati <[email protected]>wrote:
> Hello, > > I have one doubt regarding the ABI compatibility of the binaries generated > in Android. Are they ARM ABI compatible. In the sense, can I link a library > generated using RVCT compiler with and Android application without > any issues? > It depends on how you configured RVCT to generate the binaries. The ARM "EABI" standard is really a family of different ABIs which differ in subtle details (e.g. are enums at least 8 or 32 bits in size, what is the size of wchar_t, etc...). If I remember correctly, Android 1.5 uses the "aapcs" ABI implementation, this matches the arm-eabi-non-linux implementation except that we don't use 32-bit wchar_t (wchar_t is not supported by Android anyway). Also note that GCC 4.4 for ARM changed the C++ mangling of the va_list type to better match the official ARM ABI, so technically it generates C++ code that is very slighyl incompatible with previous versions of GCC. > As I found in the earlier discussions, Android ABI is not compatible with > GNU ABI. But, Is it compatible with ARM ABI? > > Thanks & Regards, > Prasanth K > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
