How can I know which header/c file to include into a project

RE: How can I know which header/c file to include into a project

butch — Sat, 29 Oct 2016 14:22:47 GMT

Probably there is no document since it would be large and have many versions. The SDK seems to change its structure often. The SDK seems to have some spurious includes, not really needed. The build system could be improved (CMake?). C/C++ is mind-numbingly stupid (Rust?). But so far, I prefer the Nordic total package over the many alternatives.

RE: How can I know which header/c file to include into a project

Ed Wios — Sat, 29 Oct 2016 04:53:58 GMT

Yes, this is what I am doing, too. It is a bit unbelievable and sad that the documents provided lacked such important information. There are 200+ views and no answer so far makes me believe this is indeed the case.

RE: How can I know which header/c file to include into a project

butch — Thu, 27 Oct 2016 20:40:40 GMT

The way I do it is to iterate: compile. When you get an undefined symbol, >cd to the SDK directory and >grep -R . That gives you a list files the symbol is in. Manually hunt for the .h file that defines the symbol (many files may reference the symbol.) Modify your makefile: add INC_PATHS += the directory above said file. Iterate. I know it is nasty. But I don't think there is any document that gives the graph of dependencies.