Thank you all for your response. Can you please clarify the following -
1) When building a component using RVCT, to work with GLIBC, a '-sysv' option is used (http://infocenter.arm.com/help/index.jsp?topic=/ com.arm.doc.dai0212a/CHDCIBCA.html). I assume, this option guides RVCT to generate a binary compatible with GLIBC. But will this binary be compatible with BIONIC LIBC? 2) Also, since BIONIC uses its own ld.so, can this load the RVCT generated libraries dynamically? 3) My question is actually, if (i) RVCT can interwork with GLIBC and (ii) BIONIC cannot interwork with GLIBC, how can (iii) RVCT generated library interwork with BIONIC LIBS? Thanks & Regards, Prasanth K On Jul 30, 1:20 am, David Turner <[email protected]> wrote: > 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- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
