Android Build / Progard logs under Eclipse

I've been developing Adroid apps for a long time, but have always used the ANT command line model to create release versions.

I decided to use the eclispe EXPORT model to start building an Android APK and it seems to work.

However, whatever one may say, I can't see the logs from the build anywhere, so I'm not sure if the PROGUARD part on the build actually worked. The APK builds and appears to be signed, but I would feel more comfortable to be able to see the build output, specifically the proguard steps that would normally be part of the console output when built with ANT.

I open a console window in Eclipse when I select export and I can't see anything, and when I try to find logging information for Eclipse with Android I also don't find anything.

Where are sysout / build logs stored from export commands?

+3


source to share


2 answers


Using the normal Ant config dialogs and then running the normal targets for (Clean, Debug) I can see the DX output right in the eclipse console tab ... You will have the same general experience with target = release and the proguard step in the process.

  • Eclipse / external tools configuration
  • tab = target - select the targets you want to enable (clear, debug)
  • check the order of the task
  • start Ant and see the console ...

you will see proguard where dx is shown below if u starts the release target.



eclipse console:

       [dx] associated EnclosingMethod attribute. This class was probably produced by a
       [dx] compiler that did not target the modern .class file format. The recommended
       [dx] solution is to recompile the class from source, using an up-to-date compiler
       [dx] and without specifying any "-target" type options. The consequence of ignoring
       [dx] this warning is that reflective operations on this class will incorrectly
       [dx] indicate that it is *not* an inner class.
       [dx] warning: Ignoring InnerClasses attribute for an anonymous inner class
       [dx] (org.apache.commons.logging.LogFactory$6) that doesn't come with an
       [dx] associated EnclosingMethod attribute. This class was probably produced by a
       [dx] compiler that did not target the modern .class file format. The recommended
       [dx] solution is to recompile the class from source, using an up-to-date compiler
       [dx] and without specifying any "-target" type options. The consequence of ignoring
       [dx] this warning is that reflective operations on this class will incorrectly
       [dx] indicate that it is *not* an inner class.
       [dx] 2 warnings
-crunch:
   [crunch] Crunching PNG Files in source dir: C:\cygwin\home\rob\src\gpsclipper\res
   [crunch] To destination dir: C:\cygwin\home\rob\src\gpsclipper\bin\res
   [crunch] Crunched 0 PNG files to update cache
-package-resources:
     [aapt] Current build type is different than previous build: forced aapt run.
     [aapt] Creating full resource package...
-package:
     [echo] --apk outfldr:C:\cygwin\home\rob\src\gpsclipper\bin  resourcefile: gpsclipper.ap_
     [echo]             apkfilepath: C:\cygwin\home\rob\src\gpsclipper\bin\gpsclipper-debug-unaligned.apk  verbose: false
     [echo]              Dxpath: C:\cygwin\home\rob\src\gpsclipper\bin\classes.dex
     [echo]              srcFldrPth: C:\cygwin\home\rob\src\gpsclipper\src jarRFID: ${project.libraries.jars} 
     [echo]             nativeFldr: ${project.libraries.libs}
[apkbuilder] Current build type is different than previous build: forced apkbuilder run.
[apkbuilder] Creating gpsclipper-debug-unaligned.apk and signing it with a debug key...
-post-package:
-do-debug:
 [zipalign] Running zip align on final apk...
     [echo] Debug Package: C:\cygwin\home\rob\src\gpsclipper\bin\gpsclipper-debug.apk
[propertyfile] Updating property file: C:\cygwin\home\rob\src\gpsclipper\bin\build.prop
[propertyfile] Updating property file: C:\cygwin\home\rob\src\gpsclipper\bin\build.prop
[propertyfile] Updating property file: C:\cygwin\home\rob\src\gpsclipper\bin\build.prop
[propertyfile] Updating property file: C:\cygwin\home\rob\src\gpsclipper\bin\build.prop
-post-build:
debug:
-pre-clean:
clean:
   [delete] Deleting directory C:\cygwin\home\rob\src\gpsclipper\bin
   [delete] Deleting directory C:\cygwin\home\rob\src\gpsclipper\gen
BUILD SUCCESSFUL
Total time: 54 seconds

      

+1


source


in the workspace containing project information you will find the Proguard directory, this directory contains all the build logs and mapping that will give you information about what has been done and what the results are.



0


source







All Articles