Your approach sounds right. E.g., the following configuration will let
ProGuard remove Log calls:
-assumenosideeffects class android.util.Log {
<methods>;
}
The logging methods have return values, but that shouldn't matter if
your code ignores them.
If it doesn't work, you should make sure that
* you have specified the fully qualified class name,
* you haven't switched off optimizations,
* you haven't specified any conflicting -keep options that preserve
these methods.
If you have any questions, you can ask them on ProGuard's help forum.
Eric
--
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