nexmon – Blame information for rev 1
?pathlinks?
Rev | Author | Line No. | Line |
---|---|---|---|
1 | office | 1 | # @configure_input@ |
2 | |||
3 | @INCLUDE = ../doxygen_global.cfg |
||
4 | |||
5 | # The PROJECT_NAME tag is a single word (or a sequence of words surrounded |
||
6 | # by quotes) that should identify the project. |
||
7 | |||
8 | PROJECT_NAME = "Wireshark Common UI" |
||
9 | |||
10 | # The PROJECT_NUMBER tag can be used to enter a project or revision number. |
||
11 | # This could be handy for archiving the generated documentation or |
||
12 | # if some version control system is used. |
||
13 | |||
14 | PROJECT_NUMBER = @VERSION@ |
||
15 | |||
16 | # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) |
||
17 | # base path where the generated documentation will be put. |
||
18 | # If a relative path is entered, it will be relative to the location |
||
19 | # where doxygen was started. If left blank the current directory will be used. |
||
20 | |||
21 | OUTPUT_DIRECTORY = ../wsar_html |
||
22 | |||
23 | # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. |
||
24 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be |
||
25 | # put in front of it. If left blank `html' will be used as the default path. |
||
26 | |||
27 | HTML_OUTPUT = ui |
||
28 | |||
29 | # The TAGFILES option can be used to specify one or more tagfiles. |
||
30 | # Optionally an initial location of the external documentation |
||
31 | # can be added for each tagfile. The format of a tag file without |
||
32 | # this location is as follows: |
||
33 | # |
||
34 | # TAGFILES = file1 file2 ... |
||
35 | # Adding location for the tag files is done as follows: |
||
36 | # |
||
37 | # TAGFILES = file1=loc1 "file2 = loc2" ... |
||
38 | # where "loc1" and "loc2" can be relative or absolute paths or |
||
39 | # URLs. If a location is present for each tag, the installdox tool |
||
40 | # does not have to be run to correct the links. |
||
41 | # Note that each tag file must have a unique name |
||
42 | # (where the name does NOT include the path) |
||
43 | # If a tag file is not located in the directory in which doxygen |
||
44 | # is run, you must also specify the path to the tagfile here. |
||
45 | |||
46 | TAGFILES = ../doxygen-core.tag=.. |
||
47 | |||
48 | # When a file name is specified after GENERATE_TAGFILE, doxygen will create |
||
49 | # a tag file that is based on the input files it reads. |
||
50 | |||
51 | GENERATE_TAGFILE = doxygen-ui.tag |
||
52 | |||
53 | # The RECURSIVE tag can be used to turn specify whether or not subdirectories |
||
54 | # should be searched for input files as well. Possible values are YES and NO. |
||
55 | # If left blank NO is used. |
||
56 | |||
57 | RECURSIVE = YES |
||
58 | |||
59 | # The EXCLUDE tag can be used to specify files and/or directories that should |
||
60 | # excluded from the INPUT source files. This way you can easily exclude a |
||
61 | # subdirectory from a directory tree whose root is specified with the INPUT tag. |
||
62 | |||
63 | EXCLUDE = |
||
64 | |||
65 | # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories |
||
66 | # that are symbolic links (a Unix filesystem feature) are excluded from the input. |
||
67 | |||
68 | EXCLUDE_SYMLINKS = NO |
||
69 | |||
70 | # If the value of the INPUT tag contains directories, you can use the |
||
71 | # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude |
||
72 | # certain files from those directories. |
||
73 | |||
74 | EXCLUDE_PATTERNS = |
||
75 | |||
76 | # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can |
||
77 | # be used to specify the file name of the resulting .chm file. You |
||
78 | # can add a path in front of the file if the result should not be |
||
79 | # written to the html output directory. |
||
80 | |||
81 | CHM_FILE = wireshark-ui.chm |