Our project uses nRF Connect SDK v1.5.0. Two main developers work with the files in very different environments.
I am not sure if this was an accident of initial development stages or if that is the proper way, but only a small part of the project files reside in our development folder. The major chunk resides in the Zephyr directory. So first question: is that indeed the correct way?
The directory structure is something like this:
\localdev\projectroot\projectname\... (such as boards, build, src) [THIS is what we usually keep in the GIT repository, with version control]
\localdev\nordic\v1.5.0\zephyr\... (such as boards, cmake, doc, drivers, kernel, samples and many others) [ideally this would contain only "off the shelf files"]
We are very confused as how to handle maintaining such a project in a git repository. Several files in below \nordic need changes, such as drivers, bluetooth configurations, power settings among others. The \zephyr directory has the following issues:
1- It is about 1.5 Gb of size (one could still live with that, but...)
2- It can be overwritten by new files if we update the SDK, and then the project specific changes would be gone.
So main question is: is there a practical way to separate the "customized nordic/zephyr files" into a folder that belongs to our repository structure?
Regards
Bruno
