I've hit a problem where Doxygen's preprocessor seems to be emitting a couple of strings incorrectly in some complicated macros. However, without seeing what the preprocessor is actually outputting, I'm unable to make any progress debugging this issue. :-(
Is there any way to run Doxygen's preprocessor in a standalone way; or to somehow keep a copy of the preprocessor's "character buffer" output file (as mentioned in various Doxygen internals pages online)?
Thanks, Nick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone,
I've hit a problem where Doxygen's preprocessor seems to be emitting a couple of strings incorrectly in some complicated macros. However, without seeing what the preprocessor is actually outputting, I'm unable to make any progress debugging this issue. :-(
Is there any way to run Doxygen's preprocessor in a standalone way; or to somehow keep a copy of the preprocessor's "character buffer" output file (as mentioned in various Doxygen internals pages online)?
Thanks, Nick
You can run doxygen as
doxygen -d Preprocessor
as mentioned https://www.stack.nl/~dimitri/doxygen/manual/preprocessing.html. But it will spit out a ton of information, so I highly recommend limiting the FILE_PATTERNS first.