Thanks Fadden will add that to the ANT Target I normally use..

Once, again thanks for your hard work

Fred Grott
http://mobilebytes.wordpress.com


PS for those following the thread my target now reads:


<target name="-obfuscate" depends="compile.incremental" >
                        <!-- In versions prior to 4.4 Peephole optimization was 
turned off
                             however in 4.4beta is now on and thus we
                             have turn off with the command of
                             -optimizations !code/simplification/cast
                             per Fadden also use
                             -allowaccessmodification -->
                        <proguard>
                          -libraryjars ${android.jar}: ${external-libs-folder}
                          -injars      ${out-classes-location}
                          -outjars     ${obfuscate-location}/classes.min.jar
                          -keep public class * extends android.app.Activity
                          -optimizations !code/simplification/cast
                          -allowaccessmodification
                        </proguard>



                </target>





On Jul 27, 4:03 pm, fadden <[email protected]> wrote:
> On Jul 25, 8:33 am, "Fred Grott(shareme)" <[email protected]>
> wrote:
>
> > ahem Proguard even has direction on now to get it to work with
> > Andorid..
> [...]
> > Hint, one new proguard feature you have to set to false..
>
> For now. :-)
>
> In a future release the bytecode verifier will recognize that e.g. the
> value resulting from shifting an integer right 24 times is a byte, and
> hence no explicit int-to-byte conversion is necessary.  This should
> remove the need to disable code/simplification/cast in 4.4.
>
> The Dalvik verifier is still pickier about integer widths than some
> other VMs, so it's possible that there will be some optimizations that
> just won't be allowed.  We'll do all the reasonable ones though. :-)
> As you found, ProGuard's configuration is pretty easy to manage once
> you figure out why the VM is unhappy.
>
> Somebody else found that, if you crank up the obfuscation options, you
> may need -allowaccessmodification to avoid some access complaints, and
> you shouldn't use -mergeinterfacesaggressively because it can make the
> VM's head explode.
--~--~---------~--~----~------------~-------~--~----~
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