On 15 April 2011 13:13, sblantipodi <[email protected]> wrote:
> > Ok, so you got the real reason :) In this case you have to use higher SDK > as > > I am not aware of any other trick you could use for Manifest to add new > > attribute and still be able to build against older SDK. > > > > I have the real reason yes but if this reason will "damage" backward > compatibility. I will prefer to forget this real reason. > No it won't. At least I do not see the chance assuming you will to do what you wrote you plan only. You are talking about obfuscation now or about compiling with SDK > Level 8 and maintain compatibility with Level 4? > Obfuscation got nothing to do with SDK level and got nothing to do with Android at all. It's matter of obfuscating *Java* bytecode. So if you target android you have to add ProGuard (or other obfuscator of choice) in your build (or rather publishing, to save time) process. ProGuard is not android-only tool, nor Eclipse dependant. You simply needs to hand it compiler output to chew and then hand its output further to produce dalvik compatible bytecode. Regards, Marcin Orlowski *Tray Agenda <http://bit.ly/trayagenda>* - keep you daily schedule handy... *Date In Tray* <http://bit.ly/dateintraypro> - current date at glance... WebnetMobile on *Facebook <http://webnetmobile.com/fb/>* and *Twitter<http://webnetmobile.com/twitter/> * -- 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
