On Feb 14, 12:25 pm, freakingtux <[email protected]> wrote: > Hello Howard, > > On Monday, February 14, 2011 5:33:16 PM UTC+1, Howard M. Harte wrote: > > > There is already support in the platform for this, I think from 1.6 > > and later. You make shared libraries using the appropriate NDK for > > each ABI you support, and during install, the appropriate shared > > library from your APK is installed on the device. Several of my apps > > support ARM, x86 (for Android-x86.org builds) and i386 for Google TV. > > There is an NDK available for Android-x86 and an unofficial one for > > Google TV. > > How did this workout for you in the past. Do you find it is much more > maintenance heavy compared to building for a single target?
It's not too bad, most of my code is in Java, so I don't update the native code too often. I build the ARM .so using the Windows version of the NDK, and the others using Linux. If I had to modify the native code often, I would probably do it all on Linux and write a Makefile to build the .so for all platforms and copy the libs to the correct places. Since everything is in a single APK, distribution is the same as usual, so that's not an issue. Of course, I need to test on each platform, so that takes time, but it not much more of a burden than the testing I already have to do on several phones, Galaxy Tab, Nook, etc. Having all platforms supported from a single NDK would be really nice, and when official NDKs are available for the different ABI's, I hope this will be the case, but the main benefit of that would probably be having less NDKs to install and maintain. -Howard -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
