This buildfile is for compiling applications that use the Standard Widget Toolkit (SWT) from the Eclipse project (http://www.eclipse.org). This buildfile can compile applications in the following ways: 1. Compiling to native using GCJ linking to SWT library statically. 2. Compiling to native using GCJ linking to SWT dynamically (i.e. shared library). Note that this option is not currently supported on Windows hosts (as of GCJ 3.2). 3. Compiling to bytecode (i.e. .class) using the default system Java compiler. Note that if you would like to force the script to use GCJ for compilation to bytecode (instead of javac), supply the -Dbuild.compiler=gcj at the command line. This buildfile has been tested on Windows 2000, Windows XP, Red Hat Linux 6.2/Motif, Red Hat Linux 8.0/Motif, and Red Hat Linux 8.0/GNOME. This buildfile should work (but hasn't been tested) on the other UNIX systems supported by Eclipse (AIX, HP/UX, Solaris) on Motif. It may also work on QNX/Photon. This buildfile has the following parameters. You can either accept the default or provide your own value at the command-line (e.g. ant -Dfoo=bar). library_dir The location where your static or shared library resides. default: ${library_dir} link The linking method: static or dynamic. default: ${link} values: static, dynamic swt.jar The location of your SWT JAR file. This is an optional setting that is useful when running the build from Eclipse. When compiling, you either need to have the Eclipse SWT source code in your library_dir or set this property to point to a valid swt.jar. If you have the Eclipse SWT source code in your library_dir, you do not need to set this value. If not, set this value to point to a valid Eclipse swt.jar. Note that the file should be in a path that does not contain spaces. defaults: ${swt.jar} values: A swt.jar file e.g. /usr/local/eclipse/plugins/org.eclipse.swt.gtk_2.0. 1\ws\win32\swt.jar This buildfile also has the following targets that you might want to call: jar Calling this task will compile your application to bytecode and package it in a JAR. This task is useful if you'd like to run your application in a virtual machine. Note that if you would like to force the script to use GCJ for compilation to bytecode (instead of javac), supply the -Dbuild.compiler=gcj at the command- line. clean Deletes compiled class files, object code (i.e. .o), and library files; thus allowing you to do a clean build. Examples: Build using a shared library: ant -Dlink=dynamic Build using a shared library with an alternate library directory: ant -Dlibrary_dir=/usr/lib -Dlink=dynamic Compile your application natively from within Eclipse: ant -Dswt.jar=..\..\plugins\org.eclipse.swt.win32_2.0. 1\ws\win32\swt.jar Compile your application to a JAR file: ant jar