-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reasses building under WSL #241
Comments
IIRC, I believe you can run software compiled for Windows in WSL, but you cannot run software compiled in WSL for Windows. We'll need to cross compile for Windows in WSL |
It looks like that project is still using MSVC and Windows SDK, that's what I had in mind :) |
This came up after building from a WSL path mapped to a network drive. The same will occur within WSL:
hack:
To resolve we would need to request MS to fix the headers, or patch them after extracting. |
Running install.ps1 from powershell in WSL folder and VS build tools installed:" PS Microsoft.PowerShell.Core\FileSystem::\\wsl.localhost\Ubuntu-20.04\home\user\socket> Set-ExecutionPolicy Bypass
# ... /y
PS Microsoft.PowerShell.Core\FileSystem::\\wsl.localhost\Ubuntu-20.04\home\user\socket> .\bin\install.ps1 -verbose
# Using toolchain: vsbuild
# C:\WINDOWS\System32\vcruntime140_1.dll found.
# Git found at, changing path to: git.exe
# Found git.exe
# Calling vcvars64.bat
'\\wsl.localhost\Ubuntu-20.04\home\user\socket'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
# C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\Build\vcvars64.bat didn't enable both clang++ and nmake, downloading vs_build.exe
clang 15.0.0, Windows SDK and nmake are required, proceed with install from Microsoft? y/[n]?
> |
manual
libuv
build is now possible, we just need to extract the necessary options from libuv's generated .vsproj and pass those th clang.I can't recall if there were other blockers.
clang/++
from WSLssc
build with prebuiltlibuv
The text was updated successfully, but these errors were encountered: