VS Code build configurations in version control

[JordanK]

I'd like my VS Code build configuration for my project to be included in version control.

It seems like this configuration is stored somewhere in the "build" directory that is specified when creating the configuration. However, the "build" directory is excluded from version control in the .gitignore file that is included in all samples.

Which file(s) in the build directory do I need to commit into version control for build configurations to be available to all users who clone the repository?

[Kazi Afroza Sultana]

Hello,

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

Thanks.

BR

Kazi

[JordanK]

.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.

[Kazi Afroza Sultana]

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

[Nick]

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?