Binary Plugs Usage

Kelly O'Hair Kelly.Ohair at Sun.COM
Sat Aug 18 11:08:23 PDT 2007


With the new sparse binary plug bundles, the build options will be slightly different.

Full openjdk control builds won't change much, but partial openjdk builds (builds
where hotspot is copied from somewhere) will be slightly different.

With the new sparse binary plugs the recommendation for full openjdk control
builds (where hotspot is also built):

     Download openjdk sources and binary plugs.
        cd control/make && gnumake ALT_BINARY_PLUGS_PATH=/plugs

The name ALT_CLOSED_JDK_IMPORT_PATH will be phased out.

The hotspot sources are part of the openjdk, so the proper or legal "open source"
way to set yourself up for partial openjdk builds would be:

    Download openjdk sources and binary plugs.
       cd control/make && gnumake ALT_BINARY_PLUGS_PATH=/plugs ALT_OUTPUTDIR=/myopenjdkimport

    Then you could repeatedly:
       cd j2se/make && gnumake ALT_BINARY_PLUGS_PATH=/plugs ALT_JDK_IMPORT_PATH=/myopenjdkimport
    to avoid rebuilding hotspot.

Since technically the hotspot VM is not a "binary plug", they are no longer in the binary
plugs bundle, and the past behavior had accidently copied the hotspot from the plugs area.
We use ALT_JDK_IMPORT_PATH as a way to facilitate partial builds where not all of
the jdk needs to be built, so the hotspot vm will now come from this location.

So for partial openjdk builds (and building from NetBeans projects) you will need
to change.

-kto





More information about the build-dev mailing list