1 .TH genhtml 1 "LCOV 1.10" 2012\-10\-10 "User Manuals"
3 genhtml \- Generate HTML view from LCOV coverage data files
7 .RB [ \-v | \-\-version ]
10 .RB [ \-q | \-\-quiet ]
11 .RB [ \-s | \-\-show\-details ]
12 .RB [ \-f | \-\-frames ]
14 .RB [ \-b | \-\-baseline\-file ]
17 .RB [ \-o | \-\-output\-directory
18 .IR output\-directory ]
23 .RB [ \-d | \-\-description\-file
24 .IR description\-file ]
26 .RB [ \-k | \-\-keep\-descriptions ]
27 .RB [ \-c | \-\-css\-file
30 .RB [ \-p | \-\-prefix
32 .RB [ \-\-no\-prefix ]
34 .RB [ \-\-no\-source ]
40 .RB [ \-\-html\-prolog
43 .RB [ \-\-html\-epilog
45 .RB [ \-\-html\-extension
48 .RB [ \-\-html\-gzip ]
52 .RB [ \-\-function\-coverage ]
53 .RB [ \-\-no\-function\-coverage ]
55 .RB [ \-\-branch\-coverage ]
56 .RB [ \-\-no\-branch\-coverage ]
58 .RB [ \-\-demangle\-cpp ]
59 .RB [ \-\-ignore\-errors
62 .RB [ \-\-config\-file
70 Create an HTML view of coverage data found in
74 may also be a list of filenames.
76 HTML output files are created in the current working directory unless the
77 \-\-output\-directory option is used. If
79 ends with ".gz", it is assumed to be GZIP\-compressed and the gunzip tool
80 will be used to decompress it transparently.
82 Note that all source code files have to be present and readable at the
83 exact file system location they were compiled.
87 to modify layout and colors of the generated HTML output. Files are
88 marked in different colors depending on the associated coverage rate. By
89 default, the coverage limits for low, medium and high coverage are set to
90 0\-75%, 75\-90% and 90\-100% percent respectively. To change these
91 values, use configuration file options
92 .IR genhtml_hi_limit " and " genhtml_med_limit .
94 Also note that when displaying percentages, 0% and 100% are only printed when
95 the values are exactly 0% and 100% respectively. Other values which would
96 conventionally be rounded to 0% or 100% are instead printed as nearest
97 non-boundary value. This behavior is in accordance with that of the
106 Print a short help text, then exit.
113 Print version number, then exit.
120 Do not print progress messages.
122 Suppresses all informational progress output. When this switch is enabled,
123 only error or warning messages are printed.
130 Use HTML frames for source code view.
132 If enabled, a frameset is created for each source code file, providing
133 an overview of the source code as a "clickable" image. Note that this
134 option will slow down output creation noticeably because each source
135 code character has to be inspected once. Note also that the GD.pm Perl
136 module has to be installed for this option to work (it may be obtained
137 from http://www.cpan.org).
144 Generate detailed directory view.
146 When this option is enabled,
148 generates two versions of each
149 file view. One containing the standard information plus a link to a
150 "detailed" version. The latter additionally contains information about
151 which test case covered how many lines of each source file.
154 .BI "\-b " baseline\-file
156 .BI "\-\-baseline\-file " baseline\-file
160 as coverage baseline.
162 The tracefile specified by
164 is read and all counts found in the original
166 are decremented by the corresponding counts in
168 before creating any output.
170 Note that when a count for a particular line in
172 is greater than the count in the
177 .BI "\-o " output\-directory
179 .BI "\-\-output\-directory " output\-directory
182 .I output\-directory.
184 Use this option to tell
186 to write the resulting files to a directory other than
189 does not exist, it will be created.
191 It is advisable to use this option since depending on the
192 project size, a lot of files and subdirectories may be created.
197 .BI "\-\-title " title
201 in header of all pages.
204 is written to the header portion of each generated HTML page to
205 identify the context in which a particular output
206 was created. By default this is the name of the tracefile.
209 .BI "\-d " description\-file
211 .BI "\-\-description\-file " description\-file
213 Read test case descriptions from
214 .IR description\-file .
216 All test case descriptions found in
218 and referenced in the input data file are read and written to an extra page
219 which is then incorporated into the HTML output.
222 .IR "description\-file " is:
228 TD:<test description>
232 Valid test case names can consist of letters, numbers and the underscore
237 .B \-\-keep\-descriptions
239 Do not remove unused test descriptions.
241 Keep descriptions found in the description file even if the coverage data
242 indicates that the associated test case did not cover any lines of code.
244 This option can also be configured permanently using the configuration file
246 .IR genhtml_keep_descriptions .
251 .BI "\-\-css\-file " css\-file
253 Use external style sheet file
256 Using this option, an extra .css file may be specified which will replace
257 the default one. This may be helpful if the default colors make your eyes want
258 to jump out of their sockets :)
260 This option can also be configured permanently using the configuration file
262 .IR genhtml_css_file .
267 .BI "\-\-prefix " prefix
271 from all directory names.
273 Because lists containing long filenames are difficult to read, there is a
274 mechanism implemented that will automatically try to shorten all directory
275 names on the overview page beginning with a common prefix. By default,
276 this is done using an algorithm that tries to find the prefix which, when
277 applied, will minimize the resulting sum of characters of all directory
280 Use this option to specify the prefix to be removed by yourself.
285 Do not remove prefix from directory names.
287 This switch will completely disable the prefix mechanism described in the
290 This option can also be configured permanently using the configuration file
292 .IR genhtml_no_prefix .
297 Do not create source code view.
299 Use this switch if you don't want to get a source code view for each file.
301 This option can also be configured permanently using the configuration file
303 .IR genhtml_no_source .
306 .BI "\-\-num\-spaces " spaces
308 Replace tabs in source view with
314 This option can also be configured permanently using the configuration file
316 .IR genhtml_num_spaces .
321 Highlight lines with converted\-only coverage data.
323 Use this option in conjunction with the \-\-diff option of
325 to highlight those lines which were only covered in data sets which were
326 converted from previous source code versions.
328 This option can also be configured permanently using the configuration file
330 .IR genhtml_highlight .
335 Include color legend in HTML output.
337 Use this option to include a legend explaining the meaning of color coding
338 in the resulting HTML output.
340 This option can also be configured permanently using the configuration file
345 .BI "\-\-html\-prolog " prolog\-file
347 Read customized HTML prolog from
350 Use this option to replace the default HTML prolog (the initial part of the
351 HTML source code leading up to and including the <body> tag) with the contents
354 Within the prolog text, the following words will be replaced when a page is generated:
358 The title of the page.
362 A relative path leading to the base directory (e.g. for locating css\-files).
364 This option can also be configured permanently using the configuration file
366 .IR genhtml_html_prolog .
369 .BI "\-\-html\-epilog " epilog\-file
371 Read customized HTML epilog from
374 Use this option to replace the default HTML epilog (the final part of the HTML
375 source including </body>) with the contents of
378 Within the epilog text, the following words will be replaced when a page is generated:
382 A relative path leading to the base directory (e.g. for locating css\-files).
384 This option can also be configured permanently using the configuration file
386 .IR genhtml_html_epilog .
389 .BI "\-\-html\-extension " extension
391 Use customized filename extension for generated HTML pages.
393 This option is useful in situations where different filename extensions
394 are required to render the resulting pages correctly (e.g. php). Note that
395 a '.' will be inserted between the filename and the extension specified by
398 This option can also be configured permanently using the configuration file
400 .IR genhtml_html_extension .
405 Compress all generated html files with gzip and add a .htaccess file specifying
406 gzip\-encoding in the root output directory.
408 Use this option if you want to save space on your webserver. Requires a
409 webserver with .htaccess support and a browser with support for gzip
412 This option can also be configured permanently using the configuration file
414 .IR genhtml_html_gzip .
421 Specify whether to include sorted views of file and directory overviews.
423 Use \-\-sort to include sorted views or \-\-no\-sort to not include them.
428 When sorted views are enabled, each overview page will contain links to
429 views of that page sorted by coverage rate.
431 This option can also be configured permanently using the configuration file
436 .B \-\-function\-coverage
438 .B \-\-no\-function\-coverage
440 Specify whether to display function coverage summaries in HTML output.
442 Use \-\-function\-coverage to enable function coverage summaries or
443 \-\-no\-function\-coverage to disable it. Function coverage summaries are
447 When function coverage summaries are enabled, each overview page will contain
448 the number of functions found and hit per file or directory, together with
449 the resulting coverage rate. In addition, each source code view will contain
450 a link to a page which lists all functions found in that file plus the
451 respective call count for those functions.
453 This option can also be configured permanently using the configuration file
455 .IR genhtml_function_coverage .
458 .B \-\-branch\-coverage
460 .B \-\-no\-branch\-coverage
462 Specify whether to display branch coverage data in HTML output.
464 Use \-\-branch\-coverage to enable branch coverage display or
465 \-\-no\-branch\-coverage to disable it. Branch coverage data display is
469 When branch coverage display is enabled, each overview page will contain
470 the number of branches found and hit per file or directory, together with
471 the resulting coverage rate. In addition, each source code view will contain
472 an extra column which lists all branches of a line with indications of
473 whether the branch was taken or not. Branches are shown in the following format:
475 ' + ': Branch was taken at least once
477 ' - ': Branch was not taken
479 ' # ': The basic block containing the branch was never executed
482 Note that it might not always be possible to relate branches to the
483 corresponding source code statements: during compilation, GCC might shuffle
484 branches around or eliminate some of them to generate better code.
486 This option can also be configured permanently using the configuration file
488 .IR genhtml_branch_coverage .
493 Specify whether to demangle C++ function names.
495 Use this option if you want to convert C++ internal function names to
496 human readable format for display on the HTML function overview page.
497 This option requires that the c++filt tool is installed (see
501 .B \-\-ignore\-errors
505 Specify a list of errors after which to continue processing.
507 Use this option to specify a list of one or more classes of errors after which
508 geninfo should continue processing instead of aborting.
511 can be a comma\-separated list of the following keywords:
514 the source code file for a data set could not be found.
521 Specify a configuration file to use.
523 When this option is specified, neither the system\-wide configuration file
524 /etc/lcovrc, nor the per\-user configuration file ~/.lcovrc is read.
526 This option may be useful when there is a need to run several
529 with different configuration file options in parallel.
536 Override a configuration directive.
538 Use this option to specify a
540 statement which overrides the corresponding configuration statement in
541 the lcovrc configuration file. You can specify this option more than once
542 to override multiple configuration statements.
545 for a list of available keywords and their meaning.
552 The system\-wide configuration file.
557 The per\-user configuration file.
561 Peter Oberparleiter <Peter.Oberparleiter@de.ibm.com>