How to stop the CMake build panel from automatically opening in VS Code? - Stack Overflow

There are two actions which cause the CMake output panel to automatically open in VS Code.

1. Restarting VS Code. CMake runs some configuration when VS Code starts, and this causes the panel to be automatically reopened
2. Saving a modified CMakeLists.txt

Here is a screenshot of the output panel to clarify which object this is.

The automatic appearance of this panel on startup is slightly annoying but tolerable. However, the automatic loading when a CMakeLists.txt (or other CMake related file) is modified is disruptive because typically the panel will take up about 1/3rd of the screen space, causing other tabs to resize significantly.

Is there any way to stop this from happening?

There are two actions which cause the CMake output panel to automatically open in VS Code.

1. Restarting VS Code. CMake runs some configuration when VS Code starts, and this causes the panel to be automatically reopened
2. Saving a modified CMakeLists.txt

Here is a screenshot of the output panel to clarify which object this is.

The automatic appearance of this panel on startup is slightly annoying but tolerable. However, the automatic loading when a CMakeLists.txt (or other CMake related file) is modified is disruptive because typically the panel will take up about 1/3rd of the screen space, causing other tabs to resize significantly.

Is there any way to stop this from happening?

• visual-studio-code
• cmake

Share Improve this question Follow asked Feb 2 at 9:19 user2138149user2138149 17.7k3030 gold badges149149 silver badges296296 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

Using the command palette, open your User Settings or Workspace Settings, as either the UI or the JSON file.

Then set these options to false:

• "Cmake: Configure On Edit" (cmake.configureOnEdit)
• "Cmake: Configure On Open" (cmake.configureOnOpen)

{
    ...
    "cmake.configureOnEdit": false,
    "cmake.configureOnOpen": false,
    ...
}

This has not worked reliably in the past, but they worked on it and it hasn't caused me trouble since.