Finding module dependencies

RE: Finding module dependencies

haakonsh — Mon, 09 Jul 2018 14:09:27 GMT

Yeah, that's a bit more tricky, I think there's possibly a runtime error if multiple backends is not supported in the logger module, but what we want is to catch it with the preprocessor.

Interdependencies, are way harder to catch. I usually use snippets from the sdk_config's from whatever example uses the relevant module. It's manual cut n paste :/

RE: Finding module dependencies

rconaway — Fri, 06 Jul 2018 16:33:45 GMT

That's a good suggestion. I can write a tool to extract headers from a module, compare it to the ones I've already got in my include path and .c files and adjust accordingly.

Any suggestions about how to fix sdk_config.h? Configuration settings are more than just "turn this module on". It looks like there are interdependencies and possibly even conflicts. I.e. when I turn on UART logging, I may have to turn off RTT logging.

RE: Finding module dependencies

haakonsh — Fri, 06 Jul 2018 14:18:01 GMT

I guess you'll have to go into the modules and see which header files are included. If an included header file contains a function prototype you'll know that there's a corresponding source file, usually with the same name, that have to be included in the build.

RE: Finding module dependencies

rconaway — Fri, 06 Jul 2018 13:42:39 GMT

Thanks for the reply. I've used SES and the configuration wizard. Recently, though, I've been just using make, since it's easier to research and compare projects.

I double checked the wizard. It seems to just display the contents of sdk_config.h in a GUI. Which might be useful if you know what configurations are needed. It doesn't do anything to add source files to the project.

My problem is knowing what needs to be added to a project to use a module.

BTW, I'm familiar with the reference sdk_config.h in config/nrf52840/config. Again, the problem is knowing what needs to be turned on.

RE: Finding module dependencies

haakonsh — Fri, 06 Jul 2018 09:30:04 GMT

You're missing Segger Embedded Studios and the CMSIS configuration wizard. SES takes care of your makefiles, the configuration wizard presents the sdk_config file in a GUI with tick boxes and drop-downs.

Nordic Semiconductor pays Segger a license fee in order to offer SES to our customers for free, as long as you're using our products ofc.

See http://www.nordicsemi.com/eng/Products/SEGGER-Embedded-Studio-IDE and the SES video tutorial.