RE: How to make SDK 17.0.2 dependencies dynamic

jake11212 — Tue, 11 Jan 2022 19:22:19 GMT

Okay I understand thank you! I was misunderstanding that the path is relative to the project location so in the relative paths the number of levels to move up is the number of levels between the SDK and the project file.

RE: How to make SDK 17.0.2 dependencies dynamic

Karl Ylvisaker — Tue, 11 Jan 2022 08:01:06 GMT

Hello Jake,

It sounds like you are looking for 'relative paths' here, and it is what is used by the SDK examples by default. If you open an unmodified example project in the SDK and navigate to Options -> Common configuration -> Preprocessor -> User Include Directories you can see how the paths usually look when relatively pointing to something within the SDK folder itself - without concern for where the SDK root might be placed.

The relative paths looks like this:

../../../../../../modules/nrfx/drivers/include

And is relative to the location of the SES project file. So, this particular example path goes up 6 levels - to the SDK root - before traversing down /modules/nrfx/drivers/include
If you make sure to only use relative paths in your project, you should be able to share it with a colleague easily, as long as they place the SES project file at the same hierarchal level in the SDK.

Please let me know if any part of this should still be unclear, or if you have any additional questions to this!

Best regards,
Karl