-
-
Notifications
You must be signed in to change notification settings - Fork 772
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
Xmake in Windows failed to compile projects stored inside WSL2 #3013
Comments
powershell support it, but xmake maybe does not support it. xmake use the native Win32 API to access windows path. It seems not support it. I don't have a windows wsl2 environment at the moment to test and improve it further. You can open a pr to improve it. |
Isn't it because xmake processes paths and deduplicate (back)slashes? (turning \\wsl.localhost into \wsl.localhost) |
I don't know, I don't have the environment to test it right now. |
maybe need improve path.c to support But I cannot test it. |
I have improved it, you can try it again. |
It should work. |
Xmake Version
2.7.2
Operating System Version and Architecture
Host: Windows 11 version 21H2; WSL2: Ubuntu 22.04 5.10.102.1-microsoft-standard-WSL2
Describe Bug
In Windows 11, Microsoft PowerShell has supported access files and paths inside WSL2. User can directly copy a path of WSL2 from Windows' file explorer and use
cd
command in PowerShell to change their working path to somewhere inside the WSL2 VM.Theoretically, this should have allowd xmake installed on Windows directly compile source code stored in WSL2 without copying them back to host. Since MSVC has the widest support of C++20 (much more than gcc/clang), such feature is supposed to be useful.
However, current version of xmake failed to parse such sort of path, who behaved as follows:
The path used in the example above is:
\\wsl.localhost\Ubuntu-22.04\home\user
.Expected Behavior
For xmake installed inside WSL2, things are fine just like they are in normal Linux:
Project Configuration
No response
Additional Information and Error Logs
No response
The text was updated successfully, but these errors were encountered: