Java

Windows-Ia64 Build Instructions

JavaTM 2 SDK, Standard Edition, v1.4.2 fcs

Build Overview

Contents

Introduction

This README file contains build instructions for the JavaTM 2 SDK, Standard Edition, v1.4.2 (J2SDK 1.4.2) 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.

Windows-Ia64 System Setup

The official build platform for the 64-bit Windows J2SDK 1.4.2 is Windows XP - 64Bit Edition.

The minimum recommended hardware for building the Windows-Ia64 version is an Itanium class processor, at least 1 gigbyte of RAM, and approximately 4 gigabytes of free disk space.

Windows-Ia64 Build Tools and Libraries Setup

You will need to install the following additional tools and libraries for building a 64-bit version of the windows J2SDK.

Microsoft Visual C++ Compiler

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 required 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.

This compiler is used in conjunction with the Microsoft Platform Software Development Kit (SDK) ccompiler as described in the next section.

Microsoft Platform Software Development Kit (SDK), November 2001 Edition

The Microsoft Platform Software Development Kit (SDK), November 2001 Edition compiler, is required for building the J2SDK. You will need to minimally install the Core SDK and the MDAC SDK features of this compiler. The compiler and other tools are expected to reside in the locations defined by the variables MSSdk and MSTools, which are set by the setup utility SETENV.BAT /XP64 (usually found in C:\Program Files\Microsoft SDK\). It is required that you run SETENV.BAT /XP64 after running VCVARS32.BAT to set MSSdk, MSTools, MSVCDir, MSDevDir, INCLUDE, LIB, and the PATH correctly prior to building the 64-bit windows 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.

Because GNU Make has problems with spaces in command PATHS, it may be required that you set ALT_COMPILER_PATH and ALT_MSDEVTOOLS_PATH to point to the locations of the SDK using the Microsoft Mangled Path name convention. For example, if the Microsoft SDK is installed in C:\Progam Files\Microsoft SDK then the settings using mangled path names on the system may be: SET ALT_COMPILER_PATH=C:\Progra~1\Micros~3\bin\win64 and SET ALT_MSDEVTOOLS_PATH=C:\Progra~1\Micros~3\bin, depending on the unique situation of your build machine.

The compiler and tools binaries must be in the PATH.

msvcrt.dll and msvcrtd.dll

The J2SDK build requires access to msvcrt.dll and msvcrtd.dll version 6.10.9337.7 (version that we use ) supplied by The Microsoft Platform Software Development Kit (SDK), November 2001 Edition compiler (usually found in C:\Program Files\Microsoft SDK\redist\WIN64). If the msvcrt.dll is not installed in $(J2SE_TOPDIR)\make\redist\ia64, set the ALT_MSVCRT_DLL_PATH environment variable to their location. If the msvcrtd.dll is not installed in $(J2SE_TOPDIR)\make\redist\ia64 set the ALT_MSVCRTD_DLL_PATH environment variable

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.

MKS Unix Command Binaries

The J2SDK build requires access to Unix command binaries supplied by MKS Toolkit version 8.0 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.

If MKS is installed into a Path that contains spaces, it will be necessary to set ALT_UNIXCOMMAND_PATH to identify that location using Microsoft Mangled Path Name conventions. For example, if the MKS command are located in C:\Program Files\MKS Toolkit\mksnt, then ALT_UNIXCOMMAND_PATH should be set to C:\Progra~1\MKSToo~1\mksnt (or whatever mangled name setting is appropriate for your installation). You can use the DOS command DIR /x as an aide in determining the mangled path and file names.

Bootstrap J2SDK

You will need access to a J2SDK 1.4.1 or later for a windows-ia64 build. 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

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 and Unzip

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.

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).

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.

Windows-Ia64 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.

Environment variables may be set in the shell environment or on the GNU make command line.

ARCH_DATA_MODEL
Set the ARCH_DATA_MODEL to 64 to tell the build to perform a 64-bit build. By default, ARCH_DATA_MODEL is set to 32 and will build a 32-bit release.

PATH
Set the PATH to contain:
  • The location of the GNU make binary
  • The location of the MKS Unix command binaries (see ALT_UNIXCOMMAND_PATH below)
  • The location of the Microsoft SDK installation (see ALT_COMPILER_PATH and ALT_MSDEVTOOLS_PATH below)
  • The location of the Microsoft VC++ 6.0 compiler and tools.
  • The locations of the Windows NT system commands (usually C:\WINNT and C:\WINNT\system32)

It is strongly recommended that the Microsoft VC 6 and SDK setup scripts VCVARS32.BAT and SETENV.BAT /XP64 be used to set the PATH.

ALT_BOOTDIR
The location of the J2SDK 1.4.1 bootstrap installation.

ALT_OUTPUTDIR
An override for specifying the (absolute) path of where the build output is to go.

ALT_UNIXCOMMAND_PATH
An override for specifying the location of the MKS Unix command binaries, needed only if they are not installed in C:\mksnt\.

ALT_COMPILER_PATH
An override for specifying the location of the Microsoft SDK+ compiler. By default the build uses a path based on MSSdk, which is set by the SETENV.BAT \XP64 setup utility.

ALT_MSDEVTOOLS_PATH
An override for specifying the location of the Microsoft SDK development tools. By default the build uses a path based on Mstools, which is set by the SETENV.BAT /XP64 setup utility.

ALT_DEVTOOLS_PATH
The location of the zip and unzip binaries. See Zip and Unzip for details.

ALT_CACERTS_FILE
The location of the cacerts file. See cacerts file for details.

ALT_MOZILLA_PATH
The location of the Mozilla headers and libraries, needed only if building Java Plug-in.

ALT_DXSDK_PATH
The location of the Microsoft DirectX SDK headers and libraries.

ALT_MSVCRT_DLL_PATH
The location of the msvcrt.dll.

ALT_MSVCRTD_DLL_PATH
The location of the msvcrtd.dll.

MILESTONE
The milestone name for the build (e.g. "beta").

BUILD_NUMBER
The build number for the build (e.g. "b27").

Windows-Ia64 Build

  1. cd into the control/make directory.
  2. Start the build with the command:
        gnumake scsl ARCH_DATA_MODEL=64 [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.

Sun