For my projects, I often use the SDK from my silliconvendor. This SDK is unpacked in a directory, named after the version of the SDK. Thus, for example: "lib/nRF5_SDK_15.3.0_59ac345".
I want to define an SDK_ROOT macro in my project and refer to files from this directory through this define, e.g. "$(SDK_ROOT)/components/ble/common/ble_advdata.c". This works fine in the SES project manager.
However, these modules usually have their interface described in a header file which lives at the same location. Thus, I would like to add "$(SDK_ROOT)/components/ble/common" to the list of (user) include directories. This does not work for some reason - none of the include files can be found.
Is this a bug? Known issue perhaps? The options dialog does say it supports macro's...
I want to define an SDK_ROOT macro in my project and refer to files from this directory through this define, e.g. "$(SDK_ROOT)/components/ble/common/ble_advdata.c". This works fine in the SES project manager.
However, these modules usually have their interface described in a header file which lives at the same location. Thus, I would like to add "$(SDK_ROOT)/components/ble/common" to the list of (user) include directories. This does not work for some reason - none of the include files can be found.
Is this a bug? Known issue perhaps? The options dialog does say it supports macro's...