What you are doing is switching between the different platform versions as a target. If you want to build with 1.6 features but still target 1.5, then build against 1.6 and set minSdkVersion to 3 (and of course make sure you actually run on 1.5).
On Mon, Oct 19, 2009 at 2:12 PM, polyclefsoftware <[email protected]> wrote: > > Here's the problem I'm running into: > > I'm using a resource directory qualifier (e.g. "res/drawable-hdpi/"). > Per the documentation's suggestion, I set the android:minSdkVersion to > "3" and the android:targetSdkVersion to "4". In Eclipse, if I set the > Project Build Target to Android 1.5, I get an error regarding the new > resource directory ("invalid resource directory name") and the project > won't compile. If I set the Project Built Target to Android 1.6, it > builds just fine, but then I can't run the app in the 1.5 emulator. > > > On Oct 19, 2:11 pm, Lance Nanek <[email protected]> wrote: > > Wouldn't an update written using the 1.6 SDK still be available to > > users on 1.5 as long as you set the android:minSdkVersion attribute on > > the uses-sdk element in the manifest to 3? > > > > I know this works fine on the emulator with a 1.5 image, at least, > > since that is one of the tests I ran after adding small screen layout > > directories to one of my apps. > > > > On Oct 19, 11:47 am, polyclefsoftware <[email protected]> wrote: > > > > > > > > > So I'm trying to make sure my apps are compatible with the 1.6 SDK > > > emulator skins WVGA800 and WVGA854. > > > > > The Android Developers Blog post regarding this seems strange to me. > > > The post talks about upgrading your app using the 1.6 SDK, then says > > > this: > > > > > "Note that not all devices will be upgraded to Android 1.6 at the same > > > time. There will be significant number of users still with Android 1.5 > > > devices. To use the same apk to target Android 1.5 devices and Android > > > 1.6 devices, build your apps using Android 1.5 SDK and test your apps > > > on both Android 1.5 and 1.6 system images to make sure they continue > > > to work well on both types of devices." > > > > > Now resource directory qualifiers (e.g. "res/drawable-mdpi/" or "res/ > > > layout-large") don't work with the 1.5 SDK. So right now as a dev I > > > have the choice to either: > > > > > 1) Update my apps with the 1.6 SDK so that they are compatible with > > > the various 1.6 emulator skins and the various hardware configurations > > > coming out. If I do this, the updates will not be available to those > > > users that still have 1.5, which is a "significant number of users." > > > > > 2) Continue using the 1.5 SDK, without the available tools in 1.6, but > > > try to somehow get my app to render properly in the various 1.6 > > > emulator skins. > > > > > Is this about right? Is anyone else dealing with this right now? > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
