jaesmile.blogg.se

1. #How to use dumpbin.exe visual studio 2018 Patch#
2. #How to use dumpbin.exe visual studio 2018 windows#

#How to use dumpbin.exe visual studio 2018 windows#

To ensure the correct environment variables are propagated from Windows to WSL, you can run the following commands:Ĥ. wsl must be started from a Windows Developer command prompt. Mklink /D C:\WindowsKits "C:\Program Files (x86)\Windows Kits"Ģ.

Mklink /D C:\VS "C:\Program Files (x86)\Microsoft Visual Studio" Due to autotools not handling spaces well, you have to create symlinks in Windows that will allow you to access Windows Kits and the VC++ compiler without spaces in the path: I have not implemented that yet, but I think I could do that as a next step if you guys think it would be useful (at least I think it would be useful, then you can test your changes for both Windows and Linux on one system.).ġ. It is also possible to use WSL to target itself (a WSL Linux binary) or even other distributions of Linux. One important thing to note is that the WSL build targets Windows.

#How to use dumpbin.exe visual studio 2018 Patch#

I've attached a patch with my proposed changes. Given that WSL is provided with newer versions of the OS (and doesn't suffer from many of the issues that Cygwin does, given that it is built into the Windows kernel), I think it would be great if OpenJDK would support building on WSL. Currently, our Windows build uses Cygwin.

I've been working on getting the OpenJDK to build on WSL (Windows Subsystem for Linux).