I need some basic help using Doxygen in C code. All basic documents look great, and I want to help structure a long, long list of files and functions.
I have a source C tree that looks like this:
src/ +
Very standard. Doxygen currently generates a flat file list of all files. We refer to every dub-dir src / as a βmoduleβ, and therefore documenting this seems to be good compatibility with Doxygen modules / groups.
How exactly should I use grouping commands to mirror the directory structure above? I want the module to be used in generated documents that reference documents file1 and file2. Just like JavaDoc will handle the package.
Adding the / addtogroup util and @ {tags to each header file created a mini-site with a flattened list of all data structures, etc. in all the headlines, which I did not expect or did not want. Perhaps this is what doxygen groups should do, i.e. Document API evenly when code is implemented across multiple files?
source share