Replies: 2 comments
-
The main benefit is that the C++ sources for doxygen invocation are collected from the sources of the target. If any source is changed or added, doxyfile is updated and doxygen re-run. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the prompt feedback. That's valuable information. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi
As I understand, the doxygen rule doesn't support the specification of a configuration file (Doxyfile), instead it expects to set all supported config parameters in the using statement with doxygen:param statements, which are then added to a Doxyfile that is generated by b2. Is this correct? If so, using this rule doesn't look very attractive compared with simply using a make rule and call doxygen directly with a predefined Doxyfile.
I am wondering whether there are any other reasons for using the doxygen rule instead of the make rule approach that I am overlooking.
Please let me know.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions