do the files in the build directory go into source control?

[Allen]

Hello,

I used the nRF Connect plugin for VCS to create a Zephyr/BLE project. It appears this copies many files into the "build" directory which are required to compile the project. Normally things under "build, debug, release. ..." are artifacts of a build and are not put into source control.

What are the source code guidelines for a nRF Connect SDK based project?

TIA

[Einar Thorsrud]

Hi,

There is no need to check in the build folder in source control. This is automatically generated when you build and can be discarded at any time. (The only thing you need to remember here, which is occasionally forgotten, is that any changes you do with menuconfig/guiconfig are done within the build folder. So to make persistent changes in the configuration you need to do these outside of the build folder, typically in prj.conf - see here).

Einar

[Allen]

Hello,

I followed your advice and did not include the build directory in source control. Unfortunately when you do that, it appears that you loose the board configuration? At least when I clone to a clean directory it doesn't know about the build configuration.

What needs to be saved to preserve the board configuration?

[Einar Thorsrud]

Hi,

What do you man by board configuration? If that is adjustments to the device tree(?), then you can do that the same for the device tree configuration as a prj.conf, using a devicetree overlay. Also, if you have a custom board you typically make a specific board file for that (you may still want overlays though, for instance if there are variations of it or similar).

[Allen]

When I cloned the repo into a clean directory and opened it using the VCS plugin, the plugin didn't know a board/build configuration existed.