Main Page
Cookbook/Overview ImageMeister the jcprops file Licensing Binary Installation & Configuration [ Win · Mac · Nix ] Changes Public API Source Code Main Page Java [ Common · Win · Mac · Nix ] Native Code [ Common · Win · Mac · Nix ] Manifest Native Code Overviews [ Common · Win · Mac · Nix · Strings ] Macros [ General · Native Macros ] Walkthroughs [ Java only · Java and native ] Building [ Win · Mac · Nix ] Distribution Issues |
It is recommended that you don't move the source
folder. If you unzipped the distribution to
the root of your C:
drive as recommended, the batch files might require only minimal changes.
Otherwise, you'll need to edit the batch files to reflect the location of the source
folder.
It is also recommended that you use Windows as your 'homebase'; i.e., store the master copies of the JConfig files on Windows, copying to Mac or Linux only as necessary to compile the native code.
Two batch files are used to compile the Java and C++ code, comp.bat
and buildall.bat
;
if you don't store the distribution into the folder given above, you'll need to edit the batch files as described below.
Also, you'll need to edit the first few lines of comp.bat
and buildall.bat
, depending on the locations where you
have the required software installed. See below for details.
To compile the Java code, you need:
comp.bat
assumes that this is stored in e:\java
comp.bat
assumes that this is stored in f:\jdk1.1.4
comp.bat
assumes that this is stored in e:\infozip.
buildall.bat
assumes that this is stored in f:\jdk1.1.4
buildall.bat
assumes that this is stored in e:\sdk-java
buildall.bat
assumes that this is stored in e:\sdk-java.20
The batch file comp.bat
is used to compile the Java code for all platforms. You'll need to edit the first few
lines of this file depending on where the JDK and InfoZip are stored. See that file for details.
Because one of the .java files uses 1.1 features,
this is a little complicated.
The batch file buildall.bat
is used to compile the Windows native code DLLs. This file uses nmake and the make files
for each of the six DLLs. You'll need to edit the first few lines of this file depending on where the JDK
and the MS Java SDKs are stored. See that file for details.
IMPORTANT NOTE: If necessary, you might also need to edit the .mak files. Try to edit the .mak files manually (i.e., as text) first before opening them with MSVC. If you open the .mdp files with MSVC, you might need to spend some time telling MSVC where to look for the correct include files and libraries.
IMPORTANT NOTE: Don't modify the relative locations of files or folders within the distribution; doing so may require editing the project files, batch files, etc.
NOTE: If you get the message 'Out of Environment Space' when running
the batch files, right click on the batch file, and choose 'Properties'.
On the 'Memory' tab, in the 'Conventional Memory' area, set the 'Initial
Environment' popup menu to its highest setting.