generated from obsidianmd/obsidian-sample-plugin
-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Does not work with WSL + Cling on Windows #333
Comments
I have the same problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have WSL 2 installed; I built Cling from scratch in WSL on Windows and I can execute the
cling
binary in a WSL console without error; I havecling
in the ~/.bashrc PATH so it can be executed in the WSL console via, simply,cling
; it can also be executed via the absolute path.However, it is not possible to get the C++ settings to work for the Execute Code plugin.
Enable WSL option (and I also tried with this option disabled trying both paths below)
Paste absolute path in Windows to cling (as in E:\path\to\cling)
*** or ***
Past absolute path in WSL to cling (as in /mnt/e/path/to/cling)
...and there is always an ENOENT error when attempting to run the code block.
Note: Python running in WSL (enabling the WSL setting and simply having 'python3' as the path to Python in the Execute Code settings for Python) succeeds, so WSL is being accessed.
It's just that C++ does not work, unfortunately. Alas! Took me two days to get Cling finally building in WSL hoping it would work with Execute Code - so just creating this issue so perhaps others will think twice before embarking on this route.
Thanks!
The text was updated successfully, but these errors were encountered: