How to back up common source libraries

RE: How to back up common source libraries

ovrebekk — Thu, 07 Dec 2017 11:32:15 GMT

I usually only modify one or two files, and I only do it if there is no other option. If you only need to modify the C file then you can keep the include settings as is, and only replace the C file, like I did here.

Any particular reason you have to change a lot of files?
The idea behind the libraries and drivers is that you shouldn't have to change them, for the most part ;)

RE: How to back up common source libraries

MichaelNordicUser — Thu, 07 Dec 2017 06:02:47 GMT

Thanks Torbjørn. For the first approach, mustn't one change include paths one by one? Seems labor intensive and error prone. What makes it so clean for you? Thanks.

RE: How to back up common source libraries

ovrebekk — Tue, 05 Dec 2017 10:19:22 GMT

Hi Michael

I always copy the files into the example project folder in this case. I find it is the cleanest approach, even if it requires some fiddling with your project settings.

If you don't like that approach you could always use Git.
Commit your SDK to a Git repo, and make a separate branch for each project. Then you can change the SDK files to your hearts content, and the changes will only affect that branch.

A third approach is to have all the changes enabled by a unique define, so that only projects that set this define get the changes.

Best regards
Torbjørn