![]() ![]() # for a project that appears at the top of each page and should give viewer -58,7 +58,7 PROJECT_LOGO = PROJECT_NUMBER = $(VERSION) +PROJECT_NUMBER = Using the PROJECT_BRIEF tag one can provide an optional one line description # could be handy for archiving the generated documentation or if some version The documentation is also available via web, at:ĭiff -git a/doc/Doxyfile.in b/doc/Doxyfile.in index fba16c4aaa39.b7a76cb16b56 100644 - a/doc/Doxyfile.in +++ b/doc/Doxyfile.in -38,7 +38,7 PROJECT_NAME = libdvbv5 It is possible to generate documentation in html, man pages and pdf formats. +If enabled, it will be built within the project. +In meson, Doxygen documentation is enabled by the auto feature: `doxygen-doc`. To: meson: Add support for doxygenĭiff -git a/README.md b/README.md index b11b7fe2ee80.e1befab71615 100644 - a/README.md +++ b/README.md -201,6 +201,9 the package with autotools, running: H=From:To:Cc:Subject:Date:In-Reply-To:References:From ī=IOCnerfO1VPo1Ll7OL8Km6U7g+5rauoUl7YwcGFC3BuJ72L7VS7cJ7eBg1V1DwXze ![]() Received: from (213-243-189-158.bb.dnainternet.fiīy (Postfix) with ESMTPSA id 2978759D ĭKIM-Signature: v=1 a=rsa-sha256 c=relaxed/simple d= īh=XPKxGinDMdHQlRxZ2tj8dCeXqBiMdmkE/2p30/Y/4bM= Received: from (īy (Postfix) with ESMTPS id D80472887D Received: from ( )īy (Postfix) with ESMTP id 4284CC6379F To make doxygen read/write to standard input/output instead of from/to a file, use - for the file name.X-Spam-Checker-Version: SpamAssassin 3.4.0 () onĪ Please use the -s or -x or -x_noenv option if you send me a configuration file as part of a bug report or post an issue on GitHub! (see also: How to report a bug) To get a minimal configuration file use the -x or -x_noenv option to show only the differences from the default doxygen configuration file. This can use be used in combination with the -u option, to add or strip the documentation from an existing configuration file. If you do not want documentation for each item inside the configuration file then you can use the optional -s option. 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 change when upgrading to a new doxygen release. ![]() If you need non-default options (for instance to use extra packages) you need to make a configuration file with those options set correctly and then specify that configuration 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).įor RTF output, you can generate the default style sheet file (see RTF_STYLESHEET_FILE) using: doxygen -w rtf rtfstyle.cfg ![]() When this is also not found it will used the default settings.įor 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 When omitted doxygen will search for a file named Doxyfile and process that. 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:įor 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 Note that comments that you may have added in the original configuration file will be lost. Any new options will have their default value. doxygen -u Īll configuration settings in the original configuration file will be copied to the new configuration file. 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. You let doxygen generate the documentation, based on the settings in the configuration file: doxygen In the configuration file you can specify the input files and a lot of optional information. You edit the configuration file so it matches your project. You generate a configuration file (see section Configuration) by calling doxygen with the -g option: doxygen -g You document your source code with special documentation blocks (see section Special comment blocks). To generate a manual for your project you typically need to follow these steps: Calling doxygen with the -help option at the command line will give you a brief description of the usage of the program.Īll options consist of a leading character -, followed by one character and one or more arguments depending on the option. ![]()
0 Comments
Leave a Reply. |