| 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> |
|---|
| 2 | |
|---|
| 3 | <html> |
|---|
| 4 | |
|---|
| 5 | <head> |
|---|
| 6 | <title>J User's Guide - Building the Source</title> |
|---|
| 7 | <LINK REL="stylesheet" HREF="j.css" TYPE="text/css"> |
|---|
| 8 | </head> |
|---|
| 9 | |
|---|
| 10 | <body> |
|---|
| 11 | |
|---|
| 12 | <a href="contents.html">Top</a> |
|---|
| 13 | |
|---|
| 14 | <hr> |
|---|
| 15 | |
|---|
| 16 | <h1>Building the Source</h1> |
|---|
| 17 | |
|---|
| 18 | <hr> |
|---|
| 19 | |
|---|
| 20 | <p> |
|---|
| 21 | <b>Using configure and make</b> |
|---|
| 22 | <p> |
|---|
| 23 | This is the recommended build system on Unix platforms. On Windows, you are |
|---|
| 24 | more likely to succeed with Ant; see <a href="#Using_Ant">below</a>. |
|---|
| 25 | <p> |
|---|
| 26 | For Linux: |
|---|
| 27 | |
|---|
| 28 | <pre> |
|---|
| 29 | $ ./configure --with-jdk=DIR |
|---|
| 30 | $ make |
|---|
| 31 | $ make install |
|---|
| 32 | </pre> |
|---|
| 33 | |
|---|
| 34 | The <code>--with-jdk</code> option is <b>always</b> required, |
|---|
| 35 | in order to specify which JDK to use (give the full path of its top-level directory). |
|---|
| 36 | <p> |
|---|
| 37 | On Mac OS X, the --with-jdk option should be specified like this: |
|---|
| 38 | <pre> |
|---|
| 39 | --with-jdk=/System/Library/Frameworks/JavaVM.framework |
|---|
| 40 | </pre> |
|---|
| 41 | <p> |
|---|
| 42 | You can use the <code>--with-extensions</code> option to specify extensions to |
|---|
| 43 | the <code>CLASSPATH</code>. For example, you may want to build j with support |
|---|
| 44 | for an external XML parser: |
|---|
| 45 | <pre> |
|---|
| 46 | $ ./configure ... --with-extensions=/usr/share/java/xerces.jar |
|---|
| 47 | </pre> |
|---|
| 48 | Extensions specified in this way are added to the <code>CLASSPATH</code> both |
|---|
| 49 | during the build process and at runtime. |
|---|
| 50 | <p> |
|---|
| 51 | <a name="jpty"></a>If you want to use certain experimental features such as |
|---|
| 52 | shell and ssh buffers, you should specify the <code>--enable-jpty</code> option |
|---|
| 53 | (you will also need to set <code>enableExperimentalFeatures=true</code> in your |
|---|
| 54 | <a href="preferences.html">preferences</a> file). |
|---|
| 55 | <p> |
|---|
| 56 | By default, j will be installed in /usr/local/bin. |
|---|
| 57 | <p> |
|---|
| 58 | After you've built and installed j, you should be able to invoke it from the |
|---|
| 59 | command line by just typing |
|---|
| 60 | <pre> |
|---|
| 61 | $ j |
|---|
| 62 | </pre> |
|---|
| 63 | if /usr/local/bin is in your path. |
|---|
| 64 | <p> |
|---|
| 65 | <b><a name="Using_Ant">Using Ant</a></b> |
|---|
| 66 | <p> |
|---|
| 67 | <a href="http://jakarta.apache.org/ant">Ant</a> is the recommended build system |
|---|
| 68 | on Windows. Version 1.4.1 or later of Ant is required. |
|---|
| 69 | <p> |
|---|
| 70 | Change into the root directory of the j source distribution and edit the file |
|---|
| 71 | build.properties to suit your situation. Then: |
|---|
| 72 | <pre> |
|---|
| 73 | C:\j-0.21.0> ant all |
|---|
| 74 | </pre> |
|---|
| 75 | This will build j.jar and generate a batch file, j.bat, that you can use to |
|---|
| 76 | launch j. |
|---|
| 77 | </body> |
|---|
| 78 | </html> |
|---|
