On 06/29/2011 10:33 PM, Nick Copeland wrote:
I don't know what syscall you are talking about.
When you build with the android NDK, you can choose to compile for armeabi, for
armeabi-v7a or for both. If you only build for the later, then your app is not
visible to non ARMv7 devices on the market. I can't remember what happens if you
try to install the APK manually on an ARMv5 device, but I think this fails or
If the app's built for both ABIs, then the package installer installs the proper
set of libraries provided by your app, either armeabi or armeabi-v7a depending
on the hardware.
Also, there's a small library provided by the NDK, called cpu-features, which
allows you to detect CPU features at run time. I used that and rely on it to
activate certain features. It works great.
>> > The ARM
AFAIK, on Android, there's no such thing as executing FPU instructions on
devices without an FPU, unless you are doing something very weird.
This 1000 factor and the syscalls you mention is something I never heard about,
which is maybe true in general about ARM, but which doesn't happen in practice
on Android, if you use the standard build tools and OS.
That said, a factor of 10 or 20 is enough for me to call it insane, yes :p
>> You got an FPU on most devices, you can compile for hard floats,
Okay, right, that's interesting. But, well, you got plenty of FPUs out there,
and you just need a single line in a makefile to use them. That was my point.
Linux-audio-dev mailing list