Open Mrkol opened 6 years ago
That sounds good and would be cool to have, but I definitely won't have time to dive into that. Also, I am by far not an expert in Windows. If anybody would want to look into that and do a nice PR, I will look into it.
I will close this but keep it in the backlog. If someone wants to contribute to this, just reopen it.
Workaround for the lazy (like me) :
{
"use_libclang": false,
"clang_binary": "clang-wsl"
}
@wsl clang++ %*
Hi @kiwec , does this still work for you? I tried this but no completion results show.
Hi @kiwec , does this still work for you? I tried this but no completion results show.
Sorry, I dropped windows permanently :smile: Can't help you :yum:
I'm lazily working on this now. Basically, we will have to add another setting like "use WSL" or smth. This way, sublime text installed on Windows would be able to use all the tools installed on WSL, like clang, cmake etc. This essentially requires only the following things to be implemented:
wsl
before every command, which is really easy to doos.path
all over the place. Sublime Text 3 did not support Python 3.4 so we are stuck with that instead of pathlib or alike. The issue here is that os.path
gets confused as it thinks we are on Windows while we want it to think we are on Linux. I'm trying various things to mitigate this.
Is it possible to painlessly add support for the Windows Subsystem for Linux (previously known as bash on ubuntu on windows)? Due to specific circumstances I have to compile my project through the WSL cmake and clang, but autocomplete via the windows binaries, therefore having to duplicate each library for both platforms. Visual studio code has recently implemented it, implying that it is theoretically possible and might not even be that hard.