Java

Build Overview

JavaTM 2 SDK, Standard Edition, v#VERSION# #MILESTONE#

            

Contents

The Directory Structure

The source code for the Java 2 SDK, Standard Edition, v#VERSION# #MILESTONE# is delivered in three sibling directories named hotspot, j2se and control. The hotspot directory contains the source code and make files for building the Java(tm) Hotspot Virutal Machine. The j2se directory contains the source code and make files for building the J2SE runtime libraries, tools and demos. The control directory contains make files to build the entire J2SE release including buidling the hotspot VM, staging the VM binaries, and building the J2SE runtime libraries, tools and demos. Building using the control workspace is the recommended manner of building the J2SE.

Building Java 2 SDK, Standard Edition, v#VERSION# #MILESTONE#

For step-by-step instructions on building the J2SDK #VERSION#, choose a platform:

Testing the Build

When the build is completed, you should see the generated binaries and associated files in the control/build/<platform>/j2sdk-image directory of your source installation. In particular, the control/build/<platform>/j2sdk-image/bin directory should contain executables for the Java 2 SDK tools and utilities.

You can test that the build completed properly by using the build to run the various demos that you will find in the control/build/<platform>/j2sdk-image/demo directory. For example to run the Java 2DTM technology demo, change directories to control/build/<platform>/j2sdk-image/demo/jfc/Java2D and launch the demo with this command:

../../../bin/java -jar Java2Demo.jar

Troubleshooting Build Problems

A build can fail for any number of reasons. Most failures are a result of trying to build in an environment in which all the pre-build requirements have not been met. The first step in troubleshooting a build failure is to recheck that you have satisfied all the pre-build requirements for your platform.

You can validate your build environment by building the sanity target from the control/make directory. Any errors listed will stop the build from starting, and any warnings may result in a flawed product build. We strongly encourage you to evaluate every sanity check warning and fix it if required, before you proceed further with your build.

Some of the more common problems with builds are briefly descibed below, with suggestions for remedies.


Copyright 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

Sun