I've used Segger Embedded Studio to compile and run a number of example projects -- nicely done!
Now I'm ready to start creating my own projects, with the ultimate goal of releasing one or more supported projects, but it's a challenge to find a project file structure is idiomatically correct for the nRF5 sdk.
The Question
I'd like to know how other people maintain nRF5 projects, or if there are good online examples of same.
Some Specifics
Assume I have a project directory named myWorkspace/myProj/
. I want to capture a snapshot of the SDK so I can work from a stable base, and put everything under .git control:
- Would you copy the SDK
components/
directory intomyProj/components/
? Or would you copy it tomyWorkspace/components
so it could be used across multiple projects? - Ditto for
config/
: would you copy it to the project directory, or to the workspace directory? - I'm using the SEGGER Embedded Studio and want to use SEGGER_RTT for debugging I/O. Would you copy (only)
external/segger_rtt/
to the project directory, or to the workspace directory? Or would you copy the entireexternal/
directory? (Or something else?) - What about
external_tools/
andsvd/
? - Once everything is in place, what's the best way to create a blank project? (This may be more of a SEGGER question than a Nordic question.)
- I'm assuming that I'd put 'myWorkspace/' under git control so it can capture the entire state of things. If there's a better approach, I'd like to know.
Thanks in advance!