• State Suggested Answer
  • +3 person also asked this people also asked this
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 70 subscribers
  • Views 23280 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 201208
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Create a new project in Segger Embedded Stuido

Ars Morozov

Hello.

Actually I have two qustions, but they are related with the same challenge.

So, I want to develop application using SDK (libararies and config), but starting from empty project. To create empty buildable project for nRF52DK I need to include a lot of necessery files, such as sdk_config.h, boards.c ... etc. So, can you give list of all files, which I need to include in project, to be able to correctly build it, and also which configuration I need to do? For example what I need to do to create project the same as examples/peripheral/template_project?

I also want to know, how to change folder of existing project? For example if I change directory of template_project from examples, how can I repair links to necessery files?

Parents
  • 0

    Hey Arsenii,

    Take a look at our Introduction to SES videos. 

    You should also use one of our example projects as a template. 

    Cheers,

    Håkon.

  • 0 in reply to haakonsh

    I watched the tutorials and they don't really talk about creating a new project either from scratch or from an existing project.

    I tried opening one of the examples and then doing Save As on the solution. It let me save it, but then all of the files in the project would not open. For example when I double click on the main.c file it says it can't fine C:\main.c. That is not where I saved the solution. When I double clicked on another files it said it couldn't find a file at some path like ..\..\components\ etc.

    It looks like all of the paths are relative to the project solution file.

    You see, the main thing is that I don't want to be saving my own project files inside of the examples folder inside of the SDK folder. That doesn't seem like a very good idea since someday I might want to update / upgrade the sdk and having my own projects files inside of it doesn't make sense.

    So the big question everyone wants to know is what is the proper way to start a new project and save it in your own location and have all of the relative paths get fixed without having to do that all myself?

Reply
  • 0 in reply to haakonsh

    I watched the tutorials and they don't really talk about creating a new project either from scratch or from an existing project.

    I tried opening one of the examples and then doing Save As on the solution. It let me save it, but then all of the files in the project would not open. For example when I double click on the main.c file it says it can't fine C:\main.c. That is not where I saved the solution. When I double clicked on another files it said it couldn't find a file at some path like ..\..\components\ etc.

    It looks like all of the paths are relative to the project solution file.

    You see, the main thing is that I don't want to be saving my own project files inside of the examples folder inside of the SDK folder. That doesn't seem like a very good idea since someday I might want to update / upgrade the sdk and having my own projects files inside of it doesn't make sense.

    So the big question everyone wants to know is what is the proper way to start a new project and save it in your own location and have all of the relative paths get fixed without having to do that all myself?

Children
  • 0 in reply to Tony

    I also want to say that one of the main reasons to want to do this is because I don't want to be modifying the existing examples and saving them in place. I want to make sure the examples stay the way they are and copy them to my new project.

    It would also be nice if I could reference files in another place that I won't be changing, but ensure that any files I will be modifying will be my own copies and not the originals.

Related