|
| 1 | +## Default configuration, generated by rosdoc2. |
| 2 | + |
| 3 | +## This 'attic section' self-documents this file's type and version. |
| 4 | +type: 'rosdoc2 config' |
| 5 | +version: 1 |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +settings: |
| 10 | + ## If this is true, a standard index page is generated in the output directory. |
| 11 | + ## It uses the package information from the 'package.xml' to show details |
| 12 | + ## about the package, creates a table of contents for the various builders |
| 13 | + ## that were run, and may contain links to things like build farm jobs for |
| 14 | + ## this package or links to other versions of this package. |
| 15 | + |
| 16 | + ## If false, you can still include content that would have been in the index |
| 17 | + ## into one of your '.rst' files from your Sphinx project, using the |
| 18 | + ## '.. include::' directive in Sphinx. |
| 19 | + ## For example, you could include it in a custom 'index.rst' so you can have |
| 20 | + ## the standard information followed by custom content. |
| 21 | + |
| 22 | + ## TODO(wjwwood): provide a concrete example of this (relative path?) |
| 23 | + |
| 24 | + ## If this is not specified explicitly, it defaults to 'true'. |
| 25 | + generate_package_index: true |
| 26 | + |
| 27 | + ## This setting, if true, attempts to run `doxygen` and the `breathe`/`exhale` |
| 28 | + ## extensions to `sphinx` regardless of build type. This is most useful if the |
| 29 | + ## user would like to generate C/C++ API documentation for a package that is not |
| 30 | + ## of the `ament_cmake/cmake` build type. |
| 31 | + always_run_doxygen: false |
| 32 | + |
| 33 | + ## This setting, if true, attempts to run `sphinx-apidoc` regardless of build |
| 34 | + ## type. This is most useful if the user would like to generate Python API |
| 35 | + ## documentation for a package that is not of the `ament_python` build type. |
| 36 | + always_run_sphinx_apidoc: false |
| 37 | + |
| 38 | + # This setting, if provided, will override the build_type of this package |
| 39 | + # for documentation purposes only. If not provided, documentation will be |
| 40 | + # generated assuming the build_type in package.xml. |
| 41 | + # override_build_type: 'ament_python' |
| 42 | + |
| 43 | + # This boolean setting, if provided, determines whether the external dependencies of a package |
| 44 | + # are shown in the home page of the documentation, which is useful for packages that are only |
| 45 | + # used to force loading of other packages (which are sometimes called meta packages). |
| 46 | + # If not set, then the decision to show the external dependencies is made on the following |
| 47 | + # heuristics: show if the package has no build_depend, does have exec_depend, and has no |
| 48 | + # subdirectories except an optional doc/ subdirectory. |
| 49 | + show_exec_dep: false |
| 50 | +builders: |
| 51 | + ## Each stanza represents a separate build step, performed by a specific 'builder'. |
| 52 | + ## The key of each stanza is the builder to use; this must be one of the |
| 53 | + ## available builders. |
| 54 | + ## The value of each stanza is a dictionary of settings for the builder that |
| 55 | + ## outputs to that directory. |
| 56 | + ## Required keys in the settings dictionary are: |
| 57 | + ## * 'output_dir' - determines output subdirectory for builder instance |
| 58 | + ## relative to --output-directory |
| 59 | + ## * 'name' - used when referencing the built docs from the index. |
| 60 | + |
| 61 | + - doxygen: { |
| 62 | + name: 'explicitly not showing dependencies', |
| 63 | + output_dir: 'generated/doxygen' |
| 64 | + } |
| 65 | + - sphinx: { |
| 66 | + name: 'dont_show_dep', |
| 67 | + ## This path is relative to output staging. |
| 68 | + doxygen_xml_directory: 'generated/doxygen/xml', |
| 69 | + output_dir: '' |
| 70 | + } |
0 commit comments