It's not an issue, but a question, where I found no answer in the docs.
Is it possible to configure the toolchain, that cmake is always invoked through another shell (e.g. Git-bash)
I have multiple gnu.toolchain based projects, using Unix Makefiles. I can do that under Windows from command line without any problems, when I use the Git Bash as my local terminal.
Git bash hides the drive letters, beautifies all environment variables, rewrites PATHes with slash instead backslash.
So all CMake generated Makefiles will work with the gnu-toolchain.
However, when CMake is running as core Windows executable or within CMD.exe or Powershell, the CMake generated Makefiles are broken for many gnu tools. So it would be nice, if CMake could be called through an encapsulated Git-bash: /path/to/bash.exe -c /path/to/cmake arguments
Using Git bash is the easiest way to overcome this problem, otherwise you have to use WSL or remote/virtual Linux machines, where all the VSCode settings need to be replicated and synchronized.
I asked the same question in the Microsoft CMake integration extension, right now this is not possible. So I am reviewing other possibilities, using some more comfort.
It's not an issue, but a question, where I found no answer in the docs. Is it possible to configure the toolchain, that cmake is always invoked through another shell (e.g. Git-bash) I have multiple gnu.toolchain based projects, using Unix Makefiles. I can do that under Windows from command line without any problems, when I use the Git Bash as my local terminal. Git bash hides the drive letters, beautifies all environment variables, rewrites PATHes with slash instead backslash. So all CMake generated Makefiles will work with the gnu-toolchain. However, when CMake is running as core Windows executable or within CMD.exe or Powershell, the CMake generated Makefiles are broken for many gnu tools. So it would be nice, if CMake could be called through an encapsulated Git-bash: /path/to/bash.exe -c /path/to/cmake arguments Using Git bash is the easiest way to overcome this problem, otherwise you have to use WSL or remote/virtual Linux machines, where all the VSCode settings need to be replicated and synchronized. I asked the same question in the Microsoft CMake integration extension, right now this is not possible. So I am reviewing other possibilities, using some more comfort.