rik/jlibcom
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SF 1580993 Feature Request tied to https://sourceforge.net/forum/forum.php?thread_id=1588018&forum_id=375946 Help discusson adds support for 64 bit dlls.

Browse Source
This commit is contained in:
clay_shooter
2006-10-20 02:55:06 +00:00
parent e56c4f5e5d
commit 719ea199bd
27 changed files with 481 additions and 273 deletions
Download Patch File Download Diff File Expand all files Collapse all files

93
docs/HowToBuild.html → docs/BuildingJacobFromSource.html
View File

@@ -1,7 +1,31 @@
<HTML>
<BODY>
<h1> Overview </h1>
JACOB is built on windows machines using ANT, most commonly from inside of Eclipse.
The main steps for getting a working Jacob build are:
<ol>
<li>Check out the source code or unpack the source zip file from sourceforge</li>
<li>Install the Development Environment</li>
<li>Configure the build by creating a <i>compilation_tools.properties</i> file.</li>
<li>Run Eclipse and load the project into eclipse</li>
<li>Open the build.xml file in Eclipse and run the default ant target </li>
</ol>
<p>
<h1> Repository Organization </h1>
<p>
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.<br>
Code is compiled into .\release<br>
<p>
The Servlet examples that required j2ee libraries to compile have temporarily
been removed.
<p>
<H1>Development Environment</h1>
The simplest installation involves MS Visual C++ 6.0, Eclipse 3.1 and JDK 1.4.
The simplest build environment involves MS Visual C++ 6.0, Eclipse 3.1 and JDK 1.4.
In that situation, you would just create the <i>compilation_tools.properties</i>
using the example build.xml as a template. All of the releases, up through 1.11,
were built using Visual C++ 6.0.
@@ -10,8 +34,24 @@ were built using Visual C++ 6.0.
<li> Eclipse 3.1 or later from www.eclipse.org.
<li> Java JDK 1.4 (this was built using 1.4.2.09)
</ul>
<p>
64 bit builds are supported with release 1.11. Tools required for 64 bit builds
include:
<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 (installed in D:\apps in my case)
<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>
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.
@@ -46,45 +86,26 @@ 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.
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:
<p>
Open up the project properties and go to the "Java Build Path" properties panel.
<ul>
<li> Eclipse automatically adds the whole project as a source directory
<li> Remove the root of the project from the build path
<li> Add folders samples, src and unittest to the build path
<li> Exclude *.txt from each of the newly added folders.
<li> Remove the root of the project from the build path</li>
<li> Add folders <code>samples</code>, <code>src</code> and <code>unittest</code>
to the build path in the Source tab.</li>
<li> Exclude *.txt from each of the newly added folders. </li>
<li> Set the build output directory to <code>jacob-project/release/java</code></li>
</ul>
<h1> Repository Organization </h1>
<p>
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.
<p>
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>
<h1> Running Samples and Tests </h1>
Samples and 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.
Last Modified 10/2005

16
docs/ReleaseNotes.html
View File

@@ -76,6 +76,10 @@
</tr>
<tr>
<td width="100%" colspan="2"><b>Feature Requests</b></td>
</tr>
<tr>
<td width="13%">1580993</td>
<td width="87%">Modify the build process to support 64 bit dll construction</td>
</tr>
<tr>
<td width="13%">1550628</td>
@@ -624,17 +628,17 @@ native code is replicated there from the jni directory...
<h2>Related Links</h2>
<ul>
<li>
The JACOB mailing list is hosted at yahoo groups:
<a href="http://groups.yahoo.com/group/jacob-project">
http://groups.yahoo.com/group/JACOB-project</a>.
The best way to get support or the latest version of JACOB is on
<a href="http://sourceforge.net/projects/jacob-project">
http://sourceforge.net/projects/jacob-project </a>
<b>This is the preferred way to get support for JACOB</b>. It also
includes an extensive archive. If you are doing any development with
JACOB, please join the list.
JACOB, please join sourceforge.
<li>
Massimiliano Bigatti has developed
<a href="http://www.bigatti.it/projects/jacobgen/">
<a href="http://sourceforge.net/projects/jacob-project">
JACOBgen - a generator that automatically creates JACOB code from
Type Libraries</a>
Type Libraries, now available on sourceforge</a>
</li>
<li>
Steven Lewis is developing a version of Java2Com that supports JACOB

45
docs/UsingJacob.html Normal file
View File

@@ -0,0 +1,45 @@
<HTML>
<BODY>
<h1> Determining the API of the target application </h1>
<p>
Section not yet written.
<p>
<hr>
<h1> Determining the API of the target application </h1>
<p>
Section not yet written.
<p>
<hr>
<h1>Jacob Command Line Settings</h1>
This library supports several different :
<h3>java.library.path</h3>
Used to add the location of the jacob dll to the JVM's library path.
<p>
Example: -Djava.library.path=d:/jacob/release/x86
<h3>com.jacob.autogc </h3>
Determines if automatic garbage collection is enabled. This is the
only way to free up objects created in event callbacks. This
feature is not fully debugged.
<p>
The default value is <strong>false</strong>
<p>
Example: -Dcom.jacob.autogc=false
<h3>com.jacob.debug</h3>
Determines if debug output is enabled to standard out.
The default value is <strong>false</strong>
<p>
Example: -Dcom.jacob.debug=false
<h3>-XCheck:jni</h3>
This turns on additional JVM checking for JNI issues. This is
not strictly a JACOB system property.
<p>
The default is "no additional checking"
Example: -XCheck:jni
Last Modified 10/2005
</BODY>
</HTML>

3
docs/todo.txt
View File

@@ -1,3 +0,0 @@
1. Make everything check the current thread's mta-ness
2. Write more documentation
3. Get someone to help write the Javadoc