cannot find valid Visual Code Studio install

[Erik Joelsson]

Hello Ty,

Microsoft Visual Studio 2019 or 2017, any edition, should work. My best 
guess is that you skipped installing the necessary parts of it. Run the 
installer again, click "Modify" and make sure you have "Desktop 
development with C++" ticked in.

/ERik

On 2020-07-09 01:29, Ty Young wrote:
> Hopefully this is the right place. Don't shoot me if it isn't, please.
>
>
> I'm trying to build the JDK from Windows 10. I got so far as to 
> configure failing on finding what it needs from the Visual Code Studio 
> install via command line:
>
>
> configure: Found Visual Studio installation at /cygdrive/c/Program 
> Files (x86)/Microsoft Visual Studio/2019/Community using well-known name
> configure: Warning: None of vc/bin/amd64/vcvars64.bat 
> vc/bin/x86_amd64/vcvarsx86_amd64.bat 
> VC/Auxiliary/Build/vcvarsx86_amd64.bat VC/Auxiliary/Build/vcvars64.bat 
> were found, Visual Studio installation not recognized. Ignoring
> configure: Found Visual Studio installation at /cygdrive/c/Program 
> Files (x86)/Microsoft Visual Studio/2019/Community using well-known name
> configure: Warning: None of vc/bin/amd64/vcvars64.bat 
> vc/bin/x86_amd64/vcvarsx86_amd64.bat 
> VC/Auxiliary/Build/vcvarsx86_amd64.bat VC/Auxiliary/Build/vcvars64.bat 
> were found, Visual Studio installation not recognized. Ignoring
> configure: Cannot locate a valid Visual Studio installation, checking 
> current environment
> checking for Visual Studio variables... not found
> configure: Cannot locate a valid Visual Studio or Windows SDK 
> installation on disk,
> configure: nor is this script run from a Visual Studio command prompt.
> configure: Try setting --with-tools-dir to the VC/bin directory within 
> the VS installation
>
>
> However there is no "bin" directory in this installation, at least not 
> one that contains any of the specified files. This is Visual Code 2019 
> Community, but I've tried the Professional version too. The building 
> document doesn't specify which version, nor does it tell me how to fix 
> this.
>
>
> How do I get this to work via command line?
>