On Tue, Sep 13, 2011 at 8:12 PM, Tom <[email protected]> wrote: > This approach doesn't allow me to build against Android 2.1, though, > as adding android:hardwareAccelerated requires me to build against > android 3.0. I want to build against my min target sdk in order to > make sure no developers on my team (myself included) accidentally > refer to an API that isn't available in my min target sdk.
By going with this approach, you can't have hardware acceleration, or lots of other things added to Android in the last 18 months (e.g., customizing the action bar for Honeycomb+). If you have solid tests with solid code coverage, you will detect any inappropriate API usage even if you compile with the newer SDK. If you don't have such tests, you have much bigger problems than lacking hardware acceleration. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.6 Available! -- 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
