Creating new projects...

[jbmillard]

I have read a number of posts here about creating new projects, most are a couple of years old.  I just want to make sure I'm not missing anything.

I am able to compile and run the examples on the evaluation kit.  I'm using the Segger IDE and the BMD-300 Series Evaluation Kit.  I want to create a new project based on an example and I have copied an example and renamed it and get a bunch of errors when try to compile -- because the paths appear to be individually hardcoded for every file and they are relative.

So:

1) Most of the posts here say to start with an example.  It would appear that you either have to keep your development code in the SDK examples tree (so the relative paths work) or modify the examples.   The only other choice is to copy a project and manually change every include path -- is this true?

2) If you create new projects in the examples directory, how do you do upgrades/updates to the SDK?  Download, install and then copy all your projects to the new directory?  Please tell this isn't what we have to do.

I feel I must be missing something fundamental here if this is what I have to do.

In our development environment, I typically install customer software on C:\ (should really be Program Files, but many seem to want it in the root) and then do development on a networked Z drive which is backed up continuously. With relative paths, this is going to make creating new projects a pain and error prone.

Thanks.

[Øyvind]

Hello jbmillard,

I am able to compile and run the examples on the evaluation kit.  I'm using the Segger IDE and the BMD-300 Series Evaluation Kit.  I want to create a new project based on an example and I have copied an example and renamed it and get a bunch of errors when try to compile -- because the paths appear to be individually hardcoded for every file and they are relative.

Can I ask what SDK version you are using? I'm glad to hear that you are able to compile and run our examples. 

1) Most of the posts here say to start with an example.  It would appear that you either have to keep your development code in the SDK examples tree (so the relative paths work) or modify the examples.   The only other choice is to copy a project and manually change every include path -- is this true?

 Yes, we do encourage people to start with a sample, e.g. our template application. This is to ensure that everything is included from the start, meaning libraries, bluetooth stack (SoftDevice), and drivers. There are some suggestions on how to do this easier, have a look at this thread and this thread. Yes, I agree that these are a couple of years old, but the principle is the same. 

2) If you create new projects in the examples directory, how do you do upgrades/updates to the SDK?  Download, install and then copy all your projects to the new directory?  Please tell this isn't what we have to do.

There are only major differences between major releases, such as v15.3 to v16. Between minor releases, the API is usually the same, i.e. between 15.2 to 15.3. Our current SDK documentation for v16 includes a migration guide on how to transition from 15.3 to 16.

Our current getting started guides are available in our tutorial section, and I agree that not all are up-to-date. There are, however, other sites that give Getting Started Tutorials. I suggest looking into www.novelbits.io, which has several good guides to start with e.g. BLE LightBulb. 

 

In our development environment, I typically install customer software on C:\ (should really be Program Files, but many seem to want it in the root) and then do development on a networked Z drive which is backed up continuously. With relative paths, this is going to make creating new projects a pain and error prone.

 Have a look at this answer regarding relative paths in SES. 

Let me know if anything is unclear!

Kind regards,
Øyvind