Adding back the mailing list.
Hi Ken,
On 18/01/2022 12:51 am, Ken Taylor wrote:
Hi David,
The instructions I am following are at
Building the JDK <https://openjdk.java.net/groups/build/doc/building.html>
Those instructions are for mainline JDK development and not directly
applicable to 8u. Unfortunately the 8u README-builds.html file has not
been updated either:
https://github.com/openjdk/jdk8u/blob/master/README-builds.html
but 8u supports building with up to VS 2017 at the moment.
Cheers,
David
-----
See the section:
Native Compiler (Toolchain) Requirements
Microsoft Visual Studio
I cloned the Git Repo for jdk8u, master branch.
Ken
On Sunday, January 16, 2022, 10:35:53 PM CST, David Holmes
<david.hol...@oracle.com> wrote:
Hi Ken,
On 13/01/2022 9:52 am, Ken Taylor wrote:
> I am trying to build JDK 8 from the jdk8u repo, master branch.Project
was forked and cloned into a Windows 10 VM.Building in Cygwin.
> It appears that the change to support VS 2019 has not been checked in.
>
> =======================================================
>
> JDK Build Instructions:
> Microsoft Visual Studio
>
> The minimum accepted version of Visual Studio is 2017. Older versions
will not be accepted by configure and will not work.
> The maximum accepted version of Visual Studio is 2019.
What repo exactly and what file contains these build instructions?
Thanks,
David
> If you have multiple versions of Visual Studio installed, configure
will by default pick the latest.
>
> You can request a specific version to be used by setting
> --with-toolchain-version, e.g. --with-toolchain-version=2017.
>
> =======================================================
>
> Our Command:
>
> ./configure
> --with-boot-jdk=/cygdrive/c/Programs/Java/jdk1.8.0_301
> --with-tools-dir='/cygdrive/c/Program Files (x86)/Microsoft
Visual Studio/2019/Community/VC/Auxiliary'
> --with-toolchain-version=2019
>
> =======================================================
>
> Error:
>
> configure: Using default toolchain microsoft (Microsoft Visual Studio)
> checking for link... /usr/bin/link
> checking if the first found link.exe is actually the Cygwin link
tool... yes
> configure: Visual Studio version 2019 is not valid.
> configure: Valid Visual Studio versions: 2010 2012 2013 2015 2017.
>
> =======================================================
>
> Was this something that got missed and is there a work-around, or
should I install VS 2017? BTW, VS 2022 also does not work.
>
> Thanks for any help you can provide.
> Ken Taylor
>
>
