![]() |
Windows Build Instructions
JavaTM 2 SDK, Standard Edition, v#VERSION# #MILESTONE#
|
Build Overview |
This README file contains build instructions for the JavaTM 2 SDK, Standard Edition, v#VERSION# (J2SDK #VERSION#) Community Source Release. Building the source code for the Java 2 SDK requires a high level of technical expertise. Sun provides the source code primarily for technical experts who want to conduct research, port the platform to new operating systems and hardware, or add enhancements that require access to platform internals. If you are not a technical professional in one of these categories, this release is probably not for you.
The official build platform for the J2SDK #VERSION# is Windows NT 4.0 with Service Pack 6 or greater installed.The minimum recommended hardware for building the Windows version is a Pentium class processor or better, at least 256 megabytes of RAM, and approximately 600 MB of free disk space.
Once the Windows OS is set up, you will need to install additional tools and libraries for building the J2SDK.
The Microsoft Visual C++ 6.0 Professional Edition compiler, with Visual C++ 6.0 Service Pack 3 installed (not Service Pack 4), is required for building the J2SDK. The compiler and other tools are expected to reside in the locations defined by the variables MSVCDir and MSDevDir, which are set by the setup utility VCVARS32.BAT (usually found in C:\Program Files\Microsoft Visual Studio\VC98\Bin\). It is highly recommended that you run VCVARS32.BAT to set MSVCDir, MSDevDir, INCLUDE, LIB, and the PATH prior to building the J2SDK. If your compiler resides in a place other than the default, you can set ALT_COMPILER_PATH to point to the location of the cl compiler binary, and ALT_MSDEVTOOLS_PATH to point to the location of the development tools. The compiler and tools binaries must be in the PATH.
The J2SDK build requires access to Unix command binaries supplied by MKS Toolkit version 6.1a or later. Information about the MKS Toolkit can be obtained from the MKS website at http://www.mks.com. If the binaries are not installed in C:\mksnt\, set the ALT_UNIXCOMMAND_PATH environment variable to their location.
The J2SDK build requires access to msvcrt.dll version 6.00.8337.0 (version that we use ) supplied by Microsoft Visual C++ 6.0 Service Pack 2 (usually found in C:\WINNT\System32\). If the msvcrt.dll is not installed in $(J2SE_TOPDIR)\make\redist\i586, set the ALT_MSVCRT_DLL_PATH environment variable to their location.
You will need access to a J2SDK 1.4.1 for Windows installation. The 1.4.1 binaries can be downloaded from Sun's J2SDK 1.4.1 download site. Set ALT_BOOTDIR to point to the location of the bootstrap J2SDK installation, and place its bin directory in the PATH.
GNU make version 3.78.1 or later, built for the MKS shell per the instructions in its documentation, is required to build the J2SDK. Information on GNU make, and access to ftp download sites, are available on the GNU make web site. Place the location of the GNU make binary in the PATH.
ZIP.EXE and UNZIP.EXE should be installed in C:\UTILS. If you have them installed elsewhere set the environment variable ALT_DEVTOOLS_PATH to their location. ZIP.EXE version should be 2.2 or 2.[2-9]. UNZIP.EXE version should be 5.12 or 5.1[2-9]. Information and the source code for ZIP.EXE and UNZIP.EXE is available on the info-zip web site.
The source bundles contain a cacerts file without CA root certificates.
J2SDK builders will need to secure permission from each public CA and
include the certficates into their own custom cacerts file. Failure to
provide a populated cacerts file will result in verification of a
certificat chain during runtime.
The ALT_CACERTS_FILE should be set to point to the location of
the populated cacerts file.
Mozilla headers and libraries are required for building Java Plug-in.
Since Mozilla headers changed significantly from Netscape 6.x to
Netscape 7, we will have to build two libraries for Mantis.
One of the libraries will be for Netscape 6.x and the other will be
for Netscape 7. As a result, the Mantis build requires both sets
of header files as shown below. Download
and unpack the headers and libraries into a directory
similar to the one shown below, and set the
ALT_MOZILLA_PATH environment variable to the
absolute path of the top-level directory.
Environment variables may be set in the shell environment
or on the GNU make command line.
In addition, execute the setup utility
VCVARS32.BAT.
cacerts
A certificates file named "cacerts" represents a system-wide keystore
with CA certificates. In J2SDK and JRE binary bundles, the "cacerts"
file contains root CA certificates from several public CAs (e.g., VeriSign,
Thawte, and Baltimore).
Mozilla Headers and Libraries
Note: the Java Plug-in product for Windows cannot be built from
the Community Source Release. This section applies only to those
with a separate source license for that product. The Mozilla
Headers and Libraries are only required for building the Java Plug-in.
If you do not build Java Plug-in, the headers and libraries are not
required.
+- devtools\ (set ALT_MOZILLA_PATH to this level)
+- win32\
| +- plugin\
| +- mozilla_libs_ns610\
|
+- share\
+- plugin\
+- mozilla_headers_ns610.win32\
+- mozilla_headers_ns7.win32\
The name of the top-level directory is
not significant; it is not required to be named devtools.
Microsoft DirectX 7 SDK header files and libraries
Microsoft DirectX 7 SDK headers are required for building j2se.
The DirectX 7 SDK can be downloaded from
http://download.microsoft.com/download/win98SE/SDK/7.0/W9X/EN-US/dx7sdk-700.1.exe.
If the link above becomes obsolete, the SDK can be obtained from
http://www.microsoft.com/directx.
If the SDK is not installed to
c:\dxsdk
, set the ALT_DXSDK_PATH
environment variable to its location.
c:\ (set ALT_DXSDK_DRIVE to this level)
+- DXSDK\ (set ALT_DXSDK_PATH to this level)
+- Include\ (set ALT_DXSDK_INCLUDE_PATH to this level)
+- Libs\ (set ALT_DXSDK_LIBS_PATH to this level)
Note: the ALT_DXSDK_* variables have the following order of precedence
(from most to least):
For example, ALT_DXSDK_DRIVE will be ignored if ALT_DXSDK_PATH is set.
Windows Build Environment Variables
This section describes environment variables that you can set to
influence various aspects of the build. Some of these variables
are mentioned specifically in the setup and build instructions
above. Others you may set at your discretion.
PATH
to contain:
Windows Build
gnumake scsl [ALT_OUTPUTDIR=directory-name-for-output] [MILESTONE=milestone_name] [BUILD_NUMBER=build_number] [other "ALT_" overrides]
Copyright 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. |
|