# HG changeset patch # User mikejwre # Date 1276728533 25200 # Node ID eda3e9ad64dc2c8eb10dfd84219a649c2dc48988 # Parent 8d883031427411f8583f47e349452621c7b40f34# Parent 1cc5e6b39ea84723271d6ff9717b83380940f0ff Merge diff -r 8d8830314274 -r eda3e9ad64dc README-builds.html --- a/README-builds.html Thu Jun 10 13:58:55 2010 -0700 +++ b/README-builds.html Wed Jun 16 15:48:53 2010 -0700 @@ -65,8 +65,9 @@
  • Certificate Authority File (cacert)
  • Compilers @@ -789,11 +790,11 @@
  • Install the - Microsoft Visual Studio Compilers). + Microsoft Visual Studio Compilers).
  • Setup all environment variables for compilers - (see compilers). + (see compilers).
  • Install @@ -958,7 +959,7 @@ are also an option, although these compilers have not been extensively used yet. - Windows i586: Microsoft Visual Studio Compilers + Windows i586: Microsoft Visual Studio 2010 Compilers

    BEGIN WARNING: At this time (Spring/Summer 2010) JDK 7 is starting a transition to @@ -971,14 +972,13 @@ We do not guarantee that VS2008 will work, although there is sufficient makefile support to make at least basic JDK builds plausible. Visual Studio 2010 Express compilers are now able to build all the -open source repositories, but this is 32 bit only, since -we have not yet seen the 7.1 Windows SDK with the 64 bit -compilers. END WARNING. +open source repositories, but this is 32 bit only. To build 64 bit +Windows binaries use the the 7.1 Windows SDK.END WARNING.

    The 32-bit OpenJDK Windows build requires Microsoft Visual Studio C++ 2010 (VS2010) Professional - Edition compiler. + Edition or Express compiler. The compiler and other tools are expected to reside in the location defined by the variable VS100COMNTOOLS which @@ -1001,14 +1001,33 @@ The path /usr/bin must be after the path to the Visual Studio product.

    - Windows x64: Microsoft Visual Studio Compilers + Windows x64: Microsoft Visual Studio 2010 Professional Compiler
    - On X64, the set up is much the same in VS2010 + For X64, builds, when using the VS2010 Professional + compiler, the 64 bit build set up is much the same as 32 bit except that you run amd64\VCVARS64.BAT to set the compiler environment variables. - Previously 64 builds had used the 64 bit compiler in - an unbundled Windows SDK but this is no longer necessary. + Previously 64 bit builds had used the 64 bit compiler in + an unbundled Windows SDK but this is no longer necessary if + you have VS2010 Professional.
    + Windows x64: Microsoft Windows 7.1 SDK 64 bit compilers. + For a free alternative for 64 bit builds, use the 7.1 SDK. + Microsoft say that to set up your paths for this run +
    +    c:\Program Files\Microsoft SDKs\Windows\v7.1\bin\setenv.cmd /x64.
    +
    + What was tested is just directly setting up LIB, INCLUDE, + PATH and based on the installation directories using the + DOS short name appropriate for the system, (you will + need to set them for yours, not just blindly copy this) eg : +
    +    set VSINSTALLDIR=c:\PROGRA~2\MICROS~1.0
    +    set WindowsSdkDir=c:\PROGRA~1\MICROS~1\Windows\v7.1
    +    set PATH=%VSINSTALLDIR%\vc\bin\amd64;%VSINSTALLDIR%\Common7\IDE;%WindowsSdkDir%\bin;%PATH%
    +    set INCLUDE=%VSINSTALLDIR%\vc\include;%WindowsSdkDir%\include
    +    set LIB=%VSINSTALLDIR%\vc\lib\amd64;%WindowsSdkDir%\lib\x64
    +

    Zip and Unzip