Problems with obfusctaion [message #30947] |
Fri, 05 June 2009 09:57  |
Eclipse User |
|
|
|
Hi!
I have installed Eclipse 3.4.2 with mtj 1.0 RC3. Seems to work fine and I
can run my midlet in the emulator, debug it and create a signed package.
But when I try to create an obfuscated package I get the following error:
Errors during build.
Errors running builder 'Package Builder' on project 'XXXX'.
Failed to inflate jar file.
C:\ver9.00\Source\XXXX\.mtj.tmp\emulation\XXXX_obf.jar (The system
cannot find the file specified)
There is of course np XXXX_obf.jar. A proguard.conf file is created with
the following content:
-libraryjars
C:\S60\devices\S60_3rd_FP2_SDK_v1.1\lib\eswt.jar;C:\S60\devi ces\S60_3rd_FP2_SDK_v1.1\lib\JSR135.jar;C:\S60\devices\S60_3 rd_FP2_SDK_v1.1\lib\JSR139.jar;C:\S60\devices\S60_3rd_FP2_SD K_v1.1\lib\JSR172.jar;C:\S60\devices\S60_3rd_FP2_SDK_v1.1\li b\JSR177.jar;C:\S60\devices\S60_3rd_FP2_SDK_v1.1\lib\JSR179. jar;C:\S60\devices\S60_3rd_FP2_SDK_v1.1\lib\JSR180.jar;C:\S6 0\devices\S60_3rd_FP2_SDK_v1.1\lib\JSR184.jar;C:\S60\devices \S60_3rd_FP2_SDK_v1.1\lib\JSR226.jar;C:\S60\devices\S60_3rd_ FP2_SDK_v1.1\lib\JSR234.jar;C:\S60\devices\S60_3rd_FP2_SDK_v 1.1\lib\JSR75.jar;C:\S60\devices\S60_3rd_FP2_SDK_v1.1\lib\JS R82.jar;C:\S60\devices\S60_3rd_FP2_SDK_v1.1\lib\midp20.jar;C :\S60\devices\S60_3rd_FP2_SDK_v1.1\lib\midp21.jar;C:\S60\dev ices\S60_3rd_FP2_SDK_v1.1\lib\wma11.jar;C:\S60\devices\S60_3 rd_FP2_SDK_v1.1\lib\wma20.jar
-injars C:\ver9.00\Source\XXXX\.mtj.tmp\emulation\XXXX.jar
-outjar C:\ver9.00\Source\XXXX\.mtj.tmp\emulation\XXXX_obf.jar
-printseeds C:\ver9.00\Source\XXXX\deployed\pro_seeds.txt
-printmapping C:\ver9.00\Source\XXXX\deployed\pro_map.txt
-dontusemixedcaseclassnames -dontnote -defaultpackage ''
-keep public class * extends javax.microedition.midlet.MIDlet
The XXXX.jar file exists, but none of the others. I Use proguard 4.3 and
have set the 'Proguard Root Directory' in Window/Preferences/Java
ME/Packaging/Obfuscation. When I try the parameters in Proguard GUI the
obfuscation completes successfully.
I have tried adding -vmargs -Dmtj.build.logging=all on Eclipse startup
parameters, but I don't get any additional information really. I don't
think proguard is run at all. I have tried with Proguard 4.2 also, but
that does not help. I have also tried other WTK's but there is no
difference.
What could be the problem? Is there some way to verify that Proguard is
installed correctly and can be started from Eclipse? I am really stuck on
this...
Erik
|
|
|
|
|
|
|
Re: Problems with obfusctaion [message #573857 is a reply to message #30947] |
Sat, 06 June 2009 08:37  |
Eclipse User |
|
|
|
Hello Erick,
Could you try to run proguard on the command line as follows and tell us
what happens!?
java -jar <path/to/proguard/home>/lib/proguard.jar @<path/to>/proguard.conf
Regards,
David Marques
erik wrote:
> Hi!
> I have installed Eclipse 3.4.2 with mtj 1.0 RC3. Seems to work fine and I
> can run my midlet in the emulator, debug it and create a signed package.
> But when I try to create an obfuscated package I get the following error:
> Errors during build.
> Errors running builder 'Package Builder' on project 'XXXX'.
> Failed to inflate jar file.
> C:ver9.00SourceXXXX.mtj.tmpemulationXXXX_obf.jar (The system
> cannot find the file specified)
> There is of course np XXXX_obf.jar. A proguard.conf file is created with
> the following content:
> -libraryjars
>
C:S60devicesS60_3rd_FP2_SDK_v1.1libeswt.jar;C:S60devicesS60_ 3rd_FP2_SDK_v1.1libJSR135.jar;C:S60devicesS60_3rd_FP2_SDK_v1 .1libJSR139.jar;C:S60devicesS60_3rd_FP2_SDK_v1.1libJSR172.ja r;C:S60devicesS60_3rd_FP2_SDK_v1.1libJSR177.jar;C:S60devices S60_3rd_FP2_SDK_v1.1libJSR179.jar;C:S60devicesS60_3rd_FP2_SD K_v1.1libJSR180.jar;C:S60devicesS60_3rd_FP2_SDK_v1.1libJSR18 4.jar;C:S60devicesS60_3rd_FP2_SDK_v1.1libJSR226.jar;C:S60dev icesS60_3rd_FP2_SDK_v1.1libJSR234.jar;C:S60devicesS60_3rd_FP 2_SDK_v1.1libJSR75.jar;C:S60devicesS60_3rd_FP2_SDK_v1.1libJS R82.jar;C:S60devicesS60_3rd_FP2_SDK_v1.1libmidp20.jar;C:S60d evicesS60_3rd_FP2_SDK_v1.1libmidp21.jar;C:S60devicesS60_3rd_ FP2_SDK_v1.1libwma11.jar;C:S60devicesS60_3rd_FP2_SDK_v1.1lib wma20.jar
> -injars C:ver9.00SourceXXXX.mtj.tmpemulationXXXX.jar
> -outjar C:ver9.00SourceXXXX.mtj.tmpemulationXXXX_obf.jar
> -printseeds C:ver9.00SourceXXXXdeployedpro_seeds.txt
> -printmapping C:ver9.00SourceXXXXdeployedpro_map.txt
> -dontusemixedcaseclassnames -dontnote -defaultpackage ''
> -keep public class * extends javax.microedition.midlet.MIDlet
> The XXXX.jar file exists, but none of the others. I Use proguard 4.3 and
> have set the 'Proguard Root Directory' in Window/Preferences/Java
> ME/Packaging/Obfuscation. When I try the parameters in Proguard GUI the
> obfuscation completes successfully.
> I have tried adding -vmargs -Dmtj.build.logging=all on Eclipse startup
> parameters, but I don't get any additional information really. I don't
> think proguard is run at all. I have tried with Proguard 4.2 also, but
> that does not help. I have also tried other WTK's but there is no
> difference.
> What could be the problem? Is there some way to verify that Proguard is
> installed correctly and can be started from Eclipse? I am really stuck on
> this...
> Erik
|
|
|
Re: Problems with obfusctaion [message #573889 is a reply to message #30980] |
Mon, 08 June 2009 03:08  |
Eclipse User |
|
|
|
Hi David!
When i run proguard from the command line it works fine. It prints a lot
of output on the screen, creates the _obf.jar and the two text files.
BTW there was an error in my first post, the configuration file name is
proguard.cfg, not proguard.conf.
Erik
|
|
|
Re: Problems with obfusctaion [message #573912 is a reply to message #31016] |
Mon, 08 June 2009 09:12  |
Eclipse User |
|
|
|
Hi Erik,
I reproduced what you have described but i did not get the error you
reported. Is the project folder under any kind of source control system ?
Could you attach your project so we can trace what is happening ? Have you
tried to create an obfuscated package with another SDK ?
Regards,
David Marques
erik wrote:
> Hi David!
> When i run proguard from the command line it works fine. It prints a lot
> of output on the screen, creates the _obf.jar and the two text files.
> BTW there was an error in my first post, the configuration file name is
> proguard.cfg, not proguard.conf.
> Erik
|
|
|
|
Powered by
FUDForum. Page generated in 0.04824 seconds