Home | History | Annotate | Download | only in manual
      1 <!doctype html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
      2 <html>
      3 <head>
      4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
      5 <meta http-equiv="content-style-type" content="text/css">
      6 <link rel="stylesheet" type="text/css" href="style.css">
      7 <title>ProGuard JME Wireless Toolkit Integration</title>
      8 </head>
      9 <body>
     10 
     11 <h2>JME Wireless Toolkit Integration</h2>
     12 
     13 <b>ProGuard</b> can be seamlessly integrated in Sun's Wireless Toolkit (WTK)
     14 for Java Micro Edition (JME).
     15 <p>
     16 
     17 The WTK already comes with a plug-in for ProGuard. Alternatively, ProGuard
     18 offers its own plug-in. This latter implementation is recommended, as it more
     19 up to date and it solves some problems. It is also somewhat more efficient,
     20 invoking the ProGuard engine directly, instead of writing out a configuration
     21 file and running ProGuard in a separate virtual machine.
     22 <p>
     23 
     24 In order to integrate this plug-in in the toolkit, you'll have to put the
     25 following lines in the file
     26 {j2mewtk.dir}<code>/wtklib/Linux/ktools.properties</code> or
     27 {j2mewtk.dir}<code>\wtklib\Windows\ktools.properties</code> (whichever is
     28 applicable).
     29 <p>
     30 
     31 <pre>
     32 obfuscator.runner.class.name: proguard.wtk.ProGuardObfuscator
     33 obfuscator.runner.classpath: /usr/local/java/proguard/lib/proguard.jar
     34 </pre>
     35 <p>
     36 
     37 Please make sure the class path is set correctly for your system.
     38 <p>
     39 
     40 Once ProGuard has been set up, you can apply it to your projects as part of
     41 the build process. The build process is started from the WTK menu bar:
     42 <p>
     43 <center><b>Project -> Package -> Create Obfuscated Package</b></center>
     44 <p>
     45 This option will compile, shrink, obfuscate, verify, and install your midlets
     46 for testing.
     47 <p>
     48 Should you ever need to customize your ProGuard configuration for the JME WTK,
     49 you can adapt the configuration file <code>proguard/wtk/default.pro</code>
     50 that's inside the <code>proguard.jar</code>.
     51 
     52 <hr>
     53 <address>
     54 Copyright &copy; 2002-2009
     55 <a href="http://www.graphics.cornell.edu/~eric/">Eric Lafortune</a>.
     56 </address>
     57 </body>
     58 </html>
     59