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

Upadted Docs for 1.12 pre-3

Browse Source
This commit is contained in:
clay_shooter
2007-03-25 13:43:40 +00:00
parent d2777b692e
commit 2d08b9e43a
2 changed files with 26 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
build.xml
View File

@@ -1,41 +1,41 @@
<?xml version="1.0"?> <?xml version="1.0"?>
<!-- ====================================================================== <!-- ======================================================================
Ant build file for JACOB. Ant build file for JACOB.
Created Feb 4, 2005 1:23:05 PM as part of migration from ANT Created Feb 4, 2005 1:23:05 PM as part of migration from ANT
Last Modified October 13, 2005 Last Modified March 24, 2007
Tested on Eclipse 3.2 with the Callisto plugis, Ant 1.6.1 and MS Visual C++ 6.0 Tested on Eclipse 3.2 with the Callisto plugis, Ant 1.6.1 and MS Visual C++ 6.0
Eclipse users are pretty lucky because the whole project Eclipse users are pretty lucky because the whole project
can be built inside eclipse due to their built in ANT support. can be built inside eclipse due to their built in ANT support.
Developers will need to find a copy of MS Visual C++ 6.0. The COM portion of this build requires MS Visual C++ 6.0.
The build proces defined in this build.xml file does support The build proces defined in this build.xml file does not support
MS Visual C++ 8.0 (Visual C++ 2005 Express) when combined with the M SDK. MS Visual C++ 8.0 (Visual C++ 2005 Express) when combined with the MS SDK.
The problem is that SafeArray.cpp will not compile The problem is that SafeArray.cpp will not compile because some of the
with that more advanced (and 64 bit aware) environment. types have changed sizes in the newer 64bit aware world.
YOU MUST define a file named compilation_tools.properties! YOU MUST define a file named compilation_tools.properties!
The file for MS Visual C++ 6.0 building only the 32 bit version The file for MS Visual C++ 6.0 building only the 32 bit version
(the only version available through 1.11) looks something like: (releases up to 1.11 only supported 32 builds) looks something like:
JDK=d:/j2sdk1.4.2_13 JDK=d:/j2sdk1.4.2_13
MSDEVDIR=d:\\apps\\Microsoft Visual Studio\\VC98 MSDEVDIR=d:\\apps\\Microsoft Visual Studio\\VC98
version=1.11-pre2 version=1.11-pre2
Construction with 64 bit support requires the MS Platform SDK. Construction with 64 bit support requires the MS Platform SDK.
compilation_tools.properties in this situation should look compilation_tools.properties in this situation should look
something like: something like:
JDK=d:/j2sdk1.4.2_13 JDK=d:/j2sdk1.4.2_13
MSDEVDIR=d:\\apps\\Microsoft Visual Studio\\VC98 MSDEVDIR=d:\\apps\\Microsoft Visual Studio\\VC98
MSSDKDIR=D:\\Apps\\Microsoft Platform SDK for Windows Server 2003 R2 MSSDKDIR=D:\\Apps\\Microsoft Platform SDK for Windows Server 2003 R2
version=1.11-pre2 version=1.11-pre2
DO NOT check compilation_tools.properties into source control as the DO NOT check compilation_tools.properties into source control as the
values are specific to YOUR environment. values are specific to YOUR environment.
the version.properties file is now completely autogenerated The version.properties file is now completely autogenerated
====================================================================== --> ====================================================================== -->
<project name="jacob" default="default" basedir="."> <project name="jacob" default="default" basedir=".">
@@ -92,6 +92,8 @@
<property name="include.x86.atl" value="${MSDEVDIR}\atl\include" /> <property name="include.x86.atl" value="${MSDEVDIR}\atl\include" />
<property name="library.x86" value="${MSDEVDIR}\lib" /> <property name="library.x86" value="${MSDEVDIR}\lib" />
<!-- You have to love the beautiful asymetry of the MS world -->
<!-- The platform SDK comes with 64 bit tools but not 32 bit tools -->
<property name="compiler.AMD64" value="${MSSDKDIR}\bin\win64\x86\AMD64\cl.exe" /> <property name="compiler.AMD64" value="${MSSDKDIR}\bin\win64\x86\AMD64\cl.exe" />
<property name="linker.AMD64" value="${MSSDKDIR}\bin\win64\x86\AMD64\link.exe" /> <property name="linker.AMD64" value="${MSSDKDIR}\bin\win64\x86\AMD64\link.exe" />
<property name="include.AMD64" value="${MSSDKDIR}\include" /> <property name="include.AMD64" value="${MSSDKDIR}\include" />

8
docs/BuildingJacobFromSource.html
View File

@@ -25,14 +25,14 @@ The Servlet examples that required j2ee libraries to compile have temporarily
been removed. been removed.
<p> <p>
<H1>Development Environment</h1> <H1>Development Environment</h1>
The simplest build environment 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.2 and JDK 1.4.
In that situation, you would just create the <i>compilation_tools.properties</i> 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, using the example build.xml as a template. All of the releases, up through 1.12,
were built using Visual C++ 6.0. were built using Visual C++ 6.0.
<UL> <UL>
<li> Microsoft Visual C++ 6.0 and it's included library. (to D:\apps in my case) <li> Microsoft Visual C++ 6.0 and it's included library. (to D:\apps in my case)
<li> Eclipse 3.1 or later from www.eclipse.org. <li> Eclipse 3.1 or later from www.eclipse.org.
<li> Java JDK 1.4 (this was built using 1.4.2.09) <li> Java JDK 1.4 (this was built using 1.4.2.13)
</ul> </ul>
<p> <p>
64 bit builds are supported with release 1.11. Tools required for 64 bit builds 64 bit builds are supported with release 1.11. Tools required for 64 bit builds
@@ -47,7 +47,7 @@ include:
</ul> </ul>
<li> Eclipse 3.1 or later from www.eclipse.org. <li> Eclipse 3.1 or later from www.eclipse.org.
<li> Java JDK 1.4 (this was built using 1.4.2.09) <li> Java JDK 1.4 (this was built using 1.4.2.13)
</ul> </ul>
Compilation using JDK 1.5 has not been tested Compilation using JDK 1.5 has not been tested