![]() This will be done by incorporating Doxygen into the CMake. The compiler includes all files as desired, as they are all contained in the project defintion. The goal of this first part is to get some warnings about missing documentation to appear in the build process. What to do about this?ītw - the "usecase" is simple: It's a visual studio project. It is actually only one of the tools for doxygen, and not the most important one. It seems my question is related to this, however the only promising answer is the comment by saying it was an issue that has been fixed in doxygen version 1.7.4. It looks like doxygen-1.8.4 binaries lack as well the doxytag, so that the only way is to modify the Makefile.in or Makefile and comment the installation of bin/doxytag. The output XML of Doxygen for ExampleType (file: xml/struct_example_type.xml) is: įloat ExampleType::arrayĪctually, I would expect ARRAY_LENGTH to be replaced by (20u) and optional_char should not be a member of the struct. My changes with regard to the default Doxygen configuration file (using Doxygen 1.8.2) are: INPUT =. cpp files, though Doxygen won’t use them extensively. But, you should still comment code in your. The comments are included in the header files (.h) files. To use Doxygen, you write comments in code using the format that Doxygen understands. This is the listing of example_include.h: #define MY_FALSE (0u) Birds-eye view of how Doxygen works There are two main steps in using Doxygen: 1. If the PERLMODLATEX tag is set to YES Doxygen will generate the necessary Makefile. This is the listing of example.h: #include "example_include.h" A template extensions file can be generated using doxygen -e rtf. I made up an example consisting of two headers and a Doxygen file: subdir/example.h I do not get the doxygen preprocessor to recursively include files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |