Oracle is planning on changing the toolchain versions used to produce
Oracle builds of OpenJDK in JDK 11. As a first step towards changing the
Windows toolchain versions, I'm implementing the basic support in the
build system for both recognizing the newer versions of Visual Studio as
well as generating a portable devkit for them.
With this patch, it becomes possible (but not default) to create a
configuration using Visual Studio 2015 and 2017. Note though that the
build will still fail very early on. Fixing all the source code issues
to get this to work will require a concerted effort from each affected
component team and will be handled in a series of followup issues. The
build system support naturally needs to happen first though to enable
others to proceed.
For now, this patch causes configure to issue warnings if you try to use
the new versions of Visual Studio as we know it won't actually work.
Bug: https://bugs.openjdk.java.net/browse/JDK-8196108
Webrev: http://cr.openjdk.java.net/~erikj/8196108/webrev.02/
If anyone inside Oracle would like to use the new devkit for 2017, you
can apply the patch below in addition to the webrev:
diff -r 7e5fbd3a2254 make/conf/jib-profiles.js
--- a/make/conf/jib-profiles.js Mon Jan 22 23:37:23 2018 -0800
+++ b/make/conf/jib-profiles.js Sat Jan 27 00:39:57 2018 +0100
@@ -769,7 +769,7 @@
macosx_x64: "Xcode6.3-MacOSX10.9+1.0",
solaris_x64: "SS12u4-Solaris11u1+1.0",
solaris_sparcv9: "SS12u4-Solaris11u1+1.0",
- windows_x64: "VS2013SP4+1.0",
+ windows_x64: "VS2017-15.5.5+1.0",
linux_aarch64:
"gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux+1.0",
linux_arm: (input.profile != null &&
input.profile.indexOf("hflt") >= 0
?
"gcc-linaro-arm-linux-gnueabihf-raspbian-2012.09-20120921_linux+1.0"
@@ -784,8 +784,8 @@
+ "-" + input.build_cpu;
var freetype_version = {
- windows_x64: "2.7.1-v120+1.1",
- windows_x86: "2.7.1-v120+1.1",
+ windows_x64: "2.7.1-v141+1.0",
+ windows_x86: "2.7.1-v141+1.0",
macosx_x64: "2.7.1-Xcode6.3-MacOSX10.9+1.0"
}[input.target_platform];
