So then I have last 3 questions: 1. if we add support the two platforms is the armeabi-v7a be automatically selected when available? 2. Is there a minimal API level that if we require the armeabi-v7a support will be there or they are completely different things? 3. If we support only armeabi-v7a and the app gets installed on a device with no support for it what are going to be the implications?
Thanks, Vladimir -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Pryor Sent: Tuesday, December 13, 2011 3:00 AM To: Discussions related to Mono for Android Subject: Re: [mono-android] Supported architectures? armeabi-v7a On Dec 12, 2011, at 5:24 PM, Vladimir Dimitrov wrote: > So does this mean that we should always enable armeabi-v7a in cases when we use a lot of multi threading and floating point operations? Maybe. Depends on the app. :-) > I guess the trade off in this case is that if we include both there will be a bigger .apk as a result? Anything else? That's pretty much it. Furthermore, given that armeabi is ancient, and even the API level 14 emulator is armeabi-v7a, there is a case to be made that armeabi doesn't need to be supported at all, leaving you with just armeabi-v7a in your .apk. (Furthermore, I have no idea how many devices this would actually exclude, Firefox Mobile made the choice to go with supporting only armeabi-v7a, so this isn't an entirely unheard of decision.) Either way, each libmonodroid.so is ~3MB in size, though this is compressed in the .apk to about 1.2MB, so you're looking at a minimum 1.2MB increase for each ABI you intend to support. - Jon _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
