Choosing which Visual Studio installation to use

Erik Joelsson erik.joelsson at
Thu Feb 15 15:27:45 UTC 2018


Just want to clear some things up around this. We use Cygwin just as a 
unix emulation layer for running typical unix tools. OpenJDK can only be 
built on Windows using Visual Studio as the compiler toolchain. We 
currently don't support any other unix emulation layer. We have had 
support for msys and we may work with msys2, but it's not being actively 
maintained so I'm pretty sure that has bit rotted by now. It's correct 
that if we actually used the gcc from cygwin, we would build for cygwin 
and not windows.

In the future I would like to support WSL, but it will require some 
work. I do believe the latest version is competent enough to get 
everything we need working though.


On 2018-02-14 05:16, John Paul Adrian Glaubitz wrote:
> On 02/14/2018 02:07 PM, Thomas Stüfe wrote:
>>     Does it have to be Cygwin though?
>> Yes. I love cygwin. You can put it into fullscreen and pretend you 
>> have a very slow Linux machine :) But seriously, it is very stable 
>> and mature, would not like at all to change my environment.
> Yes, but, if I remember correctly, the problem is that anything built
> with Cygwin always requires Cygwin to be present to be able to run.
> You always have to carry the runtime around if I remember correctly.
>>     On Windows I usually install the "git bash for Windows" package 
>> or whatever
>>     it's called and it gives me a nice bash command prompt with a 
>> working git
>>     and bash environment. You can then call the environment scripts 
>> from there.
>> Can you do a full openjdk build with that?
> I haven't tried OpenJDK. But in my previous company we did heavy Qt 
> development
> with git bash for Windows and any additional external libraries that 
> were required
> could usually be installed manually. It required some elbow grease, 
> but at least
> the resulting binaries were regular Win32 applications which didn't 
> require any
> particular runtime environment to be present except for the DLLs the 
> binaries
> were linked against.
> Adrian

More information about the build-dev mailing list