microsoft / microsoft/vscode-makefile-tools
Avoid exception by improving `makefile.additionalCompilerNames` handling to automatically escape characters like `+`
@snehara99 is already working on this.
Since Jan 29, 2026.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm trying to setup makefile tools to be able to cross compile for Nios II within vscode and have run into the same issue when attempting to run Makefile: Configure, Makefile: Clean Configure. On attempting to Debug or Run I see: Cannot run because there is no launch configuration set and the list of launch targets is empty. Double check the makefile configuration and the build target. (The build target is set to all and the build is successful) I have defined a launch target in a launch.json file but there doesn't seem to be a way of selecting this or associating it with my Makefile project.
When I attempt to run Makefile: Configure I see the following output:
The project needs a configure to populate the launch targets correctly.
Saving opened files before build.
Generating configuration cache with command: 'make all --dry-run --keep-going --print-directory'
Writing the dry-run output: /home/user/.config/Code/User/workspaceStorage/6f0a7708412f42e0089d7c9c03759fd3/ms-vscode.makefile-tools/dryrun.log
Generating dry-run elapsed time: 0.175
Preprocessing: "/home/user/.config/Code/User/workspaceStorage/6f0a7708412f42e0089d7c9c03759fd3/ms-vscode.makefile-tools/dryrun.log"
Preprocess elapsed time: 0
Parsing for IntelliSense.
Updating the CppTools IntelliSense Configuration Provider.
Parsing dry-run output for CppTools Custom Configuration Provider.
Exception thrown during the configure process: Invalid regular expression: /^[\s"](.?)((([a-zA-Z0-9-.]*-)*ccache(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*clang++(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*clang-cl(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*clang-cpp(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*clang(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*gcc(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*gpp(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*cpp(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*icc(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*cc(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*icl(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*cl(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*g++(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*c++(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*nios2-elf-gcc(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*nios2-elf-ar(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*nios2-elf-g++(-[a-zA-Z0-9-.]))|(([a-zA-Z0-9-.]*-)*nios2-elf-nm(-[a-zA-Z0-9-.])))(\s|"\s)(.*)$/gm: Nothing to repeat
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.