VS Code build configurations in version control

RE: VS Code build configurations in version control

Nick — Wed, 19 Mar 2025 22:05:56 GMT

Does this keep the build configuration linked with the CMakePresets.json file so that if the configuration is later updated and the changes are pushed to git, everyone's configurations will update?

RE: VS Code build configurations in version control

Kazi Afroza Sultana — Wed, 10 Jan 2024 17:52:56 GMT

Hello,

I have feedback from team.

You should not put the build directory itself in version control, as that will conflict every time anyone tries to build on your own machine. The recommended solution to this problem (at least in the VS Code context) is storing the build configuration as a CMake preset: https://nrfconnect.github.io/vscode-nrf-connect/guides/build_config.html#how-to-save-a-build-configuration-as-a-preset

RE: VS Code build configurations in version control

Kyle — Tue, 09 Jan 2024 16:45:59 GMT

.vscode is not in the .gitignore file. The .gitignore file looks like so:

# editors
*.swp
*~

# build
/build*/

And this is the default .gitignore you get when you clone a sample. And in the workspace .vscode directory, all it has is settings.json, which does not have anything to do with the build configuration in it.

RE: VS Code build configurations in version control

Kazi Afroza Sultana — Tue, 09 Jan 2024 15:52:43 GMT

Hello,

You need to remove the .vscode from the .gitignore file.

Thanks.

Kazi