Compiler won't run

[Gavin-Williams]

Type: Bug

I've followed the setup here...
https://code.visualstudio.com/docs/cpp/config-msvc#_prerequisites
https://code.visualstudio.com/docs/cpp/config-msvc#_run-vs-code-outside-the-developer-command-prompt

And I have the following tasks.json from the walkthrough...

{
    "version": "2.0.0",
    "windows": {
        "options": {
            "shell": {
                "executable": "cmd.exe",
                "args": [
                    "/C",
                    "\"C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/Tools/VsDevCmd.bat\"",
                    "&&"
                ]
            }
        }
    },
    "tasks": [
        {
            "type": "shell",
            "label": "cl.exe build active file",
            "command": "cl.exe",
            "args": [
                "/Zi",
                "/EHsc",
                "/Fe:",
                "${fileDirname}\\${fileBasenameNoExtension}.exe",
                "${file}"
            ],
            "problemMatcher": [
                "$msCompile"
            ],
            "group": "build"
        },
        {
            "type": "cppbuild",
            "label": "C/C++: cl.exe build active file",
            "command": "cl.exe",
            "args": [
                "/Zi",
                "/EHsc",
                "/nologo",
                "/Fe${fileDirname}\\${fileBasenameNoExtension}.exe",
                "${file}"
            ],
            "options": {
                "cwd": "${fileDirname}"
            },
            "problemMatcher": [
                "$msCompile"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "detail": "Task generated by Debugger."
        }
    ]
}

But when I build the project, cl.exe is still not recognized.

VS Code version: Code 1.101.1 (18e3a1e, 2025-06-18T13:35:12.605Z)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info

Item	Value
CPUs	AMD Ryzen 7 5700X 8-Core Processor (16 x 3400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	31.93GB (21.27GB free)
Process Argv	--crash-reporter-id ebb1a6aa-cad7-401f-9148-337640bd8191
Screen Reader	no
VM	0%

Extensions (5)

Extension	Author (truncated)	Version
copilot	Git	1.336.0
copilot-chat	Git	0.28.2
cmake-tools	ms-	1.20.53
cpptools	ms-	1.25.3
cpptools-extension-pack	ms-	1.3.1

(1 theme extensions excluded)

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyonecf:30548226
2i9eh265:30646982
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupyter:31046869
pythonrstrctxt:31112756
nativeloc1:31192215
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31314491
pythonpulldiag:31325930
996jf627:31283433
pythonrdcb7cf:31303019
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
slnrequired:31334858
c4b42873:31332228
d7aab740:31332224
usemarketplace:31333563
agentclaude:31334889
4f60g487:31327383
id45c886:31333049
gh_pad_aa_c:31335103
3cc7c867:31335119
testaa123:31335226

[meganrogge]

That suggests that exe is not on your PATH

[Gavin-Williams]

Well - why doesn't vs code look for it. It'll be in the visual studio folder probably. I've installed VS, I've installed the C++ language support in VS Code, I've installed the C++ extension package. You would think after all that, VS Code could compile C++. At least in a normal world, where antiquated details aren't held onto like precious little babies.

Please remove the need for paths, and vcvars and running from developer terminals. Just use the compiler where it's at.

Is there a way to tell VS Code where the compiler is? Because no one else thought to do so!

I put some code that I got from copilot into tasks.json, it still doesn't work. Include paths aren't set. I deleted all the tasks and put a different task in, also suggested by copilot. Still no include path set.

And why do I have to select the compiler every time?

[Gavin-Williams]

I give up - I'll launch VS Code from a developer command prompt - lol - I can't believe everyone is OK with that. Now I've got batch files and shortcuts to batch files, just to have an icon. What a totally ridiculous procedure to setup and build a project.