On Dec 13, 2011, at 3:50 AM, Vladimir Dimitrov wrote: > 1. if we add support the two platforms is the armeabi-v7a be automatically > selected when available?
Yes. If you have the Android NDK installed, see also docs/CPU-ARCH-ABIS.html §III.3. > 2. Is there a minimal API level that if we require the armeabi-v7a support > will be there or they are completely different things? They're mostly different things, though you do need Android 1.5 or later (and Mono for Android only runs on Android 1.6 or later...). > 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? I'm not actually sure, and I can't find any documentation addressing this on developer.android.com. One of two things are likely to happen: 1) The app won't be listed in the Android Marketplace within armeabi devices, because they can't support armeabi-v7a. 2) The app will be listed, installed, and will bomb at runtime because it won't be able to find a native library (because the native library won't be extracted at install time). (2) would be virtually indistinguishable from http://code.google.com/p/android/issues/detail?id=21670 What isn't listed in the bug report is the java.lang.UnsatisfiedLinkError that's thrown because libmonodroid.so couldn't be found... - Jon _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
