-
Enhancement
-
Resolution: Fixed
-
P4
-
11
-
b01
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8208845 | 8u201 | Kevin Walls | P4 | Resolved | Fixed | b01 |
| JDK-8204649 | 8u192 | Kevin Walls | P4 | Resolved | Fixed | b01 |
| JDK-8216645 | emb-8u201 | Kevin Walls | P4 | Resolved | Fixed | master |
The build needs to accept newer versions of Visual Studio as valid toolchains for building JDK 11.
We are most likely going to upgrade the toolchains used for building JDK 11. On Windows, the most likely candidate is Visual Studio 2017. We know that we will need plenty of source level changes for our product to compile with a newer Visual Studio. To make it possible for the various component teams to fix their areas, we first need to change the build to even accept the toolchain.
This bug will not change the default toolchain or attempt to fix every issue related to the new toolchain versions. It will just change the build to set things up correctly for using the new toolchain versions.
We are most likely going to upgrade the toolchains used for building JDK 11. On Windows, the most likely candidate is Visual Studio 2017. We know that we will need plenty of source level changes for our product to compile with a newer Visual Studio. To make it possible for the various component teams to fix their areas, we first need to change the build to even accept the toolchain.
This bug will not change the default toolchain or attempt to fix every issue related to the new toolchain versions. It will just change the build to set things up correctly for using the new toolchain versions.
- backported by
-
JDK-8204649 Add build support for VS 2015/2017
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8194645 Build should work with VS 2013 express for 64bit builds
-
- Resolved
-