-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch jdk8 Windows compilation to use VS2019 #15051
Comments
The change is promoted in jdk8u342-b02. |
I tried a build with VS2019 but it failed
|
I'm trying a build with VS2017.
|
The VS2017 build all passed. |
Also remove duplicate entry for freetype version Related eclipse-openj9/openj9#15051 Signed-off-by: Adam Brousseau <adam.brousseau88@gmail.com>
Also remove duplicate entry for freetype version Related eclipse-openj9/openj9#15051 Signed-off-by: Adam Brousseau <adam.brousseau88@gmail.com>
Builds are switched to VS2017. Move this forward to consider VS2019 later. |
FYI Adopt moved jdk11 to VS2019. Maybe we need to cover that in a different issue |
I don't know there is any urgency to switch, we can target after 0.33 |
Issue eclipse-openj9#15051 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
0.38 M1 used VS2019 without issue. Doc issue eclipse-openj9/openj9-docs#1073 |
We need to keep an eye on this. There may be a switch to Windows compilation coming.
See adoptium/temurin-build#2922
and 8221988: add possibility to build with Visual Studio 2019
The text was updated successfully, but these errors were encountered: