When you compile you won't be able to use any APIs introduced after your target SDK.
It won't prevent your app from appearing on earlier devices, that's purely down to the your minimum SDK chosen. Of course make sure you test on the the minimum SDK you define - to check your app behavior and check you haven't used any APIs that were introduced in later versions. On Thu, Jul 15, 2010 at 9:32 PM, Pent <tas...@dinglisch.net> wrote: >> Why don't you just set your target sdk higher? >> > > I think this may be a 'doh' moment and going slightly off topic. I've > been building the cupcake version of my app with the project target 3 > because if I build it with a higher target eclipse shows a big red > cross there when going to install it on the device, which I had > assumed meant 'can't install'. > > I now tried it with project target 8 and it installed fine, also built > with Ant. > > But does it still appear on the Market for cupcake devices then ? Does > Market only look at what's stipulated in the manifest and ignore the > build target ? > > In any case, that solved the problem with not being able to specify > android:required="false". > > Pent > > -- > 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 -- 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
