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

Why is sdk_config contained in almost every example instead of app_config?

While writing our nRF5 based application, we have used an app_config.h in our project. This is advised as one of the solutions for updating the configuration of the SDK in your getting started guide for many version of the SDK, V15 included. I'd like to ask what the reason is for suggesting this, alongside overriding the sdk_config.h file. It seems like having the app_config is an all around a better option.

Maybe someone could enlighten me.

Parents
  • This case might be useful. From my understanding, the sdk configuration file is used for changing settings that apply to the sdk modules which are common for all projects, whereas the app_config header file is used to apply settings specific to one application. So for me it makes sense to make changes to the app_config header file if those changes should only apply to the current application & not all sdk projects.

Reply
  • This case might be useful. From my understanding, the sdk configuration file is used for changing settings that apply to the sdk modules which are common for all projects, whereas the app_config header file is used to apply settings specific to one application. So for me it makes sense to make changes to the app_config header file if those changes should only apply to the current application & not all sdk projects.

Children
No Data
Related