Overview

JACOB is built on windows machines using ANT, most commonly from inside of Eclipse. The main steps for getting a working Jacob build are:
  1. Check out the source code or unpack the source zip file from sourceforge
  2. Install the Development Environment
  3. Configure the build by creating a compilation_tools.properties file.
  4. Run Eclipse and load the project into eclipse
  5. Open the build.xml file in Eclipse and run the default ant target

Repository Organization

Unpack the source archive zip file or check the files out of CVS into d:\jacob or some other familiar place. Source Java and JNI files are located in separate packages from the unit tests and the samples.

The Servlet examples that required j2ee libraries to compile have temporarily been removed.

Development Environment

The simplest build environment includes MS Visual Studio 10.0 (Studio 2010), Eclipse 3.3 with the C/C++ module and JDK 1.6. In that situation, you would just create the compilation_tools.properties using the example at the top of build.xml as a template.

ReleaseC VersionJava VersionANT VersionEclipse Version Usedgenerated DLLs
up to 1.6VC 98 (6.0)?MAKE?32 bit
1.7VC 98 (6.0)1.4 (48)1.??32 bit
1.8VC 98 (6.0)1.4 (48)1.??32 bit
1.9VC 98 (6.0)1.4 (48)1.??32 bit
1.10VC 98 (6.0)1.4 (48)1.?3.??32 bit
1.11VC 98 (6.0) & 2003 64bit libs1.4.? (48)1.6.?3.2.132 and 64 bit
1.12VC 98 (6.0) & 2003 64bit libs1.4.2 (48)1.6.53.2.232 and 64 bit
1.13VC 2005 (8)1.4.2 (48)1.7.03.332 and 64 bit
1.14VC 2005 (8)1.5.0 (49)1.7.03.332 and 64 bit
1.15VC 2005 (8)1.5.0 (49)1.7.03.432 and 64 bit
1.17VC 2005 (8)1.5.0 (49)1.8.4 Eclipse Embedded4.332 and 64 bit
1.18VS 2013 (12) Windows SDK 7.1A1.6.0 (50)1.8.4 Eclipse Embedded4.332 and 64 bit
Microsoft Visual Studio 13 supports 64 bit builds. so no additional tools are required.
Microsoft changed the location of the windows sdk (formerly known as platform sdk) after VC 8.0. https://en.wikipedia.org/wiki/Microsoft_Windows_SDK

Build Process

The build process is based on ANT. You can run ANT from inside of eclipse or from the command line. Running from inside eclipse means you don't have any installation, pathing or configuration to do. You can just open the xml, select the target in the "Outline" pane, right mouse and then "run as ant" on the selected target.

The ant process is driven off of a configuration file named compilation_tools.properties that describes the locations of the JDK and Microsoft C++ tools. The build.xml file in the root directory contains examples of the contents of this file.

There are two main ant targets.

Eclipse Java IDE

Eclipse users have to do some minor tweaks to their project if they want to use the integrated build process. This is because the unit tests are files located in the "unittest" directory while the project source files themselves are in "src" the root directory. By default, eclipse will add the entire project as source. This messes up the package naming. In addition, the build directory should be set to be the same place the ANT build puts the compiled java classes. A couple small tweaks to the build path fix these problems:

Open up the project properties and go to the "Java Build Path" properties panel.

Troubleshooting Build Problems

Running Samples and Tests

Samples and JUnit test programs can be found in the source jar or in CVS. The programs can be run from a bat file or from inside the Eclipse IDE. The java library path variable must be set to include the directory the jacob.dll is in. The simplest way to do that is to add it as a command line option. The following assume that your jacob development area is located in c:\dev\jacob:
	-Djava.library.path=c:/dev/jacob/release/x86 
	-Dcom.jacob.autogc=false 
	-Dcom.jacob.debug=false 
	-Xcheck:jni

JUnit test programs can be individually run from inside eclipse or en-masse via the ant test target. Last Modified 10/2008 1.15