From fee6de844f9d4c3aad87733734d35df50117b6b0 Mon Sep 17 00:00:00 2001 From: Marco Platania Date: Thu, 18 May 2017 11:09:08 -0400 Subject: Change location of VES5.0 code Change-Id: If8a1173813eb4d5c14c04b132269696a748505e7 Signed-off-by: Marco Platania --- vnfs/VES5.0/doxygen-1.8.12/html/doxygen_usage.html | 111 +++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 vnfs/VES5.0/doxygen-1.8.12/html/doxygen_usage.html (limited to 'vnfs/VES5.0/doxygen-1.8.12/html/doxygen_usage.html') diff --git a/vnfs/VES5.0/doxygen-1.8.12/html/doxygen_usage.html b/vnfs/VES5.0/doxygen-1.8.12/html/doxygen_usage.html new file mode 100644 index 00000000..f8ffc32d --- /dev/null +++ b/vnfs/VES5.0/doxygen-1.8.12/html/doxygen_usage.html @@ -0,0 +1,111 @@ + + + + + + + +Doxygen: Doxygen usage + + + + + + + + + + + +
+
+ + + + + + +
+
Doxygen +
+
+
+ + +
+
+ +
+
+
+ +
+
+
+
Doxygen usage
+
+
+

Doxygen is a command line based utility. Calling doxygen with the --help option at the command line will give you a brief description of the usage of the program.

+

All options consist of a leading character -, followed by one character and one or more arguments depending on the option.

+

To generate a manual for your project you typically need to follow these steps:

    +
  1. +You document your source code with special documentation blocks (see section Special comment blocks).
  2. +
  3. +You generate a configuration file (see section Configuration) by calling doxygen with the -g option:
    doxygen -g <config_file>
    +
  4. +
  5. +You edit the configuration file so it matches your project. In the configuration file you can specify the input files and a lot of optional information.
  6. +
  7. +You let doxygen generate the documentation, based on the settings in the configuration file:
    doxygen <config_file>
    +
  8. +
+

If you have a configuration file generated with an older version of doxygen, you can upgrade it to the current version by running doxygen with the -u option.

doxygen -u <config_file>
+

All configuration settings in the original configuration file will be copied to the new configuration file. Any new options will have their default value. Note that comments that you may have added in the original configuration file will be lost.

+

+Fine-tuning the output

+

If you want to fine-tune the way the output looks, doxygen allows you generate default style sheet, header, and footer files that you can edit afterwards:

    +
  • +

    For HTML output, you can generate the default header file (see HTML_HEADER), the default footer (see HTML_FOOTER), and the default style sheet (see HTML_STYLESHEET), using the following command:

    doxygen -w html header.html footer.html stylesheet.css <config_file>
    +

    The config_file is optional. When omitted doxygen will search for a file named Doxyfile and process that. When this is also not found it will used the default settings.

    +

    +
  • +
  • +For $\mbox{\LaTeX}$ output, you can generate the first and last part of refman.tex (see LATEX_HEADER and LATEX_FOOTER) and the style sheet included by that header (normally doxygen.sty), using the following command:
    doxygen -w latex header.tex footer.tex doxygen.sty <config_file>
    +
    If you need non-default options (for instance to use extra $\mbox{\LaTeX}$ packages) you need to make a config file with those options set correctly and then specify that config file after the generated files (make a backup of the configuration file first so you don't loose it in case you forget to specify one of the output files).
  • +
  • +For RTF output, you can generate the default style sheet file (see RTF_STYLESHEET_FILE) using:
    doxygen -w rtf rtfstyle.cfg
    +
  • +
+
Warning
When using a custom header you are responsible for the proper inclusion of any scripts and style sheets that doxygen needs, which is dependent on the configuration options and may changes when upgrading to a new doxygen release.
+
Note
    +
  • +If you do not want documentation for each item inside the configuration file then you can use the optional -s option. This can use be used in combination with the -u option, to add or strip the documentation from an existing configuration file. Please use the -s option if you send me a configuration file as part of a bug report!
  • +
  • +To make doxygen read/write to standard input/output instead of from/to a file, use - for the file name.
  • +
+
+

+Go to the next section or return to the + index. +

+
+
+ + + + -- cgit 1.2.3-korg