Hyvää päivää,
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. If what I want can't be achieved then I'd like to dump SES and get back to the familiar complications of eclipse. I find it hard to believe that a thousand other people don't have similar needs. So my basic question is: Am I wasting my time on SES?
I have group of applications that have a lot of similarities, and thus share a lot of code . They run on different 52-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 tandem. 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 examples by putting an ses project 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 ses project. And 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 examples directory which seems like a messy solution, especially when I want to upgrade to nrf_sdk_16.
I'd really be grateful for some experienced input, and it seems like I'm not alone, judging by the similar requests on the forum.
Kitos, and thanks.
//Mik
