Merge lp:~pete-woods/libusermetrics/cmake-extras-compatibility into lp:libusermetrics
- cmake-extras-compatibility
- Merge into trunk
Proposed by
Pete Woods
Status: | Merged |
---|---|
Approved by: | Pete Woods |
Approved revision: | 240 |
Merged at revision: | 234 |
Proposed branch: | lp:~pete-woods/libusermetrics/cmake-extras-compatibility |
Merge into: | lp:libusermetrics |
Diff against target: |
2529 lines (+97/-2221) 19 files modified
.bzrignore (+2/-0) CMakeLists.txt (+30/-10) cmake/COPYING-CMAKE-SCRIPTS (+0/-22) cmake/Coverage.cmake (+0/-37) cmake/Doxyfile.in (+0/-1891) cmake/FindGMock.cmake (+0/-10) cmake/FindValgrind.cmake (+0/-34) cmake/UseDoxygen.cmake (+0/-154) cmake/UseGSettings.cmake (+0/-29) data/CMakeLists.txt (+1/-1) debian/control (+4/-3) debian/rules (+1/-1) doc/CMakeLists.txt (+26/-0) po/CMakeLists.txt (+9/-6) tests/CMakeLists.txt (+1/-3) tests/unit/libusermetricsinput/CMakeLists.txt (+1/-1) tests/unit/libusermetricsoutput/CMakeLists.txt (+1/-1) tests/unit/libusermetricsoutput/TestSyncedUserMetricsStore.cpp (+20/-17) tests/unit/usermetricsservice/CMakeLists.txt (+1/-1) |
To merge this branch: | bzr merge lp:~pete-woods/libusermetrics/cmake-extras-compatibility |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
James Henstridge | Needs Information | ||
Review via email: mp+312702@code.launchpad.net |
Commit message
Compatibility with unversioned cmake-extras modules
Description of the change
Compatibility with unversioned cmake-extras modules
To post a comment you must log in.
Revision history for this message
Michi Henning (michihenning) wrote : | # |
I did run test builds of thumbnailer, persistent-
Revision history for this message
Pete Woods (pete-woods) wrote : | # |
I've fixed the coverage report in this MR, and also the other MRs.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1 | === added file '.bzrignore' |
2 | --- .bzrignore 1970-01-01 00:00:00 +0000 |
3 | +++ .bzrignore 2016-12-08 10:49:24 +0000 |
4 | @@ -0,0 +1,2 @@ |
5 | +/po/Makefile.in.in |
6 | +/po/POTFILES.in |
7 | |
8 | === modified file 'CMakeLists.txt' |
9 | --- CMakeLists.txt 2016-08-08 13:51:10 +0000 |
10 | +++ CMakeLists.txt 2016-12-08 10:49:24 +0000 |
11 | @@ -72,7 +72,6 @@ |
12 | |
13 | |
14 | include(GNUInstallDirs) |
15 | -include(Coverage) |
16 | |
17 | # Workaround for libexecdir on debian |
18 | if (EXISTS "/etc/debian_version") |
19 | @@ -89,16 +88,8 @@ |
20 | -DLOCALEDIR="${CMAKE_INSTALL_FULL_DATADIR}/locale" |
21 | ) |
22 | |
23 | -set(DOXYFILE_SOURCE_DIR "include") |
24 | -set(DOXYFILE_EXTRA_SOURCES "doc") |
25 | -include(UseDoxygen) |
26 | -if(DOXYGEN_FOUND AND BUILD_DOXYGEN) |
27 | - install( |
28 | - DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/doc/html |
29 | - DESTINATION ${CMAKE_INSTALL_PREFIX}/share/doc/libusermetrics-doc/ |
30 | - ) |
31 | -endif() |
32 | |
33 | +add_subdirectory("doc") |
34 | add_subdirectory("po") |
35 | add_subdirectory("src") |
36 | add_subdirectory("data") |
37 | @@ -112,4 +103,33 @@ |
38 | check |
39 | ${CMAKE_CTEST_COMMAND} --force-new-ctest-process --output-on-failure |
40 | ) |
41 | + |
42 | +find_package(CoverageReport) |
43 | +enable_coverage_report( |
44 | + TARGETS |
45 | + usermetrics-test-utils |
46 | + usermetricscommon |
47 | + usermetricsinput |
48 | + usermetricsinput-static |
49 | + usermetricsinput-integration-tests |
50 | + usermetricsinput-unit-tests |
51 | + usermetricsoutput |
52 | + usermetricsoutput-integration-tests |
53 | + usermetricsoutput-static |
54 | + usermetricsoutput-unit-tests |
55 | + usermetricsservice |
56 | + usermetricsservice-bin |
57 | + usermetricsservice-unit-tests |
58 | + FILTER |
59 | + ${CMAKE_SOURCE_DIR}/tests/* |
60 | + ${CMAKE_BINARY_DIR}/* |
61 | + TESTS |
62 | + usermetrics-test-utils |
63 | + usermetricsinput-integration-tests |
64 | + usermetricsinput-unit-tests |
65 | + usermetricsoutput-integration-tests |
66 | + usermetricsoutput-unit-tests |
67 | + usermetricsservice-unit-tests |
68 | +) |
69 | + |
70 | endif() |
71 | |
72 | === removed directory 'cmake' |
73 | === removed file 'cmake/COPYING-CMAKE-SCRIPTS' |
74 | --- cmake/COPYING-CMAKE-SCRIPTS 2013-06-10 22:52:24 +0000 |
75 | +++ cmake/COPYING-CMAKE-SCRIPTS 1970-01-01 00:00:00 +0000 |
76 | @@ -1,22 +0,0 @@ |
77 | -Redistribution and use in source and binary forms, with or without |
78 | -modification, are permitted provided that the following conditions |
79 | -are met: |
80 | - |
81 | -1. Redistributions of source code must retain the copyright |
82 | - notice, this list of conditions and the following disclaimer. |
83 | -2. Redistributions in binary form must reproduce the copyright |
84 | - notice, this list of conditions and the following disclaimer in the |
85 | - documentation and/or other materials provided with the distribution. |
86 | -3. The name of the author may not be used to endorse or promote products |
87 | - derived from this software without specific prior written permission. |
88 | - |
89 | -THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR |
90 | -IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES |
91 | -OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. |
92 | -IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, |
93 | -INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT |
94 | -NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, |
95 | -DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY |
96 | -THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
97 | -(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF |
98 | -THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
99 | |
100 | === removed file 'cmake/Coverage.cmake' |
101 | --- cmake/Coverage.cmake 2013-06-10 09:57:58 +0000 |
102 | +++ cmake/Coverage.cmake 1970-01-01 00:00:00 +0000 |
103 | @@ -1,37 +0,0 @@ |
104 | -if (CMAKE_BUILD_TYPE MATCHES coverage) |
105 | - set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} --coverage") |
106 | - set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} --coverage") |
107 | - set(CMAKE_MODULE_LINKER_FLAGS "${CMAKE_MODULE_LINKER_FLAGS} --coverage") |
108 | - set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS} --coverage") |
109 | - |
110 | - find_program(GCOVR_EXECUTABLE gcovr HINTS ${GCOVR_ROOT} "${GCOVR_ROOT}/bin") |
111 | - if (NOT GCOVR_EXECUTABLE) |
112 | - message(STATUS "Gcovr binary was not found, can not generate XML coverage info.") |
113 | - else () |
114 | - message(STATUS "Gcovr found, can generate XML coverage info.") |
115 | - add_custom_target (coverage-xml |
116 | - WORKING_DIRECTORY ${CMAKE_BINARY_DIR} |
117 | - COMMAND "${GCOVR_EXECUTABLE}" --exclude="test.*" --exclude="obj.*" -x -r "${CMAKE_SOURCE_DIR}" |
118 | - --object-directory=${CMAKE_BINARY_DIR} -o coverage.xml) |
119 | - endif() |
120 | - |
121 | - find_program(LCOV_EXECUTABLE lcov HINTS ${LCOV_ROOT} "${GCOVR_ROOT}/bin") |
122 | - find_program(GENHTML_EXECUTABLE genhtml HINTS ${GENHTML_ROOT}) |
123 | - if (NOT LCOV_EXECUTABLE) |
124 | - message(STATUS "Lcov binary was not found, can not generate HTML coverage info.") |
125 | - else () |
126 | - if(NOT GENHTML_EXECUTABLE) |
127 | - message(STATUS "Genthml binary not found, can not generate HTML coverage info.") |
128 | - else() |
129 | - message(STATUS "Lcov and genhtml found, can generate HTML coverage info.") |
130 | - add_custom_target (coverage-html |
131 | - WORKING_DIRECTORY ${CMAKE_BINARY_DIR} |
132 | - COMMAND "${LCOV_EXECUTABLE}" --capture --output-file "${CMAKE_BINARY_DIR}/coverage.info" --no-checksum --directory "${CMAKE_BINARY_DIR}" |
133 | - COMMAND "${LCOV_EXECUTABLE}" --remove "${CMAKE_BINARY_DIR}/coverage.info" '/usr/*' --output-file "${CMAKE_BINARY_DIR}/coverage.info" |
134 | - COMMAND "${LCOV_EXECUTABLE}" --remove "${CMAKE_BINARY_DIR}/coverage.info" '${CMAKE_BINARY_DIR}/*' --output-file "${CMAKE_BINARY_DIR}/coverage.info" |
135 | - COMMAND "${LCOV_EXECUTABLE}" --remove "${CMAKE_BINARY_DIR}/coverage.info" '${CMAKE_SOURCE_DIR}/tests/*' --output-file "${CMAKE_BINARY_DIR}/coverage.info" |
136 | - COMMAND "${GENHTML_EXECUTABLE}" --prefix "${CMAKE_BINARY_DIR}" --output-directory coveragereport --title "Code Coverage" --legend --show-details coverage.info |
137 | - ) |
138 | - endif() |
139 | - endif() |
140 | -endif() |
141 | |
142 | === removed file 'cmake/Doxyfile.in' |
143 | --- cmake/Doxyfile.in 2013-07-09 16:51:58 +0000 |
144 | +++ cmake/Doxyfile.in 1970-01-01 00:00:00 +0000 |
145 | @@ -1,1891 +0,0 @@ |
146 | -# Doxyfile 1.8.4 |
147 | - |
148 | -# This file describes the settings to be used by the documentation system |
149 | -# doxygen (www.doxygen.org) for a project. |
150 | -# |
151 | -# All text after a double hash (##) is considered a comment and is placed |
152 | -# in front of the TAG it is preceding . |
153 | -# All text after a hash (#) is considered a comment and will be ignored. |
154 | -# The format is: |
155 | -# TAG = value [value, ...] |
156 | -# For lists items can also be appended using: |
157 | -# TAG += value [value, ...] |
158 | -# Values that contain spaces should be placed between quotes (" "). |
159 | - |
160 | -#--------------------------------------------------------------------------- |
161 | -# Project related configuration options |
162 | -#--------------------------------------------------------------------------- |
163 | - |
164 | -# This tag specifies the encoding used for all characters in the config file |
165 | -# that follow. The default is UTF-8 which is also the encoding used for all |
166 | -# text before the first occurrence of this tag. Doxygen uses libiconv (or the |
167 | -# iconv built into libc) for the transcoding. See |
168 | -# http://www.gnu.org/software/libiconv for the list of possible encodings. |
169 | - |
170 | -DOXYFILE_ENCODING = UTF-8 |
171 | - |
172 | -# The PROJECT_NAME tag is a single word (or sequence of words) that should |
173 | -# identify the project. Note that if you do not use Doxywizard you need |
174 | -# to put quotes around the project name if it contains spaces. |
175 | - |
176 | -PROJECT_NAME = "@PROJECT_NAME@" |
177 | - |
178 | -# The PROJECT_NUMBER tag can be used to enter a project or revision number. |
179 | -# This could be handy for archiving the generated documentation or |
180 | -# if some version control system is used. |
181 | - |
182 | -PROJECT_NUMBER = "@PROJECT_VERSION@" |
183 | - |
184 | -# Using the PROJECT_BRIEF tag one can provide an optional one line description |
185 | -# for a project that appears at the top of each page and should give viewer |
186 | -# a quick idea about the purpose of the project. Keep the description short. |
187 | - |
188 | -PROJECT_BRIEF = |
189 | - |
190 | -# With the PROJECT_LOGO tag one can specify an logo or icon that is |
191 | -# included in the documentation. The maximum height of the logo should not |
192 | -# exceed 55 pixels and the maximum width should not exceed 200 pixels. |
193 | -# Doxygen will copy the logo to the output directory. |
194 | - |
195 | -PROJECT_LOGO = |
196 | - |
197 | -# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) |
198 | -# base path where the generated documentation will be put. |
199 | -# If a relative path is entered, it will be relative to the location |
200 | -# where doxygen was started. If left blank the current directory will be used. |
201 | - |
202 | -OUTPUT_DIRECTORY = "@DOXYFILE_OUTPUT_DIR@" |
203 | - |
204 | -# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create |
205 | -# 4096 sub-directories (in 2 levels) under the output directory of each output |
206 | -# format and will distribute the generated files over these directories. |
207 | -# Enabling this option can be useful when feeding doxygen a huge amount of |
208 | -# source files, where putting all generated files in the same directory would |
209 | -# otherwise cause performance problems for the file system. |
210 | - |
211 | -CREATE_SUBDIRS = NO |
212 | - |
213 | -# The OUTPUT_LANGUAGE tag is used to specify the language in which all |
214 | -# documentation generated by doxygen is written. Doxygen will use this |
215 | -# information to generate all constant output in the proper language. |
216 | -# The default language is English, other supported languages are: |
217 | -# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, |
218 | -# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, |
219 | -# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English |
220 | -# messages), Korean, Korean-en, Latvian, Lithuanian, Norwegian, Macedonian, |
221 | -# Persian, Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, |
222 | -# Slovak, Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. |
223 | - |
224 | -OUTPUT_LANGUAGE = English |
225 | - |
226 | -# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will |
227 | -# include brief member descriptions after the members that are listed in |
228 | -# the file and class documentation (similar to JavaDoc). |
229 | -# Set to NO to disable this. |
230 | - |
231 | -BRIEF_MEMBER_DESC = YES |
232 | - |
233 | -# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend |
234 | -# the brief description of a member or function before the detailed description. |
235 | -# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the |
236 | -# brief descriptions will be completely suppressed. |
237 | - |
238 | -REPEAT_BRIEF = YES |
239 | - |
240 | -# This tag implements a quasi-intelligent brief description abbreviator |
241 | -# that is used to form the text in various listings. Each string |
242 | -# in this list, if found as the leading text of the brief description, will be |
243 | -# stripped from the text and the result after processing the whole list, is |
244 | -# used as the annotated text. Otherwise, the brief description is used as-is. |
245 | -# If left blank, the following values are used ("$name" is automatically |
246 | -# replaced with the name of the entity): "The $name class" "The $name widget" |
247 | -# "The $name file" "is" "provides" "specifies" "contains" |
248 | -# "represents" "a" "an" "the" |
249 | - |
250 | -ABBREVIATE_BRIEF = |
251 | - |
252 | -# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then |
253 | -# Doxygen will generate a detailed section even if there is only a brief |
254 | -# description. |
255 | - |
256 | -ALWAYS_DETAILED_SEC = NO |
257 | - |
258 | -# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all |
259 | -# inherited members of a class in the documentation of that class as if those |
260 | -# members were ordinary class members. Constructors, destructors and assignment |
261 | -# operators of the base classes will not be shown. |
262 | - |
263 | -INLINE_INHERITED_MEMB = NO |
264 | - |
265 | -# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full |
266 | -# path before files name in the file list and in the header files. If set |
267 | -# to NO the shortest path that makes the file name unique will be used. |
268 | - |
269 | -FULL_PATH_NAMES = YES |
270 | - |
271 | -# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag |
272 | -# can be used to strip a user-defined part of the path. Stripping is |
273 | -# only done if one of the specified strings matches the left-hand part of |
274 | -# the path. The tag can be used to show relative paths in the file list. |
275 | -# If left blank the directory from which doxygen is run is used as the |
276 | -# path to strip. Note that you specify absolute paths here, but also |
277 | -# relative paths, which will be relative from the directory where doxygen is |
278 | -# started. |
279 | - |
280 | -STRIP_FROM_PATH = |
281 | - |
282 | -# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of |
283 | -# the path mentioned in the documentation of a class, which tells |
284 | -# the reader which header file to include in order to use a class. |
285 | -# If left blank only the name of the header file containing the class |
286 | -# definition is used. Otherwise one should specify the include paths that |
287 | -# are normally passed to the compiler using the -I flag. |
288 | - |
289 | -STRIP_FROM_INC_PATH = "@DOXYFILE_SOURCE_DIR@" |
290 | - |
291 | -# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter |
292 | -# (but less readable) file names. This can be useful if your file system |
293 | -# doesn't support long names like on DOS, Mac, or CD-ROM. |
294 | - |
295 | -SHORT_NAMES = NO |
296 | - |
297 | -# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen |
298 | -# will interpret the first line (until the first dot) of a JavaDoc-style |
299 | -# comment as the brief description. If set to NO, the JavaDoc |
300 | -# comments will behave just like regular Qt-style comments |
301 | -# (thus requiring an explicit @brief command for a brief description.) |
302 | - |
303 | -JAVADOC_AUTOBRIEF = NO |
304 | - |
305 | -# If the QT_AUTOBRIEF tag is set to YES then Doxygen will |
306 | -# interpret the first line (until the first dot) of a Qt-style |
307 | -# comment as the brief description. If set to NO, the comments |
308 | -# will behave just like regular Qt-style comments (thus requiring |
309 | -# an explicit \brief command for a brief description.) |
310 | - |
311 | -QT_AUTOBRIEF = NO |
312 | - |
313 | -# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen |
314 | -# treat a multi-line C++ special comment block (i.e. a block of //! or /// |
315 | -# comments) as a brief description. This used to be the default behaviour. |
316 | -# The new default is to treat a multi-line C++ comment block as a detailed |
317 | -# description. Set this tag to YES if you prefer the old behaviour instead. |
318 | - |
319 | -MULTILINE_CPP_IS_BRIEF = NO |
320 | - |
321 | -# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented |
322 | -# member inherits the documentation from any documented member that it |
323 | -# re-implements. |
324 | - |
325 | -INHERIT_DOCS = YES |
326 | - |
327 | -# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce |
328 | -# a new page for each member. If set to NO, the documentation of a member will |
329 | -# be part of the file/class/namespace that contains it. |
330 | - |
331 | -SEPARATE_MEMBER_PAGES = NO |
332 | - |
333 | -# The TAB_SIZE tag can be used to set the number of spaces in a tab. |
334 | -# Doxygen uses this value to replace tabs by spaces in code fragments. |
335 | - |
336 | -TAB_SIZE = 4 |
337 | - |
338 | -# This tag can be used to specify a number of aliases that acts |
339 | -# as commands in the documentation. An alias has the form "name=value". |
340 | -# For example adding "sideeffect=\par Side Effects:\n" will allow you to |
341 | -# put the command \sideeffect (or @sideeffect) in the documentation, which |
342 | -# will result in a user-defined paragraph with heading "Side Effects:". |
343 | -# You can put \n's in the value part of an alias to insert newlines. |
344 | - |
345 | -ALIASES = |
346 | - |
347 | -# This tag can be used to specify a number of word-keyword mappings (TCL only). |
348 | -# A mapping has the form "name=value". For example adding |
349 | -# "class=itcl::class" will allow you to use the command class in the |
350 | -# itcl::class meaning. |
351 | - |
352 | -TCL_SUBST = |
353 | - |
354 | -# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C |
355 | -# sources only. Doxygen will then generate output that is more tailored for C. |
356 | -# For instance, some of the names that are used will be different. The list |
357 | -# of all members will be omitted, etc. |
358 | - |
359 | -OPTIMIZE_OUTPUT_FOR_C = NO |
360 | - |
361 | -# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java |
362 | -# sources only. Doxygen will then generate output that is more tailored for |
363 | -# Java. For instance, namespaces will be presented as packages, qualified |
364 | -# scopes will look different, etc. |
365 | - |
366 | -OPTIMIZE_OUTPUT_JAVA = NO |
367 | - |
368 | -# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran |
369 | -# sources only. Doxygen will then generate output that is more tailored for |
370 | -# Fortran. |
371 | - |
372 | -OPTIMIZE_FOR_FORTRAN = NO |
373 | - |
374 | -# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL |
375 | -# sources. Doxygen will then generate output that is tailored for |
376 | -# VHDL. |
377 | - |
378 | -OPTIMIZE_OUTPUT_VHDL = NO |
379 | - |
380 | -# Doxygen selects the parser to use depending on the extension of the files it |
381 | -# parses. With this tag you can assign which parser to use for a given |
382 | -# extension. Doxygen has a built-in mapping, but you can override or extend it |
383 | -# using this tag. The format is ext=language, where ext is a file extension, |
384 | -# and language is one of the parsers supported by doxygen: IDL, Java, |
385 | -# Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, |
386 | -# C++. For instance to make doxygen treat .inc files as Fortran files (default |
387 | -# is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note |
388 | -# that for custom extensions you also need to set FILE_PATTERNS otherwise the |
389 | -# files are not read by doxygen. |
390 | - |
391 | -EXTENSION_MAPPING = |
392 | - |
393 | -# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all |
394 | -# comments according to the Markdown format, which allows for more readable |
395 | -# documentation. See http://daringfireball.net/projects/markdown/ for details. |
396 | -# The output of markdown processing is further processed by doxygen, so you |
397 | -# can mix doxygen, HTML, and XML commands with Markdown formatting. |
398 | -# Disable only in case of backward compatibilities issues. |
399 | - |
400 | -MARKDOWN_SUPPORT = YES |
401 | - |
402 | -# When enabled doxygen tries to link words that correspond to documented |
403 | -# classes, or namespaces to their corresponding documentation. Such a link can |
404 | -# be prevented in individual cases by by putting a % sign in front of the word |
405 | -# or globally by setting AUTOLINK_SUPPORT to NO. |
406 | - |
407 | -AUTOLINK_SUPPORT = YES |
408 | - |
409 | -# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want |
410 | -# to include (a tag file for) the STL sources as input, then you should |
411 | -# set this tag to YES in order to let doxygen match functions declarations and |
412 | -# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. |
413 | -# func(std::string) {}). This also makes the inheritance and collaboration |
414 | -# diagrams that involve STL classes more complete and accurate. |
415 | - |
416 | -BUILTIN_STL_SUPPORT = YES |
417 | - |
418 | -# If you use Microsoft's C++/CLI language, you should set this option to YES to |
419 | -# enable parsing support. |
420 | - |
421 | -CPP_CLI_SUPPORT = NO |
422 | - |
423 | -# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. |
424 | -# Doxygen will parse them like normal C++ but will assume all classes use public |
425 | -# instead of private inheritance when no explicit protection keyword is present. |
426 | - |
427 | -SIP_SUPPORT = NO |
428 | - |
429 | -# For Microsoft's IDL there are propget and propput attributes to indicate |
430 | -# getter and setter methods for a property. Setting this option to YES (the |
431 | -# default) will make doxygen replace the get and set methods by a property in |
432 | -# the documentation. This will only work if the methods are indeed getting or |
433 | -# setting a simple type. If this is not the case, or you want to show the |
434 | -# methods anyway, you should set this option to NO. |
435 | - |
436 | -IDL_PROPERTY_SUPPORT = YES |
437 | - |
438 | -# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC |
439 | -# tag is set to YES, then doxygen will reuse the documentation of the first |
440 | -# member in the group (if any) for the other members of the group. By default |
441 | -# all members of a group must be documented explicitly. |
442 | - |
443 | -DISTRIBUTE_GROUP_DOC = NO |
444 | - |
445 | -# Set the SUBGROUPING tag to YES (the default) to allow class member groups of |
446 | -# the same type (for instance a group of public functions) to be put as a |
447 | -# subgroup of that type (e.g. under the Public Functions section). Set it to |
448 | -# NO to prevent subgrouping. Alternatively, this can be done per class using |
449 | -# the \nosubgrouping command. |
450 | - |
451 | -SUBGROUPING = YES |
452 | - |
453 | -# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and |
454 | -# unions are shown inside the group in which they are included (e.g. using |
455 | -# @ingroup) instead of on a separate page (for HTML and Man pages) or |
456 | -# section (for LaTeX and RTF). |
457 | - |
458 | -INLINE_GROUPED_CLASSES = NO |
459 | - |
460 | -# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and |
461 | -# unions with only public data fields or simple typedef fields will be shown |
462 | -# inline in the documentation of the scope in which they are defined (i.e. file, |
463 | -# namespace, or group documentation), provided this scope is documented. If set |
464 | -# to NO (the default), structs, classes, and unions are shown on a separate |
465 | -# page (for HTML and Man pages) or section (for LaTeX and RTF). |
466 | - |
467 | -INLINE_SIMPLE_STRUCTS = NO |
468 | - |
469 | -# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum |
470 | -# is documented as struct, union, or enum with the name of the typedef. So |
471 | -# typedef struct TypeS {} TypeT, will appear in the documentation as a struct |
472 | -# with name TypeT. When disabled the typedef will appear as a member of a file, |
473 | -# namespace, or class. And the struct will be named TypeS. This can typically |
474 | -# be useful for C code in case the coding convention dictates that all compound |
475 | -# types are typedef'ed and only the typedef is referenced, never the tag name. |
476 | - |
477 | -TYPEDEF_HIDES_STRUCT = NO |
478 | - |
479 | -# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This |
480 | -# cache is used to resolve symbols given their name and scope. Since this can |
481 | -# be an expensive process and often the same symbol appear multiple times in |
482 | -# the code, doxygen keeps a cache of pre-resolved symbols. If the cache is too |
483 | -# small doxygen will become slower. If the cache is too large, memory is wasted. |
484 | -# The cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid |
485 | -# range is 0..9, the default is 0, corresponding to a cache size of 2^16 = 65536 |
486 | -# symbols. |
487 | - |
488 | -LOOKUP_CACHE_SIZE = 0 |
489 | - |
490 | -#--------------------------------------------------------------------------- |
491 | -# Build related configuration options |
492 | -#--------------------------------------------------------------------------- |
493 | - |
494 | -# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in |
495 | -# documentation are documented, even if no documentation was available. |
496 | -# Private class members and static file members will be hidden unless |
497 | -# the EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES |
498 | - |
499 | -EXTRACT_ALL = YES |
500 | - |
501 | -# If the EXTRACT_PRIVATE tag is set to YES all private members of a class |
502 | -# will be included in the documentation. |
503 | - |
504 | -EXTRACT_PRIVATE = NO |
505 | - |
506 | -# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal |
507 | -# scope will be included in the documentation. |
508 | - |
509 | -EXTRACT_PACKAGE = NO |
510 | - |
511 | -# If the EXTRACT_STATIC tag is set to YES all static members of a file |
512 | -# will be included in the documentation. |
513 | - |
514 | -EXTRACT_STATIC = NO |
515 | - |
516 | -# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) |
517 | -# defined locally in source files will be included in the documentation. |
518 | -# If set to NO only classes defined in header files are included. |
519 | - |
520 | -EXTRACT_LOCAL_CLASSES = YES |
521 | - |
522 | -# This flag is only useful for Objective-C code. When set to YES local |
523 | -# methods, which are defined in the implementation section but not in |
524 | -# the interface are included in the documentation. |
525 | -# If set to NO (the default) only methods in the interface are included. |
526 | - |
527 | -EXTRACT_LOCAL_METHODS = NO |
528 | - |
529 | -# If this flag is set to YES, the members of anonymous namespaces will be |
530 | -# extracted and appear in the documentation as a namespace called |
531 | -# 'anonymous_namespace{file}', where file will be replaced with the base |
532 | -# name of the file that contains the anonymous namespace. By default |
533 | -# anonymous namespaces are hidden. |
534 | - |
535 | -EXTRACT_ANON_NSPACES = NO |
536 | - |
537 | -# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all |
538 | -# undocumented members of documented classes, files or namespaces. |
539 | -# If set to NO (the default) these members will be included in the |
540 | -# various overviews, but no documentation section is generated. |
541 | -# This option has no effect if EXTRACT_ALL is enabled. |
542 | - |
543 | -HIDE_UNDOC_MEMBERS = NO |
544 | - |
545 | -# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all |
546 | -# undocumented classes that are normally visible in the class hierarchy. |
547 | -# If set to NO (the default) these classes will be included in the various |
548 | -# overviews. This option has no effect if EXTRACT_ALL is enabled. |
549 | - |
550 | -HIDE_UNDOC_CLASSES = NO |
551 | - |
552 | -# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all |
553 | -# friend (class|struct|union) declarations. |
554 | -# If set to NO (the default) these declarations will be included in the |
555 | -# documentation. |
556 | - |
557 | -HIDE_FRIEND_COMPOUNDS = NO |
558 | - |
559 | -# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any |
560 | -# documentation blocks found inside the body of a function. |
561 | -# If set to NO (the default) these blocks will be appended to the |
562 | -# function's detailed documentation block. |
563 | - |
564 | -HIDE_IN_BODY_DOCS = NO |
565 | - |
566 | -# The INTERNAL_DOCS tag determines if documentation |
567 | -# that is typed after a \internal command is included. If the tag is set |
568 | -# to NO (the default) then the documentation will be excluded. |
569 | -# Set it to YES to include the internal documentation. |
570 | - |
571 | -INTERNAL_DOCS = NO |
572 | - |
573 | -# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate |
574 | -# file names in lower-case letters. If set to YES upper-case letters are also |
575 | -# allowed. This is useful if you have classes or files whose names only differ |
576 | -# in case and if your file system supports case sensitive file names. Windows |
577 | -# and Mac users are advised to set this option to NO. |
578 | - |
579 | -CASE_SENSE_NAMES = YES |
580 | - |
581 | -# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen |
582 | -# will show members with their full class and namespace scopes in the |
583 | -# documentation. If set to YES the scope will be hidden. |
584 | - |
585 | -HIDE_SCOPE_NAMES = NO |
586 | - |
587 | -# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen |
588 | -# will put a list of the files that are included by a file in the documentation |
589 | -# of that file. |
590 | - |
591 | -SHOW_INCLUDE_FILES = YES |
592 | - |
593 | -# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen |
594 | -# will list include files with double quotes in the documentation |
595 | -# rather than with sharp brackets. |
596 | - |
597 | -FORCE_LOCAL_INCLUDES = NO |
598 | - |
599 | -# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] |
600 | -# is inserted in the documentation for inline members. |
601 | - |
602 | -INLINE_INFO = YES |
603 | - |
604 | -# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen |
605 | -# will sort the (detailed) documentation of file and class members |
606 | -# alphabetically by member name. If set to NO the members will appear in |
607 | -# declaration order. |
608 | - |
609 | -SORT_MEMBER_DOCS = YES |
610 | - |
611 | -# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the |
612 | -# brief documentation of file, namespace and class members alphabetically |
613 | -# by member name. If set to NO (the default) the members will appear in |
614 | -# declaration order. |
615 | - |
616 | -SORT_BRIEF_DOCS = NO |
617 | - |
618 | -# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen |
619 | -# will sort the (brief and detailed) documentation of class members so that |
620 | -# constructors and destructors are listed first. If set to NO (the default) |
621 | -# the constructors will appear in the respective orders defined by |
622 | -# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. |
623 | -# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO |
624 | -# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. |
625 | - |
626 | -SORT_MEMBERS_CTORS_1ST = NO |
627 | - |
628 | -# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the |
629 | -# hierarchy of group names into alphabetical order. If set to NO (the default) |
630 | -# the group names will appear in their defined order. |
631 | - |
632 | -SORT_GROUP_NAMES = NO |
633 | - |
634 | -# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be |
635 | -# sorted by fully-qualified names, including namespaces. If set to |
636 | -# NO (the default), the class list will be sorted only by class name, |
637 | -# not including the namespace part. |
638 | -# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. |
639 | -# Note: This option applies only to the class list, not to the |
640 | -# alphabetical list. |
641 | - |
642 | -SORT_BY_SCOPE_NAME = NO |
643 | - |
644 | -# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to |
645 | -# do proper type resolution of all parameters of a function it will reject a |
646 | -# match between the prototype and the implementation of a member function even |
647 | -# if there is only one candidate or it is obvious which candidate to choose |
648 | -# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen |
649 | -# will still accept a match between prototype and implementation in such cases. |
650 | - |
651 | -STRICT_PROTO_MATCHING = NO |
652 | - |
653 | -# The GENERATE_TODOLIST tag can be used to enable (YES) or |
654 | -# disable (NO) the todo list. This list is created by putting \todo |
655 | -# commands in the documentation. |
656 | - |
657 | -GENERATE_TODOLIST = YES |
658 | - |
659 | -# The GENERATE_TESTLIST tag can be used to enable (YES) or |
660 | -# disable (NO) the test list. This list is created by putting \test |
661 | -# commands in the documentation. |
662 | - |
663 | -GENERATE_TESTLIST = YES |
664 | - |
665 | -# The GENERATE_BUGLIST tag can be used to enable (YES) or |
666 | -# disable (NO) the bug list. This list is created by putting \bug |
667 | -# commands in the documentation. |
668 | - |
669 | -GENERATE_BUGLIST = YES |
670 | - |
671 | -# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or |
672 | -# disable (NO) the deprecated list. This list is created by putting |
673 | -# \deprecated commands in the documentation. |
674 | - |
675 | -GENERATE_DEPRECATEDLIST= YES |
676 | - |
677 | -# The ENABLED_SECTIONS tag can be used to enable conditional |
678 | -# documentation sections, marked by \if section-label ... \endif |
679 | -# and \cond section-label ... \endcond blocks. |
680 | - |
681 | -ENABLED_SECTIONS = |
682 | - |
683 | -# The MAX_INITIALIZER_LINES tag determines the maximum number of lines |
684 | -# the initial value of a variable or macro consists of for it to appear in |
685 | -# the documentation. If the initializer consists of more lines than specified |
686 | -# here it will be hidden. Use a value of 0 to hide initializers completely. |
687 | -# The appearance of the initializer of individual variables and macros in the |
688 | -# documentation can be controlled using \showinitializer or \hideinitializer |
689 | -# command in the documentation regardless of this setting. |
690 | - |
691 | -MAX_INITIALIZER_LINES = 30 |
692 | - |
693 | -# Set the SHOW_USED_FILES tag to NO to disable the list of files generated |
694 | -# at the bottom of the documentation of classes and structs. If set to YES the |
695 | -# list will mention the files that were used to generate the documentation. |
696 | - |
697 | -SHOW_USED_FILES = YES |
698 | - |
699 | -# Set the SHOW_FILES tag to NO to disable the generation of the Files page. |
700 | -# This will remove the Files entry from the Quick Index and from the |
701 | -# Folder Tree View (if specified). The default is YES. |
702 | - |
703 | -SHOW_FILES = YES |
704 | - |
705 | -# Set the SHOW_NAMESPACES tag to NO to disable the generation of the |
706 | -# Namespaces page. |
707 | -# This will remove the Namespaces entry from the Quick Index |
708 | -# and from the Folder Tree View (if specified). The default is YES. |
709 | - |
710 | -SHOW_NAMESPACES = YES |
711 | - |
712 | -# The FILE_VERSION_FILTER tag can be used to specify a program or script that |
713 | -# doxygen should invoke to get the current version for each file (typically from |
714 | -# the version control system). Doxygen will invoke the program by executing (via |
715 | -# popen()) the command <command> <input-file>, where <command> is the value of |
716 | -# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file |
717 | -# provided by doxygen. Whatever the program writes to standard output |
718 | -# is used as the file version. See the manual for examples. |
719 | - |
720 | -FILE_VERSION_FILTER = |
721 | - |
722 | -# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed |
723 | -# by doxygen. The layout file controls the global structure of the generated |
724 | -# output files in an output format independent way. To create the layout file |
725 | -# that represents doxygen's defaults, run doxygen with the -l option. |
726 | -# You can optionally specify a file name after the option, if omitted |
727 | -# DoxygenLayout.xml will be used as the name of the layout file. |
728 | - |
729 | -LAYOUT_FILE = |
730 | - |
731 | -# The CITE_BIB_FILES tag can be used to specify one or more bib files |
732 | -# containing the references data. This must be a list of .bib files. The |
733 | -# .bib extension is automatically appended if omitted. Using this command |
734 | -# requires the bibtex tool to be installed. See also |
735 | -# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style |
736 | -# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this |
737 | -# feature you need bibtex and perl available in the search path. Do not use |
738 | -# file names with spaces, bibtex cannot handle them. |
739 | - |
740 | -CITE_BIB_FILES = |
741 | - |
742 | -#--------------------------------------------------------------------------- |
743 | -# configuration options related to warning and progress messages |
744 | -#--------------------------------------------------------------------------- |
745 | - |
746 | -# The QUIET tag can be used to turn on/off the messages that are generated |
747 | -# by doxygen. Possible values are YES and NO. If left blank NO is used. |
748 | - |
749 | -QUIET = YES |
750 | - |
751 | -# The WARNINGS tag can be used to turn on/off the warning messages that are |
752 | -# generated by doxygen. Possible values are YES and NO. If left blank |
753 | -# NO is used. |
754 | - |
755 | -WARNINGS = YES |
756 | - |
757 | -# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings |
758 | -# for undocumented members. If EXTRACT_ALL is set to YES then this flag will |
759 | -# automatically be disabled. |
760 | - |
761 | -WARN_IF_UNDOCUMENTED = YES |
762 | - |
763 | -# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for |
764 | -# potential errors in the documentation, such as not documenting some |
765 | -# parameters in a documented function, or documenting parameters that |
766 | -# don't exist or using markup commands wrongly. |
767 | - |
768 | -WARN_IF_DOC_ERROR = YES |
769 | - |
770 | -# The WARN_NO_PARAMDOC option can be enabled to get warnings for |
771 | -# functions that are documented, but have no documentation for their parameters |
772 | -# or return value. If set to NO (the default) doxygen will only warn about |
773 | -# wrong or incomplete parameter documentation, but not about the absence of |
774 | -# documentation. |
775 | - |
776 | -WARN_NO_PARAMDOC = NO |
777 | - |
778 | -# The WARN_FORMAT tag determines the format of the warning messages that |
779 | -# doxygen can produce. The string should contain the $file, $line, and $text |
780 | -# tags, which will be replaced by the file and line number from which the |
781 | -# warning originated and the warning text. Optionally the format may contain |
782 | -# $version, which will be replaced by the version of the file (if it could |
783 | -# be obtained via FILE_VERSION_FILTER) |
784 | - |
785 | -WARN_FORMAT = "$file:$line: $text" |
786 | - |
787 | -# The WARN_LOGFILE tag can be used to specify a file to which warning |
788 | -# and error messages should be written. If left blank the output is written |
789 | -# to stderr. |
790 | - |
791 | -WARN_LOGFILE = |
792 | - |
793 | -#--------------------------------------------------------------------------- |
794 | -# configuration options related to the input files |
795 | -#--------------------------------------------------------------------------- |
796 | - |
797 | -# The INPUT tag can be used to specify the files and/or directories that contain |
798 | -# documented source files. You may enter file names like "myfile.cpp" or |
799 | -# directories like "/usr/src/myproject". Separate the files or directories |
800 | -# with spaces. |
801 | - |
802 | -INPUT = @DOXYFILE_SOURCE_DIRS@ |
803 | - |
804 | -# This tag can be used to specify the character encoding of the source files |
805 | -# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is |
806 | -# also the default input encoding. Doxygen uses libiconv (or the iconv built |
807 | -# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for |
808 | -# the list of possible encodings. |
809 | - |
810 | -INPUT_ENCODING = UTF-8 |
811 | - |
812 | -# If the value of the INPUT tag contains directories, you can use the |
813 | -# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp |
814 | -# and *.h) to filter out the source-files in the directories. If left |
815 | -# blank the following patterns are tested: |
816 | -# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh |
817 | -# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py |
818 | -# *.f90 *.f *.for *.vhd *.vhdl |
819 | - |
820 | -FILE_PATTERNS = |
821 | - |
822 | -# The RECURSIVE tag can be used to turn specify whether or not subdirectories |
823 | -# should be searched for input files as well. Possible values are YES and NO. |
824 | -# If left blank NO is used. |
825 | - |
826 | -RECURSIVE = YES |
827 | - |
828 | -# The EXCLUDE tag can be used to specify files and/or directories that should be |
829 | -# excluded from the INPUT source files. This way you can easily exclude a |
830 | -# subdirectory from a directory tree whose root is specified with the INPUT tag. |
831 | -# Note that relative paths are relative to the directory from which doxygen is |
832 | -# run. |
833 | - |
834 | -EXCLUDE = "_darcs" |
835 | - |
836 | -# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or |
837 | -# directories that are symbolic links (a Unix file system feature) are excluded |
838 | -# from the input. |
839 | - |
840 | -EXCLUDE_SYMLINKS = NO |
841 | - |
842 | -# If the value of the INPUT tag contains directories, you can use the |
843 | -# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude |
844 | -# certain files from those directories. Note that the wildcards are matched |
845 | -# against the file with absolute path, so to exclude all test directories |
846 | -# for example use the pattern */test/* |
847 | - |
848 | -EXCLUDE_PATTERNS = "*/.*" \ |
849 | - "*/.*/*" |
850 | - |
851 | -# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names |
852 | -# (namespaces, classes, functions, etc.) that should be excluded from the |
853 | -# output. The symbol name can be a fully qualified name, a word, or if the |
854 | -# wildcard * is used, a substring. Examples: ANamespace, AClass, |
855 | -# AClass::ANamespace, ANamespace::*Test |
856 | - |
857 | -EXCLUDE_SYMBOLS = |
858 | - |
859 | -# The EXAMPLE_PATH tag can be used to specify one or more files or |
860 | -# directories that contain example code fragments that are included (see |
861 | -# the \include command). |
862 | - |
863 | -EXAMPLE_PATH = "@CMAKE_CURRENT_SOURCE_DIR@/examples" |
864 | - |
865 | -# If the value of the EXAMPLE_PATH tag contains directories, you can use the |
866 | -# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp |
867 | -# and *.h) to filter out the source-files in the directories. If left |
868 | -# blank all files are included. |
869 | - |
870 | -EXAMPLE_PATTERNS = |
871 | - |
872 | -# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be |
873 | -# searched for input files to be used with the \include or \dontinclude |
874 | -# commands irrespective of the value of the RECURSIVE tag. |
875 | -# Possible values are YES and NO. If left blank NO is used. |
876 | - |
877 | -EXAMPLE_RECURSIVE = NO |
878 | - |
879 | -# The IMAGE_PATH tag can be used to specify one or more files or |
880 | -# directories that contain image that are included in the documentation (see |
881 | -# the \image command). |
882 | - |
883 | -IMAGE_PATH = "@CMAKE_CURRENT_SOURCE_DIR@" |
884 | - |
885 | -# The INPUT_FILTER tag can be used to specify a program that doxygen should |
886 | -# invoke to filter for each input file. Doxygen will invoke the filter program |
887 | -# by executing (via popen()) the command <filter> <input-file>, where <filter> |
888 | -# is the value of the INPUT_FILTER tag, and <input-file> is the name of an |
889 | -# input file. Doxygen will then use the output that the filter program writes |
890 | -# to standard output. |
891 | -# If FILTER_PATTERNS is specified, this tag will be ignored. |
892 | -# Note that the filter must not add or remove lines; it is applied before the |
893 | -# code is scanned, but not when the output code is generated. If lines are added |
894 | -# or removed, the anchors will not be placed correctly. |
895 | - |
896 | -INPUT_FILTER = |
897 | - |
898 | -# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern |
899 | -# basis. |
900 | -# Doxygen will compare the file name with each pattern and apply the |
901 | -# filter if there is a match. |
902 | -# The filters are a list of the form: |
903 | -# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further |
904 | -# info on how filters are used. If FILTER_PATTERNS is empty or if |
905 | -# non of the patterns match the file name, INPUT_FILTER is applied. |
906 | - |
907 | -FILTER_PATTERNS = |
908 | - |
909 | -# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using |
910 | -# INPUT_FILTER) will be used to filter the input files when producing source |
911 | -# files to browse (i.e. when SOURCE_BROWSER is set to YES). |
912 | - |
913 | -FILTER_SOURCE_FILES = NO |
914 | - |
915 | -# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file |
916 | -# pattern. A pattern will override the setting for FILTER_PATTERN (if any) |
917 | -# and it is also possible to disable source filtering for a specific pattern |
918 | -# using *.ext= (so without naming a filter). This option only has effect when |
919 | -# FILTER_SOURCE_FILES is enabled. |
920 | - |
921 | -FILTER_SOURCE_PATTERNS = |
922 | - |
923 | -# If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that |
924 | -# is part of the input, its contents will be placed on the main page |
925 | -# (index.html). This can be useful if you have a project on for instance GitHub |
926 | -# and want reuse the introduction page also for the doxygen output. |
927 | - |
928 | -USE_MDFILE_AS_MAINPAGE = |
929 | - |
930 | -#--------------------------------------------------------------------------- |
931 | -# configuration options related to source browsing |
932 | -#--------------------------------------------------------------------------- |
933 | - |
934 | -# If the SOURCE_BROWSER tag is set to YES then a list of source files will |
935 | -# be generated. Documented entities will be cross-referenced with these sources. |
936 | -# Note: To get rid of all source code in the generated output, make sure also |
937 | -# VERBATIM_HEADERS is set to NO. |
938 | - |
939 | -SOURCE_BROWSER = NO |
940 | - |
941 | -# Setting the INLINE_SOURCES tag to YES will include the body |
942 | -# of functions and classes directly in the documentation. |
943 | - |
944 | -INLINE_SOURCES = NO |
945 | - |
946 | -# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct |
947 | -# doxygen to hide any special comment blocks from generated source code |
948 | -# fragments. Normal C, C++ and Fortran comments will always remain visible. |
949 | - |
950 | -STRIP_CODE_COMMENTS = YES |
951 | - |
952 | -# If the REFERENCED_BY_RELATION tag is set to YES |
953 | -# then for each documented function all documented |
954 | -# functions referencing it will be listed. |
955 | - |
956 | -REFERENCED_BY_RELATION = NO |
957 | - |
958 | -# If the REFERENCES_RELATION tag is set to YES |
959 | -# then for each documented function all documented entities |
960 | -# called/used by that function will be listed. |
961 | - |
962 | -REFERENCES_RELATION = NO |
963 | - |
964 | -# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) |
965 | -# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from |
966 | -# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will |
967 | -# link to the source code. |
968 | -# Otherwise they will link to the documentation. |
969 | - |
970 | -REFERENCES_LINK_SOURCE = YES |
971 | - |
972 | -# If the USE_HTAGS tag is set to YES then the references to source code |
973 | -# will point to the HTML generated by the htags(1) tool instead of doxygen |
974 | -# built-in source browser. The htags tool is part of GNU's global source |
975 | -# tagging system (see http://www.gnu.org/software/global/global.html). You |
976 | -# will need version 4.8.6 or higher. |
977 | - |
978 | -USE_HTAGS = NO |
979 | - |
980 | -# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen |
981 | -# will generate a verbatim copy of the header file for each class for |
982 | -# which an include is specified. Set to NO to disable this. |
983 | - |
984 | -VERBATIM_HEADERS = YES |
985 | - |
986 | -#--------------------------------------------------------------------------- |
987 | -# configuration options related to the alphabetical class index |
988 | -#--------------------------------------------------------------------------- |
989 | - |
990 | -# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index |
991 | -# of all compounds will be generated. Enable this if the project |
992 | -# contains a lot of classes, structs, unions or interfaces. |
993 | - |
994 | -ALPHABETICAL_INDEX = YES |
995 | - |
996 | -# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then |
997 | -# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns |
998 | -# in which this list will be split (can be a number in the range [1..20]) |
999 | - |
1000 | -COLS_IN_ALPHA_INDEX = 5 |
1001 | - |
1002 | -# In case all classes in a project start with a common prefix, all |
1003 | -# classes will be put under the same header in the alphabetical index. |
1004 | -# The IGNORE_PREFIX tag can be used to specify one or more prefixes that |
1005 | -# should be ignored while generating the index headers. |
1006 | - |
1007 | -IGNORE_PREFIX = |
1008 | - |
1009 | -#--------------------------------------------------------------------------- |
1010 | -# configuration options related to the HTML output |
1011 | -#--------------------------------------------------------------------------- |
1012 | - |
1013 | -# If the GENERATE_HTML tag is set to YES (the default) Doxygen will |
1014 | -# generate HTML output. |
1015 | - |
1016 | -GENERATE_HTML = YES |
1017 | - |
1018 | -# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. |
1019 | -# If a relative path is entered the value of OUTPUT_DIRECTORY will be |
1020 | -# put in front of it. If left blank `html' will be used as the default path. |
1021 | - |
1022 | -HTML_OUTPUT = "@DOXYFILE_HTML_DIR@" |
1023 | - |
1024 | -# The HTML_FILE_EXTENSION tag can be used to specify the file extension for |
1025 | -# each generated HTML page (for example: .htm,.php,.asp). If it is left blank |
1026 | -# doxygen will generate files with .html extension. |
1027 | - |
1028 | -HTML_FILE_EXTENSION = .html |
1029 | - |
1030 | -# The HTML_HEADER tag can be used to specify a personal HTML header for |
1031 | -# each generated HTML page. If it is left blank doxygen will generate a |
1032 | -# standard header. Note that when using a custom header you are responsible |
1033 | -# for the proper inclusion of any scripts and style sheets that doxygen |
1034 | -# needs, which is dependent on the configuration options used. |
1035 | -# It is advised to generate a default header using "doxygen -w html |
1036 | -# header.html footer.html stylesheet.css YourConfigFile" and then modify |
1037 | -# that header. Note that the header is subject to change so you typically |
1038 | -# have to redo this when upgrading to a newer version of doxygen or when |
1039 | -# changing the value of configuration settings such as GENERATE_TREEVIEW! |
1040 | - |
1041 | -HTML_HEADER = |
1042 | - |
1043 | -# The HTML_FOOTER tag can be used to specify a personal HTML footer for |
1044 | -# each generated HTML page. If it is left blank doxygen will generate a |
1045 | -# standard footer. |
1046 | - |
1047 | -HTML_FOOTER = |
1048 | - |
1049 | -# The HTML_STYLESHEET tag can be used to specify a user-defined cascading |
1050 | -# style sheet that is used by each HTML page. It can be used to |
1051 | -# fine-tune the look of the HTML output. If left blank doxygen will |
1052 | -# generate a default style sheet. Note that it is recommended to use |
1053 | -# HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this |
1054 | -# tag will in the future become obsolete. |
1055 | - |
1056 | -HTML_STYLESHEET = |
1057 | - |
1058 | -# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional |
1059 | -# user-defined cascading style sheet that is included after the standard |
1060 | -# style sheets created by doxygen. Using this option one can overrule |
1061 | -# certain style aspects. This is preferred over using HTML_STYLESHEET |
1062 | -# since it does not replace the standard style sheet and is therefor more |
1063 | -# robust against future updates. Doxygen will copy the style sheet file to |
1064 | -# the output directory. |
1065 | - |
1066 | -HTML_EXTRA_STYLESHEET = |
1067 | - |
1068 | -# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or |
1069 | -# other source files which should be copied to the HTML output directory. Note |
1070 | -# that these files will be copied to the base HTML output directory. Use the |
1071 | -# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these |
1072 | -# files. In the HTML_STYLESHEET file, use the file name only. Also note that |
1073 | -# the files will be copied as-is; there are no commands or markers available. |
1074 | - |
1075 | -HTML_EXTRA_FILES = |
1076 | - |
1077 | -# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. |
1078 | -# Doxygen will adjust the colors in the style sheet and background images |
1079 | -# according to this color. Hue is specified as an angle on a colorwheel, |
1080 | -# see http://en.wikipedia.org/wiki/Hue for more information. |
1081 | -# For instance the value 0 represents red, 60 is yellow, 120 is green, |
1082 | -# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. |
1083 | -# The allowed range is 0 to 359. |
1084 | - |
1085 | -HTML_COLORSTYLE_HUE = 220 |
1086 | - |
1087 | -# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of |
1088 | -# the colors in the HTML output. For a value of 0 the output will use |
1089 | -# grayscales only. A value of 255 will produce the most vivid colors. |
1090 | - |
1091 | -HTML_COLORSTYLE_SAT = 100 |
1092 | - |
1093 | -# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to |
1094 | -# the luminance component of the colors in the HTML output. Values below |
1095 | -# 100 gradually make the output lighter, whereas values above 100 make |
1096 | -# the output darker. The value divided by 100 is the actual gamma applied, |
1097 | -# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, |
1098 | -# and 100 does not change the gamma. |
1099 | - |
1100 | -HTML_COLORSTYLE_GAMMA = 80 |
1101 | - |
1102 | -# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML |
1103 | -# page will contain the date and time when the page was generated. Setting |
1104 | -# this to NO can help when comparing the output of multiple runs. |
1105 | - |
1106 | -HTML_TIMESTAMP = YES |
1107 | - |
1108 | -# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML |
1109 | -# documentation will contain sections that can be hidden and shown after the |
1110 | -# page has loaded. |
1111 | - |
1112 | -HTML_DYNAMIC_SECTIONS = YES |
1113 | - |
1114 | -# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of |
1115 | -# entries shown in the various tree structured indices initially; the user |
1116 | -# can expand and collapse entries dynamically later on. Doxygen will expand |
1117 | -# the tree to such a level that at most the specified number of entries are |
1118 | -# visible (unless a fully collapsed tree already exceeds this amount). |
1119 | -# So setting the number of entries 1 will produce a full collapsed tree by |
1120 | -# default. 0 is a special value representing an infinite number of entries |
1121 | -# and will result in a full expanded tree by default. |
1122 | - |
1123 | -HTML_INDEX_NUM_ENTRIES = 100 |
1124 | - |
1125 | -# If the GENERATE_DOCSET tag is set to YES, additional index files |
1126 | -# will be generated that can be used as input for Apple's Xcode 3 |
1127 | -# integrated development environment, introduced with OSX 10.5 (Leopard). |
1128 | -# To create a documentation set, doxygen will generate a Makefile in the |
1129 | -# HTML output directory. Running make will produce the docset in that |
1130 | -# directory and running "make install" will install the docset in |
1131 | -# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find |
1132 | -# it at startup. |
1133 | -# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html |
1134 | -# for more information. |
1135 | - |
1136 | -GENERATE_DOCSET = NO |
1137 | - |
1138 | -# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the |
1139 | -# feed. A documentation feed provides an umbrella under which multiple |
1140 | -# documentation sets from a single provider (such as a company or product suite) |
1141 | -# can be grouped. |
1142 | - |
1143 | -DOCSET_FEEDNAME = "Doxygen generated docs" |
1144 | - |
1145 | -# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that |
1146 | -# should uniquely identify the documentation set bundle. This should be a |
1147 | -# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen |
1148 | -# will append .docset to the name. |
1149 | - |
1150 | -DOCSET_BUNDLE_ID = org.doxygen.Project |
1151 | - |
1152 | -# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely |
1153 | -# identify the documentation publisher. This should be a reverse domain-name |
1154 | -# style string, e.g. com.mycompany.MyDocSet.documentation. |
1155 | - |
1156 | -DOCSET_PUBLISHER_ID = org.doxygen.Publisher |
1157 | - |
1158 | -# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. |
1159 | - |
1160 | -DOCSET_PUBLISHER_NAME = Publisher |
1161 | - |
1162 | -# If the GENERATE_HTMLHELP tag is set to YES, additional index files |
1163 | -# will be generated that can be used as input for tools like the |
1164 | -# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) |
1165 | -# of the generated HTML documentation. |
1166 | - |
1167 | -GENERATE_HTMLHELP = NO |
1168 | - |
1169 | -# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can |
1170 | -# be used to specify the file name of the resulting .chm file. You |
1171 | -# can add a path in front of the file if the result should not be |
1172 | -# written to the html output directory. |
1173 | - |
1174 | -CHM_FILE = |
1175 | - |
1176 | -# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can |
1177 | -# be used to specify the location (absolute path including file name) of |
1178 | -# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run |
1179 | -# the HTML help compiler on the generated index.hhp. |
1180 | - |
1181 | -HHC_LOCATION = |
1182 | - |
1183 | -# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag |
1184 | -# controls if a separate .chi index file is generated (YES) or that |
1185 | -# it should be included in the master .chm file (NO). |
1186 | - |
1187 | -GENERATE_CHI = NO |
1188 | - |
1189 | -# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING |
1190 | -# is used to encode HtmlHelp index (hhk), content (hhc) and project file |
1191 | -# content. |
1192 | - |
1193 | -CHM_INDEX_ENCODING = |
1194 | - |
1195 | -# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag |
1196 | -# controls whether a binary table of contents is generated (YES) or a |
1197 | -# normal table of contents (NO) in the .chm file. |
1198 | - |
1199 | -BINARY_TOC = NO |
1200 | - |
1201 | -# The TOC_EXPAND flag can be set to YES to add extra items for group members |
1202 | -# to the contents of the HTML help documentation and to the tree view. |
1203 | - |
1204 | -TOC_EXPAND = NO |
1205 | - |
1206 | -# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and |
1207 | -# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated |
1208 | -# that can be used as input for Qt's qhelpgenerator to generate a |
1209 | -# Qt Compressed Help (.qch) of the generated HTML documentation. |
1210 | - |
1211 | -GENERATE_QHP = NO |
1212 | - |
1213 | -# If the QHG_LOCATION tag is specified, the QCH_FILE tag can |
1214 | -# be used to specify the file name of the resulting .qch file. |
1215 | -# The path specified is relative to the HTML output folder. |
1216 | - |
1217 | -QCH_FILE = |
1218 | - |
1219 | -# The QHP_NAMESPACE tag specifies the namespace to use when generating |
1220 | -# Qt Help Project output. For more information please see |
1221 | -# http://doc.trolltech.com/qthelpproject.html#namespace |
1222 | - |
1223 | -QHP_NAMESPACE = |
1224 | - |
1225 | -# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating |
1226 | -# Qt Help Project output. For more information please see |
1227 | -# http://doc.trolltech.com/qthelpproject.html#virtual-folders |
1228 | - |
1229 | -QHP_VIRTUAL_FOLDER = doc |
1230 | - |
1231 | -# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to |
1232 | -# add. For more information please see |
1233 | -# http://doc.trolltech.com/qthelpproject.html#custom-filters |
1234 | - |
1235 | -QHP_CUST_FILTER_NAME = |
1236 | - |
1237 | -# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the |
1238 | -# custom filter to add. For more information please see |
1239 | -# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters"> |
1240 | -# Qt Help Project / Custom Filters</a>. |
1241 | - |
1242 | -QHP_CUST_FILTER_ATTRS = |
1243 | - |
1244 | -# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this |
1245 | -# project's |
1246 | -# filter section matches. |
1247 | -# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes"> |
1248 | -# Qt Help Project / Filter Attributes</a>. |
1249 | - |
1250 | -QHP_SECT_FILTER_ATTRS = |
1251 | - |
1252 | -# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can |
1253 | -# be used to specify the location of Qt's qhelpgenerator. |
1254 | -# If non-empty doxygen will try to run qhelpgenerator on the generated |
1255 | -# .qhp file. |
1256 | - |
1257 | -QHG_LOCATION = |
1258 | - |
1259 | -# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files |
1260 | -# will be generated, which together with the HTML files, form an Eclipse help |
1261 | -# plugin. To install this plugin and make it available under the help contents |
1262 | -# menu in Eclipse, the contents of the directory containing the HTML and XML |
1263 | -# files needs to be copied into the plugins directory of eclipse. The name of |
1264 | -# the directory within the plugins directory should be the same as |
1265 | -# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before |
1266 | -# the help appears. |
1267 | - |
1268 | -GENERATE_ECLIPSEHELP = NO |
1269 | - |
1270 | -# A unique identifier for the eclipse help plugin. When installing the plugin |
1271 | -# the directory name containing the HTML and XML files should also have |
1272 | -# this name. |
1273 | - |
1274 | -ECLIPSE_DOC_ID = org.doxygen.Project |
1275 | - |
1276 | -# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) |
1277 | -# at top of each HTML page. The value NO (the default) enables the index and |
1278 | -# the value YES disables it. Since the tabs have the same information as the |
1279 | -# navigation tree you can set this option to NO if you already set |
1280 | -# GENERATE_TREEVIEW to YES. |
1281 | - |
1282 | -DISABLE_INDEX = NO |
1283 | - |
1284 | -# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index |
1285 | -# structure should be generated to display hierarchical information. |
1286 | -# If the tag value is set to YES, a side panel will be generated |
1287 | -# containing a tree-like index structure (just like the one that |
1288 | -# is generated for HTML Help). For this to work a browser that supports |
1289 | -# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). |
1290 | -# Windows users are probably better off using the HTML help feature. |
1291 | -# Since the tree basically has the same information as the tab index you |
1292 | -# could consider to set DISABLE_INDEX to NO when enabling this option. |
1293 | - |
1294 | -GENERATE_TREEVIEW = NONE |
1295 | - |
1296 | -# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values |
1297 | -# (range [0,1..20]) that doxygen will group on one line in the generated HTML |
1298 | -# documentation. Note that a value of 0 will completely suppress the enum |
1299 | -# values from appearing in the overview section. |
1300 | - |
1301 | -ENUM_VALUES_PER_LINE = 4 |
1302 | - |
1303 | -# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be |
1304 | -# used to set the initial width (in pixels) of the frame in which the tree |
1305 | -# is shown. |
1306 | - |
1307 | -TREEVIEW_WIDTH = 250 |
1308 | - |
1309 | -# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open |
1310 | -# links to external symbols imported via tag files in a separate window. |
1311 | - |
1312 | -EXT_LINKS_IN_WINDOW = NO |
1313 | - |
1314 | -# Use this tag to change the font size of Latex formulas included |
1315 | -# as images in the HTML documentation. The default is 10. Note that |
1316 | -# when you change the font size after a successful doxygen run you need |
1317 | -# to manually remove any form_*.png images from the HTML output directory |
1318 | -# to force them to be regenerated. |
1319 | - |
1320 | -FORMULA_FONTSIZE = 10 |
1321 | - |
1322 | -# Use the FORMULA_TRANPARENT tag to determine whether or not the images |
1323 | -# generated for formulas are transparent PNGs. Transparent PNGs are |
1324 | -# not supported properly for IE 6.0, but are supported on all modern browsers. |
1325 | -# Note that when changing this option you need to delete any form_*.png files |
1326 | -# in the HTML output before the changes have effect. |
1327 | - |
1328 | -FORMULA_TRANSPARENT = YES |
1329 | - |
1330 | -# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax |
1331 | -# (see http://www.mathjax.org) which uses client side Javascript for the |
1332 | -# rendering instead of using prerendered bitmaps. Use this if you do not |
1333 | -# have LaTeX installed or if you want to formulas look prettier in the HTML |
1334 | -# output. When enabled you may also need to install MathJax separately and |
1335 | -# configure the path to it using the MATHJAX_RELPATH option. |
1336 | - |
1337 | -USE_MATHJAX = NO |
1338 | - |
1339 | -# When MathJax is enabled you can set the default output format to be used for |
1340 | -# the MathJax output. Supported types are HTML-CSS, NativeMML (i.e. MathML) and |
1341 | -# SVG. The default value is HTML-CSS, which is slower, but has the best |
1342 | -# compatibility. |
1343 | - |
1344 | -MATHJAX_FORMAT = HTML-CSS |
1345 | - |
1346 | -# When MathJax is enabled you need to specify the location relative to the |
1347 | -# HTML output directory using the MATHJAX_RELPATH option. The destination |
1348 | -# directory should contain the MathJax.js script. For instance, if the mathjax |
1349 | -# directory is located at the same level as the HTML output directory, then |
1350 | -# MATHJAX_RELPATH should be ../mathjax. The default value points to |
1351 | -# the MathJax Content Delivery Network so you can quickly see the result without |
1352 | -# installing MathJax. |
1353 | -# However, it is strongly recommended to install a local |
1354 | -# copy of MathJax from http://www.mathjax.org before deployment. |
1355 | - |
1356 | -MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest |
1357 | - |
1358 | -# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension |
1359 | -# names that should be enabled during MathJax rendering. |
1360 | - |
1361 | -MATHJAX_EXTENSIONS = |
1362 | - |
1363 | -# The MATHJAX_CODEFILE tag can be used to specify a file with javascript |
1364 | -# pieces of code that will be used on startup of the MathJax code. |
1365 | - |
1366 | -MATHJAX_CODEFILE = |
1367 | - |
1368 | -# When the SEARCHENGINE tag is enabled doxygen will generate a search box |
1369 | -# for the HTML output. The underlying search engine uses javascript |
1370 | -# and DHTML and should work on any modern browser. Note that when using |
1371 | -# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets |
1372 | -# (GENERATE_DOCSET) there is already a search function so this one should |
1373 | -# typically be disabled. For large projects the javascript based search engine |
1374 | -# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. |
1375 | - |
1376 | -SEARCHENGINE = NO |
1377 | - |
1378 | -# When the SERVER_BASED_SEARCH tag is enabled the search engine will be |
1379 | -# implemented using a web server instead of a web client using Javascript. |
1380 | -# There are two flavours of web server based search depending on the |
1381 | -# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for |
1382 | -# searching and an index file used by the script. When EXTERNAL_SEARCH is |
1383 | -# enabled the indexing and searching needs to be provided by external tools. |
1384 | -# See the manual for details. |
1385 | - |
1386 | -SERVER_BASED_SEARCH = NO |
1387 | - |
1388 | -# When EXTERNAL_SEARCH is enabled doxygen will no longer generate the PHP |
1389 | -# script for searching. Instead the search results are written to an XML file |
1390 | -# which needs to be processed by an external indexer. Doxygen will invoke an |
1391 | -# external search engine pointed to by the SEARCHENGINE_URL option to obtain |
1392 | -# the search results. Doxygen ships with an example indexer (doxyindexer) and |
1393 | -# search engine (doxysearch.cgi) which are based on the open source search |
1394 | -# engine library Xapian. See the manual for configuration details. |
1395 | - |
1396 | -EXTERNAL_SEARCH = NO |
1397 | - |
1398 | -# The SEARCHENGINE_URL should point to a search engine hosted by a web server |
1399 | -# which will returned the search results when EXTERNAL_SEARCH is enabled. |
1400 | -# Doxygen ships with an example search engine (doxysearch) which is based on |
1401 | -# the open source search engine library Xapian. See the manual for configuration |
1402 | -# details. |
1403 | - |
1404 | -SEARCHENGINE_URL = |
1405 | - |
1406 | -# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed |
1407 | -# search data is written to a file for indexing by an external tool. With the |
1408 | -# SEARCHDATA_FILE tag the name of this file can be specified. |
1409 | - |
1410 | -SEARCHDATA_FILE = searchdata.xml |
1411 | - |
1412 | -# When SERVER_BASED_SEARCH AND EXTERNAL_SEARCH are both enabled the |
1413 | -# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is |
1414 | -# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple |
1415 | -# projects and redirect the results back to the right project. |
1416 | - |
1417 | -EXTERNAL_SEARCH_ID = |
1418 | - |
1419 | -# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen |
1420 | -# projects other than the one defined by this configuration file, but that are |
1421 | -# all added to the same external search index. Each project needs to have a |
1422 | -# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id |
1423 | -# of to a relative location where the documentation can be found. |
1424 | -# The format is: EXTRA_SEARCH_MAPPINGS = id1=loc1 id2=loc2 ... |
1425 | - |
1426 | -EXTRA_SEARCH_MAPPINGS = |
1427 | - |
1428 | -#--------------------------------------------------------------------------- |
1429 | -# configuration options related to the LaTeX output |
1430 | -#--------------------------------------------------------------------------- |
1431 | - |
1432 | -# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will |
1433 | -# generate Latex output. |
1434 | - |
1435 | -GENERATE_LATEX = @DOXYFILE_GENERATE_LATEX@ |
1436 | - |
1437 | -# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. |
1438 | -# If a relative path is entered the value of OUTPUT_DIRECTORY will be |
1439 | -# put in front of it. If left blank `latex' will be used as the default path. |
1440 | - |
1441 | -LATEX_OUTPUT = "@DOXYFILE_LATEX_DIR@" |
1442 | - |
1443 | -# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be |
1444 | -# invoked. If left blank `latex' will be used as the default command name. |
1445 | -# Note that when enabling USE_PDFLATEX this option is only used for |
1446 | -# generating bitmaps for formulas in the HTML output, but not in the |
1447 | -# Makefile that is written to the output directory. |
1448 | - |
1449 | -LATEX_CMD_NAME = "@LATEX_COMPILER@" |
1450 | - |
1451 | -# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to |
1452 | -# generate index for LaTeX. If left blank `makeindex' will be used as the |
1453 | -# default command name. |
1454 | - |
1455 | -MAKEINDEX_CMD_NAME = "@MAKEINDEX_COMPILER@" |
1456 | - |
1457 | -# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact |
1458 | -# LaTeX documents. This may be useful for small projects and may help to |
1459 | -# save some trees in general. |
1460 | - |
1461 | -COMPACT_LATEX = NO |
1462 | - |
1463 | -# The PAPER_TYPE tag can be used to set the paper type that is used |
1464 | -# by the printer. Possible values are: a4, letter, legal and |
1465 | -# executive. If left blank a4 will be used. |
1466 | - |
1467 | -PAPER_TYPE = a4wide |
1468 | - |
1469 | -# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX |
1470 | -# packages that should be included in the LaTeX output. |
1471 | - |
1472 | -EXTRA_PACKAGES = |
1473 | - |
1474 | -# The LATEX_HEADER tag can be used to specify a personal LaTeX header for |
1475 | -# the generated latex document. The header should contain everything until |
1476 | -# the first chapter. If it is left blank doxygen will generate a |
1477 | -# standard header. Notice: only use this tag if you know what you are doing! |
1478 | - |
1479 | -LATEX_HEADER = |
1480 | - |
1481 | -# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for |
1482 | -# the generated latex document. The footer should contain everything after |
1483 | -# the last chapter. If it is left blank doxygen will generate a |
1484 | -# standard footer. Notice: only use this tag if you know what you are doing! |
1485 | - |
1486 | -LATEX_FOOTER = |
1487 | - |
1488 | -# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images |
1489 | -# or other source files which should be copied to the LaTeX output directory. |
1490 | -# Note that the files will be copied as-is; there are no commands or markers |
1491 | -# available. |
1492 | - |
1493 | -LATEX_EXTRA_FILES = |
1494 | - |
1495 | -# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated |
1496 | -# is prepared for conversion to pdf (using ps2pdf). The pdf file will |
1497 | -# contain links (just like the HTML output) instead of page references |
1498 | -# This makes the output suitable for online browsing using a pdf viewer. |
1499 | - |
1500 | -PDF_HYPERLINKS = YES |
1501 | - |
1502 | -# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of |
1503 | -# plain latex in the generated Makefile. Set this option to YES to get a |
1504 | -# higher quality PDF documentation. |
1505 | - |
1506 | -USE_PDFLATEX = @DOXYFILE_PDFLATEX@ |
1507 | - |
1508 | -# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. |
1509 | -# command to the generated LaTeX files. This will instruct LaTeX to keep |
1510 | -# running if errors occur, instead of asking the user for help. |
1511 | -# This option is also used when generating formulas in HTML. |
1512 | - |
1513 | -LATEX_BATCHMODE = YES |
1514 | - |
1515 | -# If LATEX_HIDE_INDICES is set to YES then doxygen will not |
1516 | -# include the index chapters (such as File Index, Compound Index, etc.) |
1517 | -# in the output. |
1518 | - |
1519 | -LATEX_HIDE_INDICES = NO |
1520 | - |
1521 | -# If LATEX_SOURCE_CODE is set to YES then doxygen will include |
1522 | -# source code with syntax highlighting in the LaTeX output. |
1523 | -# Note that which sources are shown also depends on other settings |
1524 | -# such as SOURCE_BROWSER. |
1525 | - |
1526 | -LATEX_SOURCE_CODE = NO |
1527 | - |
1528 | -# The LATEX_BIB_STYLE tag can be used to specify the style to use for the |
1529 | -# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See |
1530 | -# http://en.wikipedia.org/wiki/BibTeX for more info. |
1531 | - |
1532 | -LATEX_BIB_STYLE = plain |
1533 | - |
1534 | -#--------------------------------------------------------------------------- |
1535 | -# configuration options related to the RTF output |
1536 | -#--------------------------------------------------------------------------- |
1537 | - |
1538 | -# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output |
1539 | -# The RTF output is optimized for Word 97 and may not look very pretty with |
1540 | -# other RTF readers or editors. |
1541 | - |
1542 | -GENERATE_RTF = NO |
1543 | - |
1544 | -# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. |
1545 | -# If a relative path is entered the value of OUTPUT_DIRECTORY will be |
1546 | -# put in front of it. If left blank `rtf' will be used as the default path. |
1547 | - |
1548 | -RTF_OUTPUT = rtf |
1549 | - |
1550 | -# If the COMPACT_RTF tag is set to YES Doxygen generates more compact |
1551 | -# RTF documents. This may be useful for small projects and may help to |
1552 | -# save some trees in general. |
1553 | - |
1554 | -COMPACT_RTF = NO |
1555 | - |
1556 | -# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated |
1557 | -# will contain hyperlink fields. The RTF file will |
1558 | -# contain links (just like the HTML output) instead of page references. |
1559 | -# This makes the output suitable for online browsing using WORD or other |
1560 | -# programs which support those fields. |
1561 | -# Note: wordpad (write) and others do not support links. |
1562 | - |
1563 | -RTF_HYPERLINKS = NO |
1564 | - |
1565 | -# Load style sheet definitions from file. Syntax is similar to doxygen's |
1566 | -# config file, i.e. a series of assignments. You only have to provide |
1567 | -# replacements, missing definitions are set to their default value. |
1568 | - |
1569 | -RTF_STYLESHEET_FILE = |
1570 | - |
1571 | -# Set optional variables used in the generation of an rtf document. |
1572 | -# Syntax is similar to doxygen's config file. |
1573 | - |
1574 | -RTF_EXTENSIONS_FILE = |
1575 | - |
1576 | -#--------------------------------------------------------------------------- |
1577 | -# configuration options related to the man page output |
1578 | -#--------------------------------------------------------------------------- |
1579 | - |
1580 | -# If the GENERATE_MAN tag is set to YES (the default) Doxygen will |
1581 | -# generate man pages |
1582 | - |
1583 | -GENERATE_MAN = NO |
1584 | - |
1585 | -# The MAN_OUTPUT tag is used to specify where the man pages will be put. |
1586 | -# If a relative path is entered the value of OUTPUT_DIRECTORY will be |
1587 | -# put in front of it. If left blank `man' will be used as the default path. |
1588 | - |
1589 | -MAN_OUTPUT = man |
1590 | - |
1591 | -# The MAN_EXTENSION tag determines the extension that is added to |
1592 | -# the generated man pages (default is the subroutine's section .3) |
1593 | - |
1594 | -MAN_EXTENSION = .3 |
1595 | - |
1596 | -# If the MAN_LINKS tag is set to YES and Doxygen generates man output, |
1597 | -# then it will generate one additional man file for each entity |
1598 | -# documented in the real man page(s). These additional files |
1599 | -# only source the real man page, but without them the man command |
1600 | -# would be unable to find the correct page. The default is NO. |
1601 | - |
1602 | -MAN_LINKS = NO |
1603 | - |
1604 | -#--------------------------------------------------------------------------- |
1605 | -# configuration options related to the XML output |
1606 | -#--------------------------------------------------------------------------- |
1607 | - |
1608 | -# If the GENERATE_XML tag is set to YES Doxygen will |
1609 | -# generate an XML file that captures the structure of |
1610 | -# the code including all documentation. |
1611 | - |
1612 | -GENERATE_XML = NO |
1613 | - |
1614 | -# The XML_OUTPUT tag is used to specify where the XML pages will be put. |
1615 | -# If a relative path is entered the value of OUTPUT_DIRECTORY will be |
1616 | -# put in front of it. If left blank `xml' will be used as the default path. |
1617 | - |
1618 | -XML_OUTPUT = xml |
1619 | - |
1620 | -# The XML_SCHEMA tag can be used to specify an XML schema, |
1621 | -# which can be used by a validating XML parser to check the |
1622 | -# syntax of the XML files. |
1623 | - |
1624 | -XML_SCHEMA = |
1625 | - |
1626 | -# The XML_DTD tag can be used to specify an XML DTD, |
1627 | -# which can be used by a validating XML parser to check the |
1628 | -# syntax of the XML files. |
1629 | - |
1630 | -XML_DTD = |
1631 | - |
1632 | -# If the XML_PROGRAMLISTING tag is set to YES Doxygen will |
1633 | -# dump the program listings (including syntax highlighting |
1634 | -# and cross-referencing information) to the XML output. Note that |
1635 | -# enabling this will significantly increase the size of the XML output. |
1636 | - |
1637 | -XML_PROGRAMLISTING = YES |
1638 | - |
1639 | -#--------------------------------------------------------------------------- |
1640 | -# configuration options related to the DOCBOOK output |
1641 | -#--------------------------------------------------------------------------- |
1642 | - |
1643 | -# If the GENERATE_DOCBOOK tag is set to YES Doxygen will generate DOCBOOK files |
1644 | -# that can be used to generate PDF. |
1645 | - |
1646 | -GENERATE_DOCBOOK = NO |
1647 | - |
1648 | -# The DOCBOOK_OUTPUT tag is used to specify where the DOCBOOK pages will be put. |
1649 | -# If a relative path is entered the value of OUTPUT_DIRECTORY will be put in |
1650 | -# front of it. If left blank docbook will be used as the default path. |
1651 | - |
1652 | -DOCBOOK_OUTPUT = docbook |
1653 | - |
1654 | -#--------------------------------------------------------------------------- |
1655 | -# configuration options for the AutoGen Definitions output |
1656 | -#--------------------------------------------------------------------------- |
1657 | - |
1658 | -# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will |
1659 | -# generate an AutoGen Definitions (see autogen.sf.net) file |
1660 | -# that captures the structure of the code including all |
1661 | -# documentation. Note that this feature is still experimental |
1662 | -# and incomplete at the moment. |
1663 | - |
1664 | -GENERATE_AUTOGEN_DEF = NO |
1665 | - |
1666 | -#--------------------------------------------------------------------------- |
1667 | -# configuration options related to the Perl module output |
1668 | -#--------------------------------------------------------------------------- |
1669 | - |
1670 | -# If the GENERATE_PERLMOD tag is set to YES Doxygen will |
1671 | -# generate a Perl module file that captures the structure of |
1672 | -# the code including all documentation. Note that this |
1673 | -# feature is still experimental and incomplete at the |
1674 | -# moment. |
1675 | - |
1676 | -GENERATE_PERLMOD = NO |
1677 | - |
1678 | -# If the PERLMOD_LATEX tag is set to YES Doxygen will generate |
1679 | -# the necessary Makefile rules, Perl scripts and LaTeX code to be able |
1680 | -# to generate PDF and DVI output from the Perl module output. |
1681 | - |
1682 | -PERLMOD_LATEX = NO |
1683 | - |
1684 | -# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be |
1685 | -# nicely formatted so it can be parsed by a human reader. |
1686 | -# This is useful |
1687 | -# if you want to understand what is going on. |
1688 | -# On the other hand, if this |
1689 | -# tag is set to NO the size of the Perl module output will be much smaller |
1690 | -# and Perl will parse it just the same. |
1691 | - |
1692 | -PERLMOD_PRETTY = YES |
1693 | - |
1694 | -# The names of the make variables in the generated doxyrules.make file |
1695 | -# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. |
1696 | -# This is useful so different doxyrules.make files included by the same |
1697 | -# Makefile don't overwrite each other's variables. |
1698 | - |
1699 | -PERLMOD_MAKEVAR_PREFIX = |
1700 | - |
1701 | -#--------------------------------------------------------------------------- |
1702 | -# Configuration options related to the preprocessor |
1703 | -#--------------------------------------------------------------------------- |
1704 | - |
1705 | -# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will |
1706 | -# evaluate all C-preprocessor directives found in the sources and include |
1707 | -# files. |
1708 | - |
1709 | -ENABLE_PREPROCESSING = YES |
1710 | - |
1711 | -# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro |
1712 | -# names in the source code. If set to NO (the default) only conditional |
1713 | -# compilation will be performed. Macro expansion can be done in a controlled |
1714 | -# way by setting EXPAND_ONLY_PREDEF to YES. |
1715 | - |
1716 | -MACRO_EXPANSION = NO |
1717 | - |
1718 | -# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES |
1719 | -# then the macro expansion is limited to the macros specified with the |
1720 | -# PREDEFINED and EXPAND_AS_DEFINED tags. |
1721 | - |
1722 | -EXPAND_ONLY_PREDEF = NO |
1723 | - |
1724 | -# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files |
1725 | -# pointed to by INCLUDE_PATH will be searched when a #include is found. |
1726 | - |
1727 | -SEARCH_INCLUDES = YES |
1728 | - |
1729 | -# The INCLUDE_PATH tag can be used to specify one or more directories that |
1730 | -# contain include files that are not input files but should be processed by |
1731 | -# the preprocessor. |
1732 | - |
1733 | -INCLUDE_PATH = |
1734 | - |
1735 | -# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard |
1736 | -# patterns (like *.h and *.hpp) to filter out the header-files in the |
1737 | -# directories. If left blank, the patterns specified with FILE_PATTERNS will |
1738 | -# be used. |
1739 | - |
1740 | -INCLUDE_FILE_PATTERNS = |
1741 | - |
1742 | -# The PREDEFINED tag can be used to specify one or more macro names that |
1743 | -# are defined before the preprocessor is started (similar to the -D option of |
1744 | -# gcc). The argument of the tag is a list of macros of the form: name |
1745 | -# or name=definition (no spaces). If the definition and the = are |
1746 | -# omitted =1 is assumed. To prevent a macro definition from being |
1747 | -# undefined via #undef or recursively expanded use the := operator |
1748 | -# instead of the = operator. |
1749 | - |
1750 | -PREDEFINED = |
1751 | - |
1752 | -# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then |
1753 | -# this tag can be used to specify a list of macro names that should be expanded. |
1754 | -# The macro definition that is found in the sources will be used. |
1755 | -# Use the PREDEFINED tag if you want to use a different macro definition that |
1756 | -# overrules the definition found in the source code. |
1757 | - |
1758 | -EXPAND_AS_DEFINED = |
1759 | - |
1760 | -# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then |
1761 | -# doxygen's preprocessor will remove all references to function-like macros |
1762 | -# that are alone on a line, have an all uppercase name, and do not end with a |
1763 | -# semicolon, because these will confuse the parser if not removed. |
1764 | - |
1765 | -SKIP_FUNCTION_MACROS = YES |
1766 | - |
1767 | -#--------------------------------------------------------------------------- |
1768 | -# Configuration::additions related to external references |
1769 | -#--------------------------------------------------------------------------- |
1770 | - |
1771 | -# The TAGFILES option can be used to specify one or more tagfiles. For each |
1772 | -# tag file the location of the external documentation should be added. The |
1773 | -# format of a tag file without this location is as follows: |
1774 | -# |
1775 | -# TAGFILES = file1 file2 ... |
1776 | -# Adding location for the tag files is done as follows: |
1777 | -# |
1778 | -# TAGFILES = file1=loc1 "file2 = loc2" ... |
1779 | -# where "loc1" and "loc2" can be relative or absolute paths |
1780 | -# or URLs. Note that each tag file must have a unique name (where the name does |
1781 | -# NOT include the path). If a tag file is not located in the directory in which |
1782 | -# doxygen is run, you must also specify the path to the tagfile here. |
1783 | - |
1784 | -TAGFILES = |
1785 | - |
1786 | -# When a file name is specified after GENERATE_TAGFILE, doxygen will create |
1787 | -# a tag file that is based on the input files it reads. |
1788 | - |
1789 | -GENERATE_TAGFILE = |
1790 | - |
1791 | -# If the ALLEXTERNALS tag is set to YES all external classes will be listed |
1792 | -# in the class index. If set to NO only the inherited external classes |
1793 | -# will be listed. |
1794 | - |
1795 | -ALLEXTERNALS = NO |
1796 | - |
1797 | -# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed |
1798 | -# in the modules index. If set to NO, only the current project's groups will |
1799 | -# be listed. |
1800 | - |
1801 | -EXTERNAL_GROUPS = YES |
1802 | - |
1803 | -# If the EXTERNAL_PAGES tag is set to YES all external pages will be listed |
1804 | -# in the related pages index. If set to NO, only the current project's |
1805 | -# pages will be listed. |
1806 | - |
1807 | -EXTERNAL_PAGES = YES |
1808 | - |
1809 | -# The PERL_PATH should be the absolute path and name of the perl script |
1810 | -# interpreter (i.e. the result of `which perl'). |
1811 | - |
1812 | -PERL_PATH = /usr/bin/perl |
1813 | - |
1814 | -#--------------------------------------------------------------------------- |
1815 | -# Configuration options related to the dot tool |
1816 | -#--------------------------------------------------------------------------- |
1817 | - |
1818 | -# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will |
1819 | -# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base |
1820 | -# or super classes. Setting the tag to NO turns the diagrams off. Note that |
1821 | -# this option also works with HAVE_DOT disabled, but it is recommended to |
1822 | -# install and use dot, since it yields more powerful graphs. |
1823 | - |
1824 | -CLASS_DIAGRAMS = YES |
1825 | - |
1826 | -# You can define message sequence charts within doxygen comments using the \msc |
1827 | -# command. Doxygen will then run the mscgen tool (see |
1828 | -# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the |
1829 | -# documentation. The MSCGEN_PATH tag allows you to specify the directory where |
1830 | -# the mscgen tool resides. If left empty the tool is assumed to be found in the |
1831 | -# default search path. |
1832 | - |
1833 | -MSCGEN_PATH = |
1834 | - |
1835 | -# If set to YES, the inheritance and collaboration graphs will hide |
1836 | -# inheritance and usage relations if the target is undocumented |
1837 | -# or is not a class. |
1838 | - |
1839 | -HIDE_UNDOC_RELATIONS = YES |
1840 | - |
1841 | -# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is |
1842 | -# available from the path. This tool is part of Graphviz, a graph visualization |
1843 | -# toolkit from AT&T and Lucent Bell Labs. The other options in this section |
1844 | -# have no effect if this option is set to NO (the default) |
1845 | - |
1846 | -HAVE_DOT = @DOXYFILE_DOT@ |
1847 | - |
1848 | -# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is |
1849 | -# allowed to run in parallel. When set to 0 (the default) doxygen will |
1850 | -# base this on the number of processors available in the system. You can set it |
1851 | -# explicitly to a value larger than 0 to get control over the balance |
1852 | -# between CPU load and processing speed. |
1853 | - |
1854 | -DOT_NUM_THREADS = 0 |
1855 | - |
1856 | -# By default doxygen will use the Helvetica font for all dot files that |
1857 | -# doxygen generates. When you want a differently looking font you can specify |
1858 | -# the font name using DOT_FONTNAME. You need to make sure dot is able to find |
1859 | -# the font, which can be done by putting it in a standard location or by setting |
1860 | -# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the |
1861 | -# directory containing the font. |
1862 | - |
1863 | -DOT_FONTNAME = |
1864 | - |
1865 | -# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. |
1866 | -# The default size is 10pt. |
1867 | - |
1868 | -DOT_FONTSIZE = 10 |
1869 | - |
1870 | -# By default doxygen will tell dot to use the Helvetica font. |
1871 | -# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to |
1872 | -# set the path where dot can find it. |
1873 | - |
1874 | -DOT_FONTPATH = |
1875 | - |
1876 | -# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen |
1877 | -# will generate a graph for each documented class showing the direct and |
1878 | -# indirect inheritance relations. Setting this tag to YES will force the |
1879 | -# CLASS_DIAGRAMS tag to NO. |
1880 | - |
1881 | -CLASS_GRAPH = YES |
1882 | - |
1883 | -# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen |
1884 | -# will generate a graph for each documented class showing the direct and |
1885 | -# indirect implementation dependencies (inheritance, containment, and |
1886 | -# class references variables) of the class with other documented classes. |
1887 | - |
1888 | -COLLABORATION_GRAPH = YES |
1889 | - |
1890 | -# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen |
1891 | -# will generate a graph for groups, showing the direct groups dependencies |
1892 | - |
1893 | -GROUP_GRAPHS = YES |
1894 | - |
1895 | -# If the UML_LOOK tag is set to YES doxygen will generate inheritance and |
1896 | -# collaboration diagrams in a style similar to the OMG's Unified Modeling |
1897 | -# Language. |
1898 | - |
1899 | -UML_LOOK = NO |
1900 | - |
1901 | -# If the UML_LOOK tag is enabled, the fields and methods are shown inside |
1902 | -# the class node. If there are many fields or methods and many nodes the |
1903 | -# graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS |
1904 | -# threshold limits the number of items for each type to make the size more |
1905 | -# manageable. Set this to 0 for no limit. Note that the threshold may be |
1906 | -# exceeded by 50% before the limit is enforced. |
1907 | - |
1908 | -UML_LIMIT_NUM_FIELDS = 10 |
1909 | - |
1910 | -# If set to YES, the inheritance and collaboration graphs will show the |
1911 | -# relations between templates and their instances. |
1912 | - |
1913 | -TEMPLATE_RELATIONS = NO |
1914 | - |
1915 | -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT |
1916 | -# tags are set to YES then doxygen will generate a graph for each documented |
1917 | -# file showing the direct and indirect include dependencies of the file with |
1918 | -# other documented files. |
1919 | - |
1920 | -INCLUDE_GRAPH = YES |
1921 | - |
1922 | -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and |
1923 | -# HAVE_DOT tags are set to YES then doxygen will generate a graph for each |
1924 | -# documented header file showing the documented files that directly or |
1925 | -# indirectly include this file. |
1926 | - |
1927 | -INCLUDED_BY_GRAPH = YES |
1928 | - |
1929 | -# If the CALL_GRAPH and HAVE_DOT options are set to YES then |
1930 | -# doxygen will generate a call dependency graph for every global function |
1931 | -# or class method. Note that enabling this option will significantly increase |
1932 | -# the time of a run. So in most cases it will be better to enable call graphs |
1933 | -# for selected functions only using the \callgraph command. |
1934 | - |
1935 | -CALL_GRAPH = NO |
1936 | - |
1937 | -# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then |
1938 | -# doxygen will generate a caller dependency graph for every global function |
1939 | -# or class method. Note that enabling this option will significantly increase |
1940 | -# the time of a run. So in most cases it will be better to enable caller |
1941 | -# graphs for selected functions only using the \callergraph command. |
1942 | - |
1943 | -CALLER_GRAPH = NO |
1944 | - |
1945 | -# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen |
1946 | -# will generate a graphical hierarchy of all classes instead of a textual one. |
1947 | - |
1948 | -GRAPHICAL_HIERARCHY = YES |
1949 | - |
1950 | -# If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES |
1951 | -# then doxygen will show the dependencies a directory has on other directories |
1952 | -# in a graphical way. The dependency relations are determined by the #include |
1953 | -# relations between the files in the directories. |
1954 | - |
1955 | -DIRECTORY_GRAPH = YES |
1956 | - |
1957 | -# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images |
1958 | -# generated by dot. Possible values are svg, png, jpg, or gif. |
1959 | -# If left blank png will be used. If you choose svg you need to set |
1960 | -# HTML_FILE_EXTENSION to xhtml in order to make the SVG files |
1961 | -# visible in IE 9+ (other browsers do not have this requirement). |
1962 | - |
1963 | -DOT_IMAGE_FORMAT = png |
1964 | - |
1965 | -# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to |
1966 | -# enable generation of interactive SVG images that allow zooming and panning. |
1967 | -# Note that this requires a modern browser other than Internet Explorer. |
1968 | -# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you |
1969 | -# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files |
1970 | -# visible. Older versions of IE do not have SVG support. |
1971 | - |
1972 | -INTERACTIVE_SVG = NO |
1973 | - |
1974 | -# The tag DOT_PATH can be used to specify the path where the dot tool can be |
1975 | -# found. If left blank, it is assumed the dot tool can be found in the path. |
1976 | - |
1977 | -DOT_PATH = "@DOXYGEN_DOT_PATH@" |
1978 | - |
1979 | -# The DOTFILE_DIRS tag can be used to specify one or more directories that |
1980 | -# contain dot files that are included in the documentation (see the |
1981 | -# \dotfile command). |
1982 | - |
1983 | -DOTFILE_DIRS = |
1984 | - |
1985 | -# The MSCFILE_DIRS tag can be used to specify one or more directories that |
1986 | -# contain msc files that are included in the documentation (see the |
1987 | -# \mscfile command). |
1988 | - |
1989 | -MSCFILE_DIRS = |
1990 | - |
1991 | -# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of |
1992 | -# nodes that will be shown in the graph. If the number of nodes in a graph |
1993 | -# becomes larger than this value, doxygen will truncate the graph, which is |
1994 | -# visualized by representing a node as a red box. Note that doxygen if the |
1995 | -# number of direct children of the root node in a graph is already larger than |
1996 | -# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note |
1997 | -# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. |
1998 | - |
1999 | -DOT_GRAPH_MAX_NODES = 50 |
2000 | - |
2001 | -# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the |
2002 | -# graphs generated by dot. A depth value of 3 means that only nodes reachable |
2003 | -# from the root by following a path via at most 3 edges will be shown. Nodes |
2004 | -# that lay further from the root node will be omitted. Note that setting this |
2005 | -# option to 1 or 2 may greatly reduce the computation time needed for large |
2006 | -# code bases. Also note that the size of a graph can be further restricted by |
2007 | -# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. |
2008 | - |
2009 | -MAX_DOT_GRAPH_DEPTH = 0 |
2010 | - |
2011 | -# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent |
2012 | -# background. This is disabled by default, because dot on Windows does not |
2013 | -# seem to support this out of the box. Warning: Depending on the platform used, |
2014 | -# enabling this option may lead to badly anti-aliased labels on the edges of |
2015 | -# a graph (i.e. they become hard to read). |
2016 | - |
2017 | -DOT_TRANSPARENT = YES |
2018 | - |
2019 | -# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output |
2020 | -# files in one run (i.e. multiple -o and -T options on the command line). This |
2021 | -# makes dot run faster, but since only newer versions of dot (>1.8.10) |
2022 | -# support this, this feature is disabled by default. |
2023 | - |
2024 | -DOT_MULTI_TARGETS = NO |
2025 | - |
2026 | -# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will |
2027 | -# generate a legend page explaining the meaning of the various boxes and |
2028 | -# arrows in the dot generated graphs. |
2029 | - |
2030 | -GENERATE_LEGEND = YES |
2031 | - |
2032 | -# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will |
2033 | -# remove the intermediate dot files that are used to generate |
2034 | -# the various graphs. |
2035 | - |
2036 | -DOT_CLEANUP = YES |
2037 | |
2038 | === removed file 'cmake/FindGMock.cmake' |
2039 | --- cmake/FindGMock.cmake 2013-07-10 15:23:46 +0000 |
2040 | +++ cmake/FindGMock.cmake 1970-01-01 00:00:00 +0000 |
2041 | @@ -1,10 +0,0 @@ |
2042 | -# Build with system gmock and embedded gtest |
2043 | -set (GMOCK_INCLUDE_DIRS "/usr/include/gmock/include" CACHE PATH "gmock source include directory") |
2044 | -set (GMOCK_SOURCE_DIR "/usr/src/gmock" CACHE PATH "gmock source directory") |
2045 | -set (GTEST_INCLUDE_DIRS "${GMOCK_SOURCE_DIR}/gtest/include" CACHE PATH "gtest source include directory") |
2046 | - |
2047 | -add_subdirectory(${GMOCK_SOURCE_DIR} "${CMAKE_CURRENT_BINARY_DIR}/gmock") |
2048 | - |
2049 | -set(GTEST_LIBRARIES gtest) |
2050 | -set(GTEST_MAIN_LIBRARIES gtest_main) |
2051 | -set(GMOCK_LIBRARIES gmock gmock_main) |
2052 | |
2053 | === removed file 'cmake/FindValgrind.cmake' |
2054 | --- cmake/FindValgrind.cmake 2013-09-26 09:12:58 +0000 |
2055 | +++ cmake/FindValgrind.cmake 1970-01-01 00:00:00 +0000 |
2056 | @@ -1,34 +0,0 @@ |
2057 | - |
2058 | -option( |
2059 | - ENABLE_MEMCHECK_OPTION |
2060 | - "If set to ON, enables automatic creation of memcheck targets" |
2061 | - OFF |
2062 | -) |
2063 | - |
2064 | -find_program( |
2065 | - VALGRIND_PROGRAM |
2066 | - NAMES valgrind |
2067 | -) |
2068 | - |
2069 | -if(VALGRIND_PROGRAM) |
2070 | - set(VALGRIND_PROGRAM_OPTIONS |
2071 | - "--suppressions=${CMAKE_SOURCE_DIR}/tests/data/valgrind.suppression" |
2072 | - "--gen-suppressions=all" |
2073 | - "--error-exitcode=1" |
2074 | - "--leak-check=full" |
2075 | - "--quiet" |
2076 | - ) |
2077 | -endif() |
2078 | - |
2079 | -find_package_handle_standard_args( |
2080 | - VALGRIND DEFAULT_MSG |
2081 | - VALGRIND_PROGRAM |
2082 | -) |
2083 | - |
2084 | -function(add_valgrind_test NAME EXECUTABLE) |
2085 | - if(ENABLE_MEMCHECK_OPTION) |
2086 | - add_test(${NAME} ${VALGRIND_PROGRAM} ${VALGRIND_PROGRAM_OPTIONS} "${CMAKE_CURRENT_BINARY_DIR}/${EXECUTABLE}") |
2087 | - else() |
2088 | - add_test(${NAME} ${EXECUTABLE}) |
2089 | - endif() |
2090 | -endfunction() |
2091 | |
2092 | === removed file 'cmake/UseDoxygen.cmake' |
2093 | --- cmake/UseDoxygen.cmake 2013-06-11 09:01:30 +0000 |
2094 | +++ cmake/UseDoxygen.cmake 1970-01-01 00:00:00 +0000 |
2095 | @@ -1,154 +0,0 @@ |
2096 | - # - Run Doxygen |
2097 | -# |
2098 | -# Adds a doxygen target that runs doxygen to generate the html |
2099 | -# and optionally the LaTeX API documentation. |
2100 | -# The doxygen target is added to the doc target as a dependency. |
2101 | -# i.e.: the API documentation is built with: |
2102 | -# make doc |
2103 | -# |
2104 | -# USAGE: GLOBAL INSTALL |
2105 | -# |
2106 | -# Install it with: |
2107 | -# cmake ./ && sudo make install |
2108 | -# Add the following to the CMakeLists.txt of your project: |
2109 | -# include(UseDoxygen OPTIONAL) |
2110 | -# Optionally copy Doxyfile.in in the directory of CMakeLists.txt and edit it. |
2111 | -# |
2112 | -# USAGE: INCLUDE IN PROJECT |
2113 | -# |
2114 | -# set(CMAKE_MODULE_PATH ${CMAKE_CURRENT_SOURCE_DIR}) |
2115 | -# include(UseDoxygen) |
2116 | -# Add the Doxyfile.in and UseDoxygen.cmake files to the projects source directory. |
2117 | -# |
2118 | -# |
2119 | -# CONFIGURATION |
2120 | -# |
2121 | -# To configure Doxygen you can edit Doxyfile.in and set some variables in cmake. |
2122 | -# Variables you may define are: |
2123 | -# DOXYFILE_SOURCE_DIR - Path where the Doxygen input files are. |
2124 | -# Defaults to the current source directory. |
2125 | -# DOXYFILE_EXTRA_SOURCES - Additional source diretories/files for Doxygen to scan. |
2126 | -# The Paths should be in double quotes and separated by space. e.g.: |
2127 | -# "${CMAKE_CURRENT_BINARY_DIR}/foo.c" "${CMAKE_CURRENT_BINARY_DIR}/bar/" |
2128 | -# |
2129 | -# DOXYFILE_OUTPUT_DIR - Path where the Doxygen output is stored. |
2130 | -# Defaults to "${CMAKE_CURRENT_BINARY_DIR}/doc". |
2131 | -# |
2132 | -# DOXYFILE_LATEX - ON/OFF; Set to "ON" if you want the LaTeX documentation |
2133 | -# to be built. |
2134 | -# DOXYFILE_LATEX_DIR - Directory relative to DOXYFILE_OUTPUT_DIR where |
2135 | -# the Doxygen LaTeX output is stored. Defaults to "latex". |
2136 | -# |
2137 | -# DOXYFILE_HTML_DIR - Directory relative to DOXYFILE_OUTPUT_DIR where |
2138 | -# the Doxygen html output is stored. Defaults to "html". |
2139 | -# |
2140 | - |
2141 | -# |
2142 | -# Copyright (c) 2009, 2010, 2011 Tobias Rautenkranz <tobias@rautenkranz.ch> |
2143 | -# |
2144 | -# Redistribution and use is allowed according to the terms of the New |
2145 | -# BSD license. |
2146 | -# For details see the accompanying COPYING-CMAKE-SCRIPTS file. |
2147 | -# |
2148 | - |
2149 | -option( |
2150 | - BUILD_DOXYGEN |
2151 | - "Build Doxygen documentation as part of the default build" |
2152 | - OFF |
2153 | -) |
2154 | - |
2155 | -macro(usedoxygen_set_default name value type docstring) |
2156 | - if(NOT DEFINED "${name}") |
2157 | - set("${name}" "${value}" CACHE "${type}" "${docstring}") |
2158 | - endif() |
2159 | -endmacro() |
2160 | - |
2161 | -find_package(Doxygen) |
2162 | - |
2163 | -if(DOXYGEN_FOUND) |
2164 | - find_file(DOXYFILE_IN "Doxyfile.in" |
2165 | - PATHS ${CMAKE_MODULE_PATH} "${CMAKE_ROOT}/Modules/" |
2166 | - NO_DEFAULT_PATH |
2167 | - DOC "Path to the doxygen configuration template file") |
2168 | - set(DOXYFILE "${CMAKE_CURRENT_BINARY_DIR}/Doxyfile") |
2169 | - include(FindPackageHandleStandardArgs) |
2170 | - find_package_handle_standard_args(DOXYFILE_IN DEFAULT_MSG "DOXYFILE_IN") |
2171 | -endif() |
2172 | - |
2173 | -if(DOXYGEN_FOUND AND DOXYFILE_IN_FOUND) |
2174 | - usedoxygen_set_default(DOXYFILE_OUTPUT_DIR "${CMAKE_CURRENT_BINARY_DIR}/doc" |
2175 | - PATH "Doxygen output directory") |
2176 | - usedoxygen_set_default(DOXYFILE_HTML_DIR "html" |
2177 | - STRING "Doxygen HTML output directory") |
2178 | - usedoxygen_set_default(DOXYFILE_SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}" |
2179 | - PATH "Input files source directory") |
2180 | - usedoxygen_set_default(DOXYFILE_EXTRA_SOURCE_DIRS "" |
2181 | - STRING "Additional source files/directories separated by space") |
2182 | - set(DOXYFILE_SOURCE_DIRS "\"${DOXYFILE_SOURCE_DIR}\" ${DOXYFILE_EXTRA_SOURCES}") |
2183 | - |
2184 | - usedoxygen_set_default(DOXYFILE_LATEX YES BOOL "Generate LaTeX API documentation" OFF) |
2185 | - usedoxygen_set_default(DOXYFILE_LATEX_DIR "latex" STRING "LaTex output directory") |
2186 | - |
2187 | - mark_as_advanced(DOXYFILE_OUTPUT_DIR DOXYFILE_HTML_DIR DOXYFILE_LATEX_DIR |
2188 | - DOXYFILE_SOURCE_DIR DOXYFILE_EXTRA_SOURCE_DIRS DOXYFILE_IN) |
2189 | - |
2190 | - |
2191 | - set_property(DIRECTORY |
2192 | - APPEND PROPERTY |
2193 | - ADDITIONAL_MAKE_CLEAN_FILES |
2194 | - "${DOXYFILE_OUTPUT_DIR}/${DOXYFILE_HTML_DIR}") |
2195 | - |
2196 | - add_custom_target(doxygen |
2197 | - COMMAND "${DOXYGEN_EXECUTABLE}" |
2198 | - "${DOXYFILE}" |
2199 | - COMMENT "Writing documentation to ${DOXYFILE_OUTPUT_DIR}..." |
2200 | - WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}") |
2201 | - |
2202 | - set(DOXYFILE_DOT "NO") |
2203 | - if(DOXYGEN_DOT_EXECUTABLE) |
2204 | - set(DOXYFILE_DOT "YES") |
2205 | - endif() |
2206 | - |
2207 | - ## LaTeX |
2208 | - set(DOXYFILE_PDFLATEX "NO") |
2209 | - |
2210 | - set_property(DIRECTORY APPEND PROPERTY |
2211 | - ADDITIONAL_MAKE_CLEAN_FILES |
2212 | - "${DOXYFILE_OUTPUT_DIR}/${DOXYFILE_LATEX_DIR}") |
2213 | - |
2214 | - if(DOXYFILE_LATEX STREQUAL "ON") |
2215 | - set(DOXYFILE_GENERATE_LATEX "YES") |
2216 | - find_package(LATEX) |
2217 | - find_program(DOXYFILE_MAKE make) |
2218 | - mark_as_advanced(DOXYFILE_MAKE) |
2219 | - if(LATEX_COMPILER AND MAKEINDEX_COMPILER AND DOXYFILE_MAKE) |
2220 | - if(PDFLATEX_COMPILER) |
2221 | - set(DOXYFILE_PDFLATEX "YES") |
2222 | - endif() |
2223 | - |
2224 | - add_custom_command(TARGET doxygen |
2225 | - POST_BUILD |
2226 | - COMMAND "${DOXYFILE_MAKE}" |
2227 | - COMMENT "Running LaTeX for Doxygen documentation in ${DOXYFILE_OUTPUT_DIR}/${DOXYFILE_LATEX_DIR}..." |
2228 | - WORKING_DIRECTORY "${DOXYFILE_OUTPUT_DIR}/${DOXYFILE_LATEX_DIR}") |
2229 | - else() |
2230 | - set(DOXYGEN_LATEX "NO") |
2231 | - endif() |
2232 | - else() |
2233 | - set(DOXYFILE_GENERATE_LATEX "NO") |
2234 | - endif() |
2235 | - |
2236 | - |
2237 | - configure_file("${DOXYFILE_IN}" "${DOXYFILE}" @ONLY) |
2238 | - |
2239 | - if (BUILD_DOXYGEN) |
2240 | - set(ALL "ALL") |
2241 | - endif() |
2242 | - |
2243 | - get_target_property(DOC_TARGET doc TYPE) |
2244 | - if(NOT DOC_TARGET) |
2245 | - add_custom_target(doc ${ALL}) |
2246 | - endif() |
2247 | - |
2248 | - add_dependencies(doc doxygen) |
2249 | -endif() |
2250 | |
2251 | === removed file 'cmake/UseGSettings.cmake' |
2252 | --- cmake/UseGSettings.cmake 2013-09-20 12:20:49 +0000 |
2253 | +++ cmake/UseGSettings.cmake 1970-01-01 00:00:00 +0000 |
2254 | @@ -1,29 +0,0 @@ |
2255 | -# GSettings.cmake, CMake macros written for Marlin, feel free to re-use them. |
2256 | - |
2257 | -option (GSETTINGS_COMPILE "Compile GSettings Schemas after installation" ${GSETTINGS_LOCALINSTALL}) |
2258 | - |
2259 | -if(GSETTINGS_COMPILE) |
2260 | - message(STATUS "GSettings schemas will be compiled.") |
2261 | -endif() |
2262 | - |
2263 | -macro(add_schema SCHEMA_NAME) |
2264 | - set(PKG_CONFIG_EXECUTABLE pkg-config) |
2265 | - SET (GSETTINGS_DIR "${CMAKE_INSTALL_PREFIX}/share/glib-2.0/schemas/") |
2266 | - |
2267 | - # Run the validator and error if it fails |
2268 | - execute_process (COMMAND ${PKG_CONFIG_EXECUTABLE} gio-2.0 --variable glib_compile_schemas OUTPUT_VARIABLE _glib_comple_schemas OUTPUT_STRIP_TRAILING_WHITESPACE) |
2269 | - execute_process (COMMAND ${_glib_comple_schemas} --dry-run --schema-file=${CMAKE_CURRENT_SOURCE_DIR}/${SCHEMA_NAME} ERROR_VARIABLE _schemas_invalid OUTPUT_STRIP_TRAILING_WHITESPACE) |
2270 | - |
2271 | - if (_schemas_invalid) |
2272 | - message (SEND_ERROR "Schema validation error: ${_schemas_invalid}") |
2273 | - endif (_schemas_invalid) |
2274 | - |
2275 | - # Actually install and recomple schemas |
2276 | - message (STATUS "GSettings schemas will be installed into ${GSETTINGS_DIR}") |
2277 | - install (FILES ${CMAKE_CURRENT_SOURCE_DIR}/${SCHEMA_NAME} DESTINATION ${GSETTINGS_DIR} OPTIONAL) |
2278 | - |
2279 | - if (GSETTINGS_COMPILE) |
2280 | - install (CODE "message (STATUS \"Compiling GSettings schemas\")") |
2281 | - install (CODE "execute_process (COMMAND ${_glib_comple_schemas} ${GSETTINGS_DIR})") |
2282 | - endif () |
2283 | -endmacro() |
2284 | |
2285 | === modified file 'data/CMakeLists.txt' |
2286 | --- data/CMakeLists.txt 2013-10-22 16:59:17 +0000 |
2287 | +++ data/CMakeLists.txt 2016-12-08 10:49:24 +0000 |
2288 | @@ -1,4 +1,4 @@ |
2289 | -include("UseGSettings") |
2290 | +find_package(GSettings) |
2291 | |
2292 | ########################### |
2293 | # Settings |
2294 | |
2295 | === modified file 'debian/control' |
2296 | --- debian/control 2015-01-29 12:37:39 +0000 |
2297 | +++ debian/control 2016-12-08 10:49:24 +0000 |
2298 | @@ -2,12 +2,14 @@ |
2299 | Priority: optional |
2300 | Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
2301 | Build-Depends: cmake, |
2302 | - cmake-extras (>= 0.2), |
2303 | + cmake-extras (>= 0.10), |
2304 | dbus, |
2305 | debhelper (>= 9), |
2306 | doxygen, |
2307 | - gettext, |
2308 | + gcovr, |
2309 | google-mock (>= 1.6.0+svn437), |
2310 | + intltool, |
2311 | + lcov, |
2312 | libapparmor-dev, |
2313 | libclick-0.4-dev, |
2314 | libgsettings-qt-dev, |
2315 | @@ -19,7 +21,6 @@ |
2316 | pkg-config, |
2317 | qtbase5-dev, |
2318 | sqlite3, |
2319 | - valgrind [!arm64 !powerpc !ppc64el], |
2320 | qtdeclarative5-dev, |
2321 | qtdeclarative5-qtquick2-plugin, |
2322 | qtdeclarative5-test-plugin, |
2323 | |
2324 | === modified file 'debian/rules' |
2325 | --- debian/rules 2016-08-08 13:51:10 +0000 |
2326 | +++ debian/rules 2016-12-08 10:49:24 +0000 |
2327 | @@ -15,5 +15,5 @@ |
2328 | dh $@ --parallel --fail-missing |
2329 | |
2330 | override_dh_auto_configure: |
2331 | - dh_auto_configure -- -DBUILD_DOXYGEN=YES -DENABLE_TESTS=${ENABLE_TESTS} |
2332 | + dh_auto_configure -- -DENABLE_TESTS=${ENABLE_TESTS} |
2333 | |
2334 | |
2335 | === added file 'doc/CMakeLists.txt' |
2336 | --- doc/CMakeLists.txt 1970-01-01 00:00:00 +0000 |
2337 | +++ doc/CMakeLists.txt 2016-12-08 10:49:24 +0000 |
2338 | @@ -0,0 +1,26 @@ |
2339 | +find_package(DoxygenBuilder) |
2340 | + |
2341 | +add_doxygen( |
2342 | + qtdoc |
2343 | + PROJECT_NAME |
2344 | + "libusermetrics" |
2345 | + INPUT |
2346 | + "${CMAKE_SOURCE_DIR}/include" |
2347 | + "${CMAKE_CURRENT_SOURCE_DIR}/pages" |
2348 | + EXAMPLE_PATH |
2349 | + "${CMAKE_SOURCE_DIR}/examples/" |
2350 | + STRIP_FROM_PATH |
2351 | + "${CMAKE_SOURCE_DIR}/include" |
2352 | + STRIP_FROM_INC_PATH |
2353 | + "${CMAKE_SOURCE_DIR}/include" |
2354 | + EXCLUDE_PATTERNS |
2355 | + */internal/* |
2356 | + EXCLUDE_SYMBOLS |
2357 | + *::internal* |
2358 | + *::Priv |
2359 | + INSTALL |
2360 | + ${CMAKE_INSTALL_DATAROOTDIR}/doc/libusermetrics-doc |
2361 | + XML |
2362 | + ALL |
2363 | +) |
2364 | + |
2365 | |
2366 | === added directory 'doc/pages' |
2367 | === renamed file 'doc/building_source.md' => 'doc/pages/building_source.md' |
2368 | === renamed file 'doc/installing_prebuilt.md' => 'doc/pages/installing_prebuilt.md' |
2369 | === renamed file 'doc/mainpage.md' => 'doc/pages/mainpage.md' |
2370 | === modified file 'po/CMakeLists.txt' |
2371 | --- po/CMakeLists.txt 2014-09-05 12:34:23 +0000 |
2372 | +++ po/CMakeLists.txt 2016-12-08 10:49:24 +0000 |
2373 | @@ -1,10 +1,13 @@ |
2374 | -include(UseXGettext) |
2375 | - |
2376 | -add_translations_directory(${GETTEXT_PACKAGE}) |
2377 | - |
2378 | -add_translations_catalog( |
2379 | +find_package(Intltool REQUIRED) |
2380 | + |
2381 | +intltool_update_potfile( |
2382 | + KEYWORDS "_" "_:1,2" "N_" "N_:1,2" |
2383 | GETTEXT_PACKAGE ${GETTEXT_PACKAGE} |
2384 | COPYRIGHT_HOLDER "Canonical Ltd." |
2385 | - SOURCE_DIRECTORIES "${CMAKE_SOURCE_DIR}/src" |
2386 | +) |
2387 | + |
2388 | +intltool_install_translations( |
2389 | + ALL |
2390 | + GETTEXT_PACKAGE ${GETTEXT_PACKAGE} |
2391 | ) |
2392 | |
2393 | |
2394 | === modified file 'tests/CMakeLists.txt' |
2395 | --- tests/CMakeLists.txt 2013-10-22 16:59:17 +0000 |
2396 | +++ tests/CMakeLists.txt 2016-12-08 10:49:24 +0000 |
2397 | @@ -1,9 +1,7 @@ |
2398 | set(CMAKE_AUTOMOC OFF) |
2399 | -include(FindGMock) |
2400 | +find_package(GMock) |
2401 | set(CMAKE_AUTOMOC ON) |
2402 | |
2403 | -find_package("Valgrind" REQUIRED) |
2404 | - |
2405 | include_directories(${CMAKE_CURRENT_SOURCE_DIR}) |
2406 | include_directories(${GMOCK_INCLUDE_DIRS}) |
2407 | include_directories(${GTEST_INCLUDE_DIRS}) |
2408 | |
2409 | === modified file 'tests/unit/libusermetricsinput/CMakeLists.txt' |
2410 | --- tests/unit/libusermetricsinput/CMakeLists.txt 2013-06-28 08:48:33 +0000 |
2411 | +++ tests/unit/libusermetricsinput/CMakeLists.txt 2016-12-08 10:49:24 +0000 |
2412 | @@ -18,7 +18,7 @@ |
2413 | ${GMOCK_LIBRARIES} |
2414 | ) |
2415 | |
2416 | -add_valgrind_test( |
2417 | +add_test( |
2418 | usermetricsinput-unit-tests |
2419 | usermetricsinput-unit-tests |
2420 | ) |
2421 | |
2422 | === modified file 'tests/unit/libusermetricsoutput/CMakeLists.txt' |
2423 | --- tests/unit/libusermetricsoutput/CMakeLists.txt 2013-09-26 09:12:58 +0000 |
2424 | +++ tests/unit/libusermetricsoutput/CMakeLists.txt 2016-12-08 10:49:24 +0000 |
2425 | @@ -24,7 +24,7 @@ |
2426 | ${GMOCK_LIBRARIES} |
2427 | ) |
2428 | |
2429 | -add_valgrind_test( |
2430 | +add_test( |
2431 | usermetricsoutput-unit-tests |
2432 | usermetricsoutput-unit-tests |
2433 | ) |
2434 | |
2435 | === modified file 'tests/unit/libusermetricsoutput/TestSyncedUserMetricsStore.cpp' |
2436 | --- tests/unit/libusermetricsoutput/TestSyncedUserMetricsStore.cpp 2014-10-15 17:12:16 +0000 |
2437 | +++ tests/unit/libusermetricsoutput/TestSyncedUserMetricsStore.cpp 2016-12-08 10:49:24 +0000 |
2438 | @@ -38,6 +38,21 @@ |
2439 | using namespace UserMetricsOutput; |
2440 | using namespace UserMetricsTestUtils; |
2441 | |
2442 | +#define WAIT_FOR_STRINGS_TO_CHANGE() {\ |
2443 | +if (dataSource->formatString().isEmpty()) { \ |
2444 | + QSignalSpy formatStringChangedSpy(dataSource.data(), SIGNAL(formatStringChanged(const QString &))); \ |
2445 | + ASSERT_TRUE(formatStringChangedSpy.wait()); \ |
2446 | +} \ |
2447 | +if (dataSource->emptyDataString().isEmpty()) { \ |
2448 | + QSignalSpy emptyDataStringChangedSpy(dataSource.data(), SIGNAL(emptyDataStringChanged(const QString &))); \ |
2449 | + ASSERT_TRUE(emptyDataStringChangedSpy.wait()); \ |
2450 | +} \ |
2451 | +if (dataSource->textDomain().isEmpty()) { \ |
2452 | + QSignalSpy textDomainChangedSpy(dataSource.data(), SIGNAL(textDomainChanged(const QString &))); \ |
2453 | + ASSERT_TRUE(textDomainChangedSpy.wait()); \ |
2454 | +} \ |
2455 | +} |
2456 | + |
2457 | namespace { |
2458 | |
2459 | class TestSyncedUserMetricsStore: public DBusTest { |
2460 | @@ -73,9 +88,7 @@ |
2461 | { |
2462 | DataSourcePtr dataSource(store.dataSource(DBusPaths::dataSource(1))); |
2463 | ASSERT_FALSE(dataSource.isNull()); |
2464 | - QSignalSpy emptyDataStringChangedSpy(dataSource.data(), |
2465 | - SIGNAL(emptyDataStringChanged(const QString &))); |
2466 | - ASSERT_TRUE(emptyDataStringChangedSpy.wait()); |
2467 | + WAIT_FOR_STRINGS_TO_CHANGE(); |
2468 | EXPECT_EQ(QString("format string one %1"), dataSource->formatString()); |
2469 | EXPECT_EQ(QString("empty data string one"), |
2470 | dataSource->emptyDataString()); |
2471 | @@ -85,9 +98,7 @@ |
2472 | { |
2473 | DataSourcePtr dataSource(store.dataSource(DBusPaths::dataSource(2))); |
2474 | ASSERT_FALSE(dataSource.isNull()); |
2475 | - QSignalSpy emptyDataStringChangedSpy(dataSource.data(), |
2476 | - SIGNAL(emptyDataStringChanged(const QString &))); |
2477 | - ASSERT_TRUE(emptyDataStringChangedSpy.wait()); |
2478 | + WAIT_FOR_STRINGS_TO_CHANGE(); |
2479 | EXPECT_EQ(QString("format string two %1"), dataSource->formatString()); |
2480 | EXPECT_EQ(QString("empty data string two"), |
2481 | dataSource->emptyDataString()); |
2482 | @@ -113,9 +124,7 @@ |
2483 | { |
2484 | DataSourcePtr dataSource(store.dataSource(DBusPaths::dataSource(1))); |
2485 | ASSERT_FALSE(dataSource.isNull()); |
2486 | - QSignalSpy formatStringChangedSpy(dataSource.data(), |
2487 | - SIGNAL(formatStringChanged(const QString &))); |
2488 | - ASSERT_TRUE(formatStringChangedSpy.wait()); |
2489 | + WAIT_FOR_STRINGS_TO_CHANGE(); |
2490 | EXPECT_EQ(QString("format string one %1"), dataSource->formatString()); |
2491 | EXPECT_EQ(QString("text-domain-one"), dataSource->textDomain()); |
2492 | } |
2493 | @@ -139,11 +148,7 @@ |
2494 | { |
2495 | DataSourcePtr dataSource(store.dataSource(DBusPaths::dataSource(1))); |
2496 | ASSERT_FALSE(dataSource.isNull()); |
2497 | - if (dataSource->emptyDataString().isEmpty()) { |
2498 | - QSignalSpy emptyDataStringChangedSpy(dataSource.data(), |
2499 | - SIGNAL(emptyDataStringChanged(const QString &))); |
2500 | - ASSERT_TRUE(emptyDataStringChangedSpy.wait()); |
2501 | - } |
2502 | + WAIT_FOR_STRINGS_TO_CHANGE(); |
2503 | EXPECT_EQ(QString("format string one %1"), dataSource->formatString()); |
2504 | EXPECT_EQ(QString("no data source ones"), |
2505 | dataSource->emptyDataString()); |
2506 | @@ -153,9 +158,7 @@ |
2507 | { |
2508 | DataSourcePtr dataSource(store.dataSource(DBusPaths::dataSource(2))); |
2509 | ASSERT_FALSE(dataSource.isNull()); |
2510 | - QSignalSpy emptyDataStringChangedSpy(dataSource.data(), |
2511 | - SIGNAL(emptyDataStringChanged(const QString &))); |
2512 | - ASSERT_TRUE(emptyDataStringChangedSpy.wait()); |
2513 | + WAIT_FOR_STRINGS_TO_CHANGE(); |
2514 | EXPECT_EQ(QString("format string two %1"), dataSource->formatString()); |
2515 | EXPECT_EQ(QString("no data source twos"), |
2516 | dataSource->emptyDataString()); |
2517 | |
2518 | === modified file 'tests/unit/usermetricsservice/CMakeLists.txt' |
2519 | --- tests/unit/usermetricsservice/CMakeLists.txt 2013-10-01 10:22:38 +0000 |
2520 | +++ tests/unit/usermetricsservice/CMakeLists.txt 2016-12-08 10:49:24 +0000 |
2521 | @@ -19,7 +19,7 @@ |
2522 | ${GMOCK_LIBRARIES} |
2523 | ) |
2524 | |
2525 | -add_valgrind_test( |
2526 | +add_test( |
2527 | usermetricsservice-unit-tests |
2528 | usermetricsservice-unit-tests |
2529 | ) |
Does the coverage report still work with this change?
The cmake/Coverage. cmake file looks like it will unconditionally add the coverage rules if CMAKE_BUILD_ TYPE=coverage once it is included.
With find_package( CoverageReport) , it is also necessary to call enable_ coverage_ report( ), telling it about the coverage targets, test targets, and directories to exclude from the report.