-
I have been working a lot with doxygen and fortran on the PIO project. Although there are some gotchas, it's possible to have documenation with the code, and get the usual benefits of doxygen, includi…
-
Doxygen headers have been added for all files, but function and class documentation needs to be added (starting with drishti public API).
TODO: The standard library style namespace macros (which prev…
-
The doxygen code indicates that the OR conjunction is supported, but inspection of the source code for find_object() suggests it is not implemented.
Immediate fix is to remove OR from the doxygen d…
-
Although not related to CMake, I post this issue here because the problem was encountered in many packages and the best place to provide a solution is this package.
This is mostly for reporting as I …
-
-
"If USE_STAMP_FILE is set, the custom command defined by this function will create a stamp file with the name .stamp in the current binary directory whenever doxygen is re-run. With this option presen…
ghost updated
8 months ago
-
Hi there!
First, a bit of context:
I have several embedded C projects documented with Doxygen. My company's rules demand that we generate PDF documentation (yes, I know). We're currently using a…
-
From emails this week: we should support higher level documentation that covers multiple library features (e.g., extracting Lagrangian data). It should be possible to add this type of page to the gene…
-
The first step of that task is to make sure our CMake scripts display information about which third-party libraries that are available, and which versions.
Then, in the testsuite scripts (collection …
-
## Summary
We should really update our doxygen comments throughout the code base. Also, work towards better commenting and documentation in general.
Sample Doxygen comment:
```
//! This class re…