updates for 1.11

This commit is contained in:
clay_shooter
2006-10-16 02:16:48 +00:00
parent a7668bfadd
commit e56c4f5e5d

View File

@@ -11,51 +11,43 @@ were built using Visual C++ 6.0.
<li> Java JDK 1.4 (this was built using 1.4.2.09)
</ul>
<p>
A more complicated set up would involve:
<UL>
<li> Microsoft Visual Studio 2005 Express, available from the MS web site.<BR>
if you get an <b>mspdb80.dll not found</b> then you didn't set the environment variables
%PATH% during the install. You can either add the Common\IDE directory to your path in
the EnvironmentVariables configuration panel or you can do a quick hack (like I did).
You can just copy Common7\IDE\*.dll to VC\bin.
<li> Microsoft SDK with the following components
<ul>
<li>Windows Core SDK
<li>Microsoft Web Workshop (IE) SDK is required because it is referenced in atlbase.h
<li>(optional) Some folks also install the Debugging tools.
</ul>
<li> Eclipse 3.1 or later from www.eclipse.org.
<li> Java JDK 1.4 (this was built using 1.4.2.09)
</ul>
Compilation using JDK 1.5 has not been tested
<H1>Build Process</H1>
This project has been converted completely from MAKE to ANT. You can
run ANT from inside of eclipse or from the command line.
The build process is based on ANT. It cannot be built using MAKE.
You can run ANT from inside of eclipse or from the command line.
The ant process is driven off of a configuration file named
<i>compilation_tools.properties</i> 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.
<p>
Running ANT via build.xml will do the following with the default target.
There are two main ant targets.
<UL>
<li> Build the Java code
<li> Build the jni code
<li> create the dll
<li> create jar file
<li>"default" executes the following steps when using the default target.
<UL>
<li> Build the Java code
<li> Build the jni code
<li> create the dll
<li> create jar file
</UL>
<li>"package" runs the above listed steps and then
<UL>
<LI>builds the javadoc
<LI>builds a source zip
<li>builds a binary zip with the javadoc
</UL>
</UL>
Running the "package" ANT target runs the above listed steps and then
builds the javadoc and then the zip files.
<p>
<H1>Eclipse Java IDE</h1>
<p>
Eclipse users will have to do some minor tweaks to their project if they
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. A couple small tweaks to the build path
fix this problem.
<ul>
<li> Eclipse automatically adds the whole project as a source directory
@@ -66,7 +58,9 @@ the project source files themselves are in "src" the root directory.
<h1> Repository Organization </h1>
<p>
Unpack the source archive or check the files out of CVS into d:\jacob
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 seperate
packages from the unit tests and the samples.
<p>
The java code is in .\src.<BR>
The C++ code is in .\jni.
@@ -74,6 +68,24 @@ The C++ code is in .\jni.
The Servlet examples that required j2ee libraries to compile have temporarily
been removed.
<p>
<h1> 64 bit build support </h1>
<p>
<B>64 bit builds are not supported at this time</b>
<p>
A 64 bit build would involve:
<UL>
<li> Microsoft Visual C++ 6.0 and it's included library. (installed in D:\apps in my case)
<li> Microsoft SDK 2005R2 with the following components
<ul>
<li>Windows Core SDK
<li>Microsoft Web Workshop (IE) SDK is required because it is referenced in atlbase.h
<li>(optional) Some folks also install the Debugging tools.
</ul>
<li> Eclipse 3.1 or later from www.eclipse.org.
<li> Java JDK 1.4 (this was built using 1.4.2.09)
</ul>
Last Modified 10/2005
</BODY>