.
will be generated. You may view the manual page with: nroff -man .
| less'. A typical entry in a Makefile or Makefile.am is: DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl XP = xsltproc -''-nonet -''-param man.charmap.use.subset "0" manpage.1: manpage.xml $(XP) $(DB2MAN) $< The xsltproc binary is found in the xsltproc package. The XSL files are in docbook-xsl. A description of the parameters you can use can be found in the docbook-xsl-doc-* packages. Please remember that if you create the nroff version in one of the debian/rules file targets (such as build), you will need to include xsltproc and docbook-xsl in your Build-Depends control field. Alternatively use the xmlto command/package. That will also automatically pull in xsltproc and docbook-xsl. Notes for using docbook2x: docbook2x-man does not automatically create the AUTHOR(S) and COPYRIGHT sections. In this case, please add them manually as ... . To disable the automatic creation of the AUTHOR(S) and COPYRIGHT sections read /usr/share/doc/docbook-xsl/doc/manpages/authors.html. This file can be found in the docbook-xsl-doc-html package. Validation can be done using: `xmllint -''-noout -''-valid manpage.xml` General documentation about man-pages and man-page-formatting: man(1), man(7), http://www.tldp.org/HOWTO/Man-Page/ --> ]> &dhtitle; &dhpackage; &dhfirstname; &dhsurname; Wrote this manpage for the Debian system.
&dhemail;
2009 &dhusername; This manual page was written for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or (at your option) any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-2.
&dhucpackage; &dhsection; &dhpackage; Simple syntax checking of C/C++. &dhpackage; DESCRIPTION A tool for static C/C++ code analysis intended to complement the checking of the compiler. Checks for: memory leaks, mismatching allocation-deallocation, buffer overrun, and many more. OPTIONS Analyze given C/C++ files for common errors. Normally a message is only shown if cppcheck is sure it has found a bug. When this option is given, all messages are shown. This allows you to provide information about functions by providing an implementation for these. Suppress warnings about classes that have automatic deallocation The classnames must be provided in plain text - one classname / line - in a .lst file. This option can be given several times, allowing you to provide several .lst files. If errors are found, integer [n] is returned instead of default 0. EXIT_FAILURE is returned if arguments are not valid or if no input files are provided. Note that your operating system can modify this value, e.g. 256 can become 0. Force checking of files that have a lot of configurations. Error is printed if such a file is found so there is no reason to use this by default. Print help text. Give include path. Give several -I parameters to give several paths. First given path is checked first. If paths are relative to source files, this is not needed. Start [jobs] threads to do the checking work. Only print something when there is an error. Check coding style. Format the error messages. E.g. '{file}:{line},{severity},{id},{message}' or '{file}({line}):({severity}) {message}'. Pre-defined templates: gcc, vs Check if there are unused functions More detailed error reports Print out version information Write results in xml to error stream AUTHOR The program was written by Bill Egert, Daniel Marjamäki, Gianluca Scacco, Hoang Tuan Su, Kimmo Varis, Leandro Penz, Nicolas Le Cam, Reijo Tomperi, Slava Semushin and Vesa Pikki SEE ALSO Full list of features: http://cppcheck.wiki.sourceforge.net/