This is the mail archive of the
mailing list for the binutils project.
Re: .note.ABI-tag extension for Android
- From: nick clifton <nickc at redhat dot com>
- To: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
- Cc: binutils at sourceware dot org
- Date: Wed, 02 May 2012 16:10:55 +0100
- Subject: Re: .note.ABI-tag extension for Android
- References: <1334964688.23845.3.camel@hactar>
I'm discussing with Google engineers about adding a .note.ABI-tag to
Android binaries, and extending the note format to allow identifying an
Why not use the ELF header for this ? You have the ei_osabi value in
the e_ident field for example which is already used to encode different
flavours of Linux.
Of course this does not provide much room to defined the Android API in
I arbitrarily chose os_variant = 1 to mean Android.
So the idea is that if desc size is>= 20, then the fifth 32-bit word
will be examined. If it is 1, then this is an Android ELF file. The
sixth word will then tell you the API level the application expects.
Are there a large number of Android APIs ? I am wondering if it is
necessart to have two new 32-bit fields, or whether it would be more
efficient to combine them into just one ?