bash configure - LINK : fatal error LNK1104: cannot open file ...fixpath.exe

[jbvernee]

Hey Erik,

I was running into warnings in the standard library being treated as 
errors with VS 2015, so --disable-warnings-as-errors did the trick :D

The information I remembered turned out to be outdated. I went and 
looked at doc/building.html again and found that amber required at least 
VS 2013 update 4. I should have RTFM (oops). The toolchain_windows.m4 
tip was a good one, it looks like the repo also supports VS 2017, so I'm 
now building using the BuildTools version of 2017 successfully (thanks 
for the tip). Tbh, it feels really great to finally get this working :) 
The support for newer versions of VS is really appreciated.

Thanks for all the help,
Jorn Vernee

Erik Joelsson schreef op 2018-06-12 15:56:
> Hello,
> 
> Glad to hear you got Cygwin in order!
> 
> The officially supported toolchain for jdk/jdk (current mainline for
> JDK 11) is VS 2017. We recently upgraded from 2013. Amber seems to be
> pretty much up to date with that from looking at the repo changes. You
> can check at the top of toolchain_windows.m4 for the list of VS
> versions. The order of that list shows our preference. I do not think
> 2010 works well since we upgraded from that to 2013 a long time ago in
> JDK 9. I do believe 2015 should work, but last I tried, I needed to
> add --disable-warnings-as-errors to get through. For 2017, you only
> need the "BuildTools" edition if you want to minimize the install. If
> you want the Visual Studio IDE, then community edition works just as
> well.
> 
> If you are running Windows 10, you can also try installing the Windows
> Subsystem for Linux. In my experience, OpenJDK builds pretty much out
> of the box in Ubuntu under WSL as long as you provide a bootjdk of the
> correct version (for Linux). You get a Linux binary that works in WSL
> (or native Linux).
> 
> /Erik