Which files to commit to code repository to save build information (VS Code and git)

I'm trying to commit a VS Code project to source control and don't want to include the entire build directory (with all of the build-generated files). But it seems that all of the information about the build configuration is stored in the build directory. Is there a definitive list of files necessary (to save in a repository) to allow a successful build when cloning the project?

Thanks!

Top Replies

CktDesigner over 1 year ago in reply to Einar Thorsrud +1

I already have a project that builds (and was migrated from the older Segger environment). I also know that I shouldn't commit anything from the build folder. My point was that if the build folder is…
CktDesigner over 1 year ago in reply to Einar Thorsrud +1

Understood... Still doesn't help the situation where the project is cloned from Git (by another user) who has to create a configuration before building...
CktDesigner over 1 year ago in reply to Einar Thorsrud +1

This is understood. But I think you might be missing my original question. I have a project that compiles in VS code using the Nordic nRF Connect extension. I want others to be able to clone the…

0 AMarch01 20 days ago in reply to CktDesigner

I know this is a year ago, but that would be a useful feature. Even if there was some way to create a script that automated the build configuration. The script could be saved in that case.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel