Case: I want to edit my project on Windows using QtC and then cross-compile it for elf-i386 using toolchain installed in WSL. I can do it just fine using regular cmd, i.e. I can just type wsl (or wsl.exe) make and it'll build my project.

I though I could just create a custom project in QtC and add 'wsl make' as a custom build step but for some reason QtC complains that it can't open/start process "wsl".

I've tried using full path, I've also tried using "cmd /c C:\Windows\System32\wsl.exe ls" command which works just fine in the cmd itself, but from QtC it fails to start it too (can't find it).

I've also noticed one other very strange difference in behcaiour: if I invoke 'cmd /c dir C:\Windows\System32' as a QtC build step it doesn't list wsl.exe and in the summary it has 2981 total files and 186 folders, while if I do the same from the regular cmd promt, It lists 4534 files (this time it includes wsl.exe) and 212 folders.