SDK_config.h inconsistencies

[jev]

I just replaced SDK 14.0 with the shiny new SDK 14.1 in my project. My project uses components from the SDK, but I don't use the exact same structure. Once again, it won't compile out of the box. sigh

Okay, here's the question. I assumed ~\nRF5_SDK_14.1.0_1dda907\config\sdk_config.h to be a typical "master" from which the sdk_config.h files used in the examples are derived. No such luck. I expected this master not to be that different from, for example, from ~\nRF5_SDK_14.1.0_1dda907\examples\peripheral\blinky\pca10040\blank\config\sdk_config.h.

Wrong. It is next to impossible to compare the differences in these two using an automated tool.

Is there another "master" that is being used for creation of the examples?

How can I compare the sdk_config.h from my project (that started life using SDK 13) with the changes required in SDK 14.1?

[jev]

Just received an e-mail  an engineer was assigned to this issue. In the meantime, we remoddeled our software so that it now uses app_config.h which can be included from sdk_config.h automatically. It would be a good idea to provide one sdk_config.h "master" and, in every example, move the changes to this app_config.h. That makes it easier to spot the changes made for that specific example. Whilst on it, I would suggest to include all macro's that are potentially being used to get the example going, even if these macro's are the same as the defaults.

E.g.: if though the default setting for NRFX_SPIM_MISO_PULL_CFG is 1, I would still include a "#define NRFX_SPIM_MISO_PULL_CFG 1" in an example that illustrates the use of SPIM.

[Branden Ghena]

It would really be great if Nordic used this same structure for their examples too so that it would be relatively easy to check which options have been changed from their default for that example to work.