This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

segger studio: how to export project?

Hi All,

I would like to export all project files to an archive. Since the Nordic SDK files are all over the place that does not seem to be that easy.

Is there an "export project" function in segger studio and where would I find it?

Regards,

Parents
  • Hi

    I'm afraid SES does not have an export function. Most IDEs (to my knowledge) have an import function though, where you can import projects from another IDE to fit that IDE's structure. Keep in mind that it's only the project file(s) that is specific to SEGGER, and all the libraries and drivers are general .c/.h files compliant with the C language.

    Best regards,

    Simon

  • Hi Simon,

    thank you for clarifying this; with all those menus and context dependent mouse clicks I was not sure that I overlooked something.

    I can of course zip all the relevant files up but then the person receiving them has to have the same installation directories.  Relative path doesn't work because libraries are in a totally different part of the directory structure compared to the .c .h files.

    I think segger could have done better; I know IDEs from other semiconductor companies where you can export a project, send it to somebody who imports it and than has all the files to replicate the build.

    But then again this may have been intentional; an attempt to keep people with segger once you made the mistake of importing and working with their IDE. Same business model seems to be embraced by all semiconductor companies now as well (incl. nordic sdk); no way to move to a different processor once you started using their software infrastructure. Portability and reusability of software seem to be forgotten concepts...

    Regards,

Reply
  • Hi Simon,

    thank you for clarifying this; with all those menus and context dependent mouse clicks I was not sure that I overlooked something.

    I can of course zip all the relevant files up but then the person receiving them has to have the same installation directories.  Relative path doesn't work because libraries are in a totally different part of the directory structure compared to the .c .h files.

    I think segger could have done better; I know IDEs from other semiconductor companies where you can export a project, send it to somebody who imports it and than has all the files to replicate the build.

    But then again this may have been intentional; an attempt to keep people with segger once you made the mistake of importing and working with their IDE. Same business model seems to be embraced by all semiconductor companies now as well (incl. nordic sdk); no way to move to a different processor once you started using their software infrastructure. Portability and reusability of software seem to be forgotten concepts...

    Regards,

Children
No Data
Related