With 0.28.2, we changed the cwd of Windows tasks to ${workspaceFolder} instead of the compiler's path (https://github.com/microsoft/vscode-cpptools/pull/5585/files#diff-534e02d5e11dbc8e84fb43120a7488eeR351). However, this causes mingw to fail if it's not on the path, i.e. the workaround is either to add it to your path (might require a VS Code restart afterwards) or change the default cwd. I thought the issue only affected Cygwin and not mingw too.
This could be considered "by design", but it seems safer to just default to the compiler's path on Windows. UPDATE: We can check PATH for the compiler's path.
The original change was made in response to #4761 .
With 0.28.2, we changed the cwd of Windows tasks to ${workspaceFolder} instead of the compiler's path (https://github.com/microsoft/vscode-cpptools/pull/5585/files#diff-534e02d5e11dbc8e84fb43120a7488eeR351). However, this causes mingw to fail if it's not on the path, i.e. the workaround is either to add it to your path (might require a VS Code restart afterwards) or change the default cwd. I thought the issue only affected Cygwin and not mingw too.
This could be considered "by design", but it seems safer to just default to the compiler's path on Windows. UPDATE: We can check PATH for the compiler's path.
The original change was made in response to #4761 .