It's the difference between target and min sdk in your manifest. As
long as you have min set to 3, it'll deploy fine to 1.5 devices; the
unknown xml elements and attributes will just be ignored.

String

On Aug 13, 5:38 pm, Fabrizio Giudici <[email protected]>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 8/13/10 18:00 , Lance Nanek wrote:
>
> > You can have a build target higher than Android 1.5, but still
> > specify Android 1.5 support in the android:minSdkVersion attribute
> > of the uses- sdk element.
>
> It's the thing described in "Supporting legacy..." in Android docs,
> right? I hoped to avoid that, but I don't see other solutions.
>
> - --
> Fabrizio Giudici - Java Architect, Project Manager
> Tidalwave s.a.s. - "We make Java work. Everywhere."
> java.net/blog/fabriziogiudici -www.tidalwave.it/people
> [email protected]
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkxldPgACgkQeDweFqgUGxeBEwCgj1UV7YUIlCaowfamyqtb+VDN
> 1j0AnRKXCjFksS/HM6HUObGA/arhEK0V
> =/95c
> -----END PGP SIGNATURE-----

-- 
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

Reply via email to