Hi,
I'm moving from Eclipse to SES which on the face of it seems smoother and cleaner. My problem is figuring out how to setup my projects. Can I do what I want with SES?
I have group of applications that have a lot of similarities, and thus share a lot of code . They run on different nRF52-series modules with different peripheral devices. They are all contained in a single directory tree under git control.
I want to set up SES so that I can develop applications in tight lock-step. So I'd like all the applications to be somehow visible in the explorer, so I can compare chunks from different apps, and compile the whole lot in one go for example. So the conceptual structure I think I want is as follows:
---------------
my-group // a bunch of stuff I can open in one go with SES
application#1
config+code for hardware variant #1
config+code for hardware variant #2
...
config+code for hardware variant #n
application#1
config+code for hardware variant #1
...
my-group-source-library#1
my-group-source-library#2
nRF_SDK - shared by other groups/solutions
-----------------
I see that NordicSemi have simplified SES examples by putting an ses project file in each example directory under the appropriate hardware sub-dir. So for example, I have to dig down to blinky_pca10040 before I can open the corresponding ses project. But then I don't get to see the other parts of my group/solution. Maybe an extra user guide is required.
I see a suggestion that I should simply add my project to the list of projects in the nrf_sdk examples directory which seems like a messy solution, especially when I want to upgrade to the latest sdk.
Please would some experienced guru throw me a line. Even a pointer to a similar project structure that I could use as a model could be a life-saver.
Thanks
//Mik
I'm moving from Eclipse to SES which on the face of it seems smoother and cleaner. My problem is figuring out how to setup my projects. Can I do what I want with SES?
I have group of applications that have a lot of similarities, and thus share a lot of code . They run on different nRF52-series modules with different peripheral devices. They are all contained in a single directory tree under git control.
I want to set up SES so that I can develop applications in tight lock-step. So I'd like all the applications to be somehow visible in the explorer, so I can compare chunks from different apps, and compile the whole lot in one go for example. So the conceptual structure I think I want is as follows:
---------------
my-group // a bunch of stuff I can open in one go with SES
application#1
config+code for hardware variant #1
config+code for hardware variant #2
...
config+code for hardware variant #n
application#1
config+code for hardware variant #1
...
my-group-source-library#1
my-group-source-library#2
nRF_SDK - shared by other groups/solutions
-----------------
I see that NordicSemi have simplified SES examples by putting an ses project file in each example directory under the appropriate hardware sub-dir. So for example, I have to dig down to blinky_pca10040 before I can open the corresponding ses project. But then I don't get to see the other parts of my group/solution. Maybe an extra user guide is required.
I see a suggestion that I should simply add my project to the list of projects in the nrf_sdk examples directory which seems like a messy solution, especially when I want to upgrade to the latest sdk.
Please would some experienced guru throw me a line. Even a pointer to a similar project structure that I could use as a model could be a life-saver.
Thanks
//Mik