Segger Embedded Studio relative paths

RE: Segger Embedded Studio relative paths

Vidar Berg — Wed, 21 Mar 2018 09:09:46 GMT

Thanks for the clarification It is possible to define your own macros: select Tools from the menu bar in SES, then open options -> Building -> Build -> Global macros.

e.g.,

Once you have defined the macro you need to manually update the source paths.I think the easiest way of doing that is to do a 'search and replace' in your *.emProject file.

RE: Segger Embedded Studio relative paths

xcipolesv — Tue, 20 Mar 2018 17:52:39 GMT

Sorry, I expressed myself a bit misleading.
I noticed that there where relative paths also.
But what I would like to is lika I clearified above. To have source files from, for example SDK, be related to a macro so that if I have SDK stored in a other directory on a different computer the macro could have a different value, not the path to every source file.

Is there a macro expansion performed when the Project file is loaded?

RE: Segger Embedded Studio relative paths

Vidar Berg — Tue, 20 Mar 2018 08:22:15 GMT

Hi,

Please open the *.emProject file in a text editor to confirm whether the source paths are relative or absolute. I tried the same here with SES and relative paths were used both when I added existing and new source files.