SDKV12 sdk_config.h "master" ?

[Ray]

Hello. I have a question and a request for Nordic developers.

It is really super-helpful that in SDKV12 you converted to having a master sdk_config.h that contains what seems to be 100% of all sdk config parameters. This is terrific.

What has been making conversion from SDK11 a bit more challenging for me, however, is the fact that I can't seem to find a "master" sdk_config.h that contains 100% of all parameters. It has been a trial and error process that involves scanning the sdk_config.h's contained within the various examples, which seem to have differing subsets of sdk_config.h.

Furthermore, in at least one case I was stumped by the fact that there were no sdk_config.h's at all, in any of the examples, that had a parameter that turned out to be necessary and should have been in there: APP_GPIOTE_ENABLED.

I don't know what other developers do, but what I would like to be able to do each time a new SDK is released is this:

1. Go into a subfolder of /documentation that contains the "master" sdk_config.h for that release
2. Diff it against the "master" sdk_config for the previous release.
3. Manually upgrade my own sdk_config.h's based upon what I find.

I say this because given the number of parameters it can be tricky and error-prone to propagate an app's config parameters from one release to another. If the Nordic devs would maintain the sdk_config.h in a "readily diff-able" manner, it would really help 3rd party devs in sdk transitions.

Thanks for your consideration.

[Ray]

@keton this is a very good point. I'm actually a bit confused about "officially" whether Nordic is suggesting that we put our pin definitions into sdk_config.h, or into custom_board.h (via boards.h && -DBOARD_CUSTOM).

Right now I am maintaining pins in custom_board.h and stripped out the handful of spurious pin definitions from sdk_config.h.

I think it would be helpful for Nordic to give us some definitive guardrails here - such as "put all SDK config parameters into sdk_config.h, and put all your board/pin definitions into custom_board.h", and put all your app and peripheral definitions into your own header files".

If on the other hand we are moving to put all custom board/bsp information into sdk_custom.h, that's also fine. I just think the dev community could use some prescriptive guidance here.

thanks