Since you want to use a new attribute that requires SDK level 8 or higher, you will need to build against that SDK, older ones will give a compile (invalid tag) error.
Then to make sure your app also still runs fine on 1.6 you need to deploy it on a device with a level 4 SDK, or if not available, create a 1.6 AVD and run it on that one. The 1.6 runtime is just skipping the new attribute. I've read that this is the behaviour recently for the xlargeScreens attribute, but can't find it anymore :( Should you be using Android Java API features that were introduced after 1.6, then you need to make sure your code gracefully handles it when those features are not present. See for a good explanation on how to do this: http://android-developers.blogspot.com/2009/04/backward-compatibility-for-android.html HTH. On 15 apr, 11:57, sblantipodi <perini.dav...@dpsoftware.org> wrote: > > "Don't fix it until is broken". > > Ok, this is common but what is the real answer? :) > I would like to add this attribute to my manifest: > android:installLocation="preferExternal" > but this requires SDK Level 8 to build the source. > > Isn't safe to compile using Level 8 SDK only for this attribute and > than > run my apps on Level 4? > > > Obfuscation is not SDK dependant. > > I mean that from SDK 2.3 proguard has been integrated into the into > the SDK, this could be really useful for a > netbeans user like me. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
