The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I recently took over maintenance for rosdoc_lite, but am not yet familiar with the code. Please bear with me while trying to figure this out.
Doxygen is invoked with a template file that sets the CALL_GRAPH to NO. I don't see any option for overriding that template file or replacing it with one of your own.
The comments immediately before, recommend enabling caller graphs for selected functions only using the \callergraph command. Is that an option for you?
| | 2 | No.2 Revision |
I recently took over maintenance for rosdoc_lite, but am not yet familiar with the code. Please bear with me while trying to figure this out.
Doxygen is invoked with a template file that sets the CALL_GRAPH to = NO. I don't see any option for overriding that template file or replacing it with one of your own.
The comments immediately before, recommend enabling caller graphs for selected functions only using the \callergraph command. Is that an option for you?
| | 3 | No.3 Revision |
I recently took over maintenance for rosdoc_lite, but am not yet familiar with the code. Please bear with me while trying to figure this out.
Doxygen is invoked with a template file that sets CALL_GRAPH = NO. I don't see any option for overriding that template file or replacing it with one of your own.
The comments immediately before, before recommend enabling caller graphs only for selected functions only functions, using the \callergraph command. Is that an option for you?
| | 4 | No.4 Revision |
I recently took over maintenance for rosdoc_lite, but am not yet familiar with the code. Please bear with me while trying to figure this out.
Doxygen is invoked with a template file that sets CALL_GRAPH = NO. I don't see any option for overriding that template file or replacing it with one of your own.own. Some variables, such as FILE_PATTERNS, can have per-package values defined in rosdoc.yaml, but CALL_GRAPH is not one of them.
The comments immediately before recommend enabling caller graphs only for selected functions, using the \callergraph command. Is that an option for you?
| | 5 | No.5 Revision |
I recently took over maintenance for rosdoc_lite, but am not yet familiar with the code. Please bear with me while trying to figure this out.
Doxygen is invoked with a template file that sets CALL_GRAPH = NO. I don't see any option for overriding that template file or replacing it with one of your own. Some variables, such as FILE_PATTERNS, can have per-package values values defined in rosdoc.yaml, but CALL_GRAPH is not one of them.
The comments immediately before recommend enabling caller graphs only for selected functions, using the \callergraph command. Is that an option for you?
| | 6 | No.6 Revision |
I recently took over maintenance for rosdoc_lite, rosdoc_lite, but am not yet familiar with the code. Please bear with me while trying to figure this out.
Doxygen is invoked with a template file that sets CALL_GRAPH = NO. I don't see any option for overriding that template file or replacing it with one of your own. Some variables, such as FILE_PATTERNS, can have per-package values defined in rosdoc.yaml, but CALL_GRAPH is not one of them.
The comments immediately before recommend enabling caller graphs only for selected functions, using the \callergraph command. Is that an option for you?
UPDATE: the main purpose of rosdoc_lite is automatically generating documentation for packages listed on the ROS wiki or similar destinations. The main reason for running it locally is to check updates to those docs before committing them.
If your documentation goals differ, running Doxygen directly may make more sense.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
