Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Suggestion for Simplifying Include Paths

In order to simply the creation of nRF softdevice projects, I'd like to make a suggestion. Rather than require the end-programmer to include dozens of individual include paths in their project, it would be much preferable to reference all includes from the base SDK directory.

For example, rather than putting:

#include "nordic_common.h"

Use

#include "components/libraries/util/nordic_common.h"

If this format were followed throughout the Nordic SDK, it would also make it easier to redirect which SDK version the compiler looks at since you only need to change the base Include path.

Thanks!

Parents
  • Along these lines, is there anywhere that I can add a file path to the nRF52 SDK using Keil other than in the individual projects?  For some reason, the relative path to core_cm4.h is not included in the predefined paths.  This means that I have to add this path to every example that I want to run in order to be able to build it.  It doesn't appear to be in the sdk_config.h files.

Reply
  • Along these lines, is there anywhere that I can add a file path to the nRF52 SDK using Keil other than in the individual projects?  For some reason, the relative path to core_cm4.h is not included in the predefined paths.  This means that I have to add this path to every example that I want to run in order to be able to build it.  It doesn't appear to be in the sdk_config.h files.

Children
Related