Commit 00f1226575c39b2b31e2164748c4e427dfd92b46
Exists in
master
and in
1 other branch
Merge branch 'dev' of bizet.dis.ulpgc.es:ediaz/heisenwave into dev
Showing
9 changed files
with
2054 additions
and
24 deletions
Show diff stats
app/CMakeLists.txt
... | ... | @@ -0,0 +1,29 @@ |
1 | + | |
2 | +if (NOT EXISTS "/home/quique/Documents/14-15/SETR/Craft/deps/glfw/install_manifest.txt") | |
3 | + message(FATAL_ERROR "Cannot find install manifest: \"/home/quique/Documents/14-15/SETR/Craft/deps/glfw/install_manifest.txt\"") | |
4 | +endif() | |
5 | + | |
6 | +file(READ "/home/quique/Documents/14-15/SETR/Craft/deps/glfw/install_manifest.txt" files) | |
7 | +string(REGEX REPLACE "\n" ";" files "${files}") | |
8 | + | |
9 | +foreach (file ${files}) | |
10 | + message(STATUS "Uninstalling \"$ENV{DESTDIR}${file}\"") | |
11 | + if (EXISTS "$ENV{DESTDIR}${file}") | |
12 | + exec_program("/usr/bin/cmake" ARGS "-E remove \"$ENV{DESTDIR}${file}\"" | |
13 | + OUTPUT_VARIABLE rm_out | |
14 | + RETURN_VALUE rm_retval) | |
15 | + if (NOT "${rm_retval}" STREQUAL 0) | |
16 | + MESSAGE(FATAL_ERROR "Problem when removing \"$ENV{DESTDIR}${file}\"") | |
17 | + endif() | |
18 | + elseif (IS_SYMLINK "$ENV{DESTDIR}${file}") | |
19 | + EXEC_PROGRAM("/usr/bin/cmake" ARGS "-E remove \"$ENV{DESTDIR}${file}\"" | |
20 | + OUTPUT_VARIABLE rm_out | |
21 | + RETURN_VALUE rm_retval) | |
22 | + if (NOT "${rm_retval}" STREQUAL 0) | |
23 | + message(FATAL_ERROR "Problem when removing symlink \"$ENV{DESTDIR}${file}\"") | |
24 | + endif() | |
25 | + else() | |
26 | + message(STATUS "File \"$ENV{DESTDIR}${file}\" does not exist.") | |
27 | + endif() | |
28 | +endforeach() | |
29 | + | ... | ... |
... | ... | @@ -0,0 +1,1871 @@ |
1 | +# Doxyfile 1.8.3.1 | |
2 | + | |
3 | +# This file describes the settings to be used by the documentation system | |
4 | +# doxygen (www.doxygen.org) for a project. | |
5 | +# | |
6 | +# All text after a hash (#) is considered a comment and will be ignored. | |
7 | +# The format is: | |
8 | +# TAG = value [value, ...] | |
9 | +# For lists items can also be appended using: | |
10 | +# TAG += value [value, ...] | |
11 | +# Values that contain spaces should be placed between quotes (" "). | |
12 | + | |
13 | +#--------------------------------------------------------------------------- | |
14 | +# Project related configuration options | |
15 | +#--------------------------------------------------------------------------- | |
16 | + | |
17 | +# This tag specifies the encoding used for all characters in the config file | |
18 | +# that follow. The default is UTF-8 which is also the encoding used for all | |
19 | +# text before the first occurrence of this tag. Doxygen uses libiconv (or the | |
20 | +# iconv built into libc) for the transcoding. See | |
21 | +# http://www.gnu.org/software/libiconv for the list of possible encodings. | |
22 | + | |
23 | +DOXYFILE_ENCODING = UTF-8 | |
24 | + | |
25 | +# The PROJECT_NAME tag is a single word (or sequence of words) that should | |
26 | +# identify the project. Note that if you do not use Doxywizard you need | |
27 | +# to put quotes around the project name if it contains spaces. | |
28 | + | |
29 | +PROJECT_NAME = "GLFW" | |
30 | + | |
31 | +# The PROJECT_NUMBER tag can be used to enter a project or revision number. | |
32 | +# This could be handy for archiving the generated documentation or | |
33 | +# if some version control system is used. | |
34 | + | |
35 | +PROJECT_NUMBER = 3.0.3 | |
36 | + | |
37 | +# Using the PROJECT_BRIEF tag one can provide an optional one line description | |
38 | +# for a project that appears at the top of each page and should give viewer | |
39 | +# a quick idea about the purpose of the project. Keep the description short. | |
40 | + | |
41 | +PROJECT_BRIEF = "A multi-platform library for OpenGL, window and input" | |
42 | + | |
43 | +# With the PROJECT_LOGO tag one can specify an logo or icon that is | |
44 | +# included in the documentation. The maximum height of the logo should not | |
45 | +# exceed 55 pixels and the maximum width should not exceed 200 pixels. | |
46 | +# Doxygen will copy the logo to the output directory. | |
47 | + | |
48 | +PROJECT_LOGO = | |
49 | + | |
50 | +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) | |
51 | +# base path where the generated documentation will be put. | |
52 | +# If a relative path is entered, it will be relative to the location | |
53 | +# where doxygen was started. If left blank the current directory will be used. | |
54 | + | |
55 | +OUTPUT_DIRECTORY = /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs | |
56 | + | |
57 | +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create | |
58 | +# 4096 sub-directories (in 2 levels) under the output directory of each output | |
59 | +# format and will distribute the generated files over these directories. | |
60 | +# Enabling this option can be useful when feeding doxygen a huge amount of | |
61 | +# source files, where putting all generated files in the same directory would | |
62 | +# otherwise cause performance problems for the file system. | |
63 | + | |
64 | +CREATE_SUBDIRS = NO | |
65 | + | |
66 | +# The OUTPUT_LANGUAGE tag is used to specify the language in which all | |
67 | +# documentation generated by doxygen is written. Doxygen will use this | |
68 | +# information to generate all constant output in the proper language. | |
69 | +# The default language is English, other supported languages are: | |
70 | +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, | |
71 | +# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, | |
72 | +# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English | |
73 | +# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, | |
74 | +# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, | |
75 | +# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. | |
76 | + | |
77 | +OUTPUT_LANGUAGE = English | |
78 | + | |
79 | +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will | |
80 | +# include brief member descriptions after the members that are listed in | |
81 | +# the file and class documentation (similar to JavaDoc). | |
82 | +# Set to NO to disable this. | |
83 | + | |
84 | +BRIEF_MEMBER_DESC = YES | |
85 | + | |
86 | +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend | |
87 | +# the brief description of a member or function before the detailed description. | |
88 | +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the | |
89 | +# brief descriptions will be completely suppressed. | |
90 | + | |
91 | +REPEAT_BRIEF = NO | |
92 | + | |
93 | +# This tag implements a quasi-intelligent brief description abbreviator | |
94 | +# that is used to form the text in various listings. Each string | |
95 | +# in this list, if found as the leading text of the brief description, will be | |
96 | +# stripped from the text and the result after processing the whole list, is | |
97 | +# used as the annotated text. Otherwise, the brief description is used as-is. | |
98 | +# If left blank, the following values are used ("$name" is automatically | |
99 | +# replaced with the name of the entity): "The $name class" "The $name widget" | |
100 | +# "The $name file" "is" "provides" "specifies" "contains" | |
101 | +# "represents" "a" "an" "the" | |
102 | + | |
103 | +ABBREVIATE_BRIEF = | |
104 | + | |
105 | +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then | |
106 | +# Doxygen will generate a detailed section even if there is only a brief | |
107 | +# description. | |
108 | + | |
109 | +ALWAYS_DETAILED_SEC = YES | |
110 | + | |
111 | +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all | |
112 | +# inherited members of a class in the documentation of that class as if those | |
113 | +# members were ordinary class members. Constructors, destructors and assignment | |
114 | +# operators of the base classes will not be shown. | |
115 | + | |
116 | +INLINE_INHERITED_MEMB = NO | |
117 | + | |
118 | +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full | |
119 | +# path before files name in the file list and in the header files. If set | |
120 | +# to NO the shortest path that makes the file name unique will be used. | |
121 | + | |
122 | +FULL_PATH_NAMES = NO | |
123 | + | |
124 | +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag | |
125 | +# can be used to strip a user-defined part of the path. Stripping is | |
126 | +# only done if one of the specified strings matches the left-hand part of | |
127 | +# the path. The tag can be used to show relative paths in the file list. | |
128 | +# If left blank the directory from which doxygen is run is used as the | |
129 | +# path to strip. Note that you specify absolute paths here, but also | |
130 | +# relative paths, which will be relative from the directory where doxygen is | |
131 | +# started. | |
132 | + | |
133 | +STRIP_FROM_PATH = | |
134 | + | |
135 | +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of | |
136 | +# the path mentioned in the documentation of a class, which tells | |
137 | +# the reader which header file to include in order to use a class. | |
138 | +# If left blank only the name of the header file containing the class | |
139 | +# definition is used. Otherwise one should specify the include paths that | |
140 | +# are normally passed to the compiler using the -I flag. | |
141 | + | |
142 | +STRIP_FROM_INC_PATH = | |
143 | + | |
144 | +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter | |
145 | +# (but less readable) file names. This can be useful if your file system | |
146 | +# doesn't support long names like on DOS, Mac, or CD-ROM. | |
147 | + | |
148 | +SHORT_NAMES = NO | |
149 | + | |
150 | +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen | |
151 | +# will interpret the first line (until the first dot) of a JavaDoc-style | |
152 | +# comment as the brief description. If set to NO, the JavaDoc | |
153 | +# comments will behave just like regular Qt-style comments | |
154 | +# (thus requiring an explicit @brief command for a brief description.) | |
155 | + | |
156 | +JAVADOC_AUTOBRIEF = NO | |
157 | + | |
158 | +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will | |
159 | +# interpret the first line (until the first dot) of a Qt-style | |
160 | +# comment as the brief description. If set to NO, the comments | |
161 | +# will behave just like regular Qt-style comments (thus requiring | |
162 | +# an explicit \brief command for a brief description.) | |
163 | + | |
164 | +QT_AUTOBRIEF = NO | |
165 | + | |
166 | +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen | |
167 | +# treat a multi-line C++ special comment block (i.e. a block of //! or /// | |
168 | +# comments) as a brief description. This used to be the default behaviour. | |
169 | +# The new default is to treat a multi-line C++ comment block as a detailed | |
170 | +# description. Set this tag to YES if you prefer the old behaviour instead. | |
171 | + | |
172 | +MULTILINE_CPP_IS_BRIEF = NO | |
173 | + | |
174 | +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented | |
175 | +# member inherits the documentation from any documented member that it | |
176 | +# re-implements. | |
177 | + | |
178 | +INHERIT_DOCS = YES | |
179 | + | |
180 | +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce | |
181 | +# a new page for each member. If set to NO, the documentation of a member will | |
182 | +# be part of the file/class/namespace that contains it. | |
183 | + | |
184 | +SEPARATE_MEMBER_PAGES = NO | |
185 | + | |
186 | +# The TAB_SIZE tag can be used to set the number of spaces in a tab. | |
187 | +# Doxygen uses this value to replace tabs by spaces in code fragments. | |
188 | + | |
189 | +TAB_SIZE = 8 | |
190 | + | |
191 | +# This tag can be used to specify a number of aliases that acts | |
192 | +# as commands in the documentation. An alias has the form "name=value". | |
193 | +# For example adding "sideeffect=\par Side Effects:\n" will allow you to | |
194 | +# put the command \sideeffect (or @sideeffect) in the documentation, which | |
195 | +# will result in a user-defined paragraph with heading "Side Effects:". | |
196 | +# You can put \n's in the value part of an alias to insert newlines. | |
197 | + | |
198 | +ALIASES = | |
199 | + | |
200 | +# This tag can be used to specify a number of word-keyword mappings (TCL only). | |
201 | +# A mapping has the form "name=value". For example adding | |
202 | +# "class=itcl::class" will allow you to use the command class in the | |
203 | +# itcl::class meaning. | |
204 | + | |
205 | +TCL_SUBST = | |
206 | + | |
207 | +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C | |
208 | +# sources only. Doxygen will then generate output that is more tailored for C. | |
209 | +# For instance, some of the names that are used will be different. The list | |
210 | +# of all members will be omitted, etc. | |
211 | + | |
212 | +OPTIMIZE_OUTPUT_FOR_C = YES | |
213 | + | |
214 | +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java | |
215 | +# sources only. Doxygen will then generate output that is more tailored for | |
216 | +# Java. For instance, namespaces will be presented as packages, qualified | |
217 | +# scopes will look different, etc. | |
218 | + | |
219 | +OPTIMIZE_OUTPUT_JAVA = NO | |
220 | + | |
221 | +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran | |
222 | +# sources only. Doxygen will then generate output that is more tailored for | |
223 | +# Fortran. | |
224 | + | |
225 | +OPTIMIZE_FOR_FORTRAN = NO | |
226 | + | |
227 | +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL | |
228 | +# sources. Doxygen will then generate output that is tailored for | |
229 | +# VHDL. | |
230 | + | |
231 | +OPTIMIZE_OUTPUT_VHDL = NO | |
232 | + | |
233 | +# Doxygen selects the parser to use depending on the extension of the files it | |
234 | +# parses. With this tag you can assign which parser to use for a given | |
235 | +# extension. Doxygen has a built-in mapping, but you can override or extend it | |
236 | +# using this tag. The format is ext=language, where ext is a file extension, | |
237 | +# and language is one of the parsers supported by doxygen: IDL, Java, | |
238 | +# Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | |
239 | +# C++. For instance to make doxygen treat .inc files as Fortran files (default | |
240 | +# is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note | |
241 | +# that for custom extensions you also need to set FILE_PATTERNS otherwise the | |
242 | +# files are not read by doxygen. | |
243 | + | |
244 | +EXTENSION_MAPPING = | |
245 | + | |
246 | +# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all | |
247 | +# comments according to the Markdown format, which allows for more readable | |
248 | +# documentation. See http://daringfireball.net/projects/markdown/ for details. | |
249 | +# The output of markdown processing is further processed by doxygen, so you | |
250 | +# can mix doxygen, HTML, and XML commands with Markdown formatting. | |
251 | +# Disable only in case of backward compatibilities issues. | |
252 | + | |
253 | +MARKDOWN_SUPPORT = YES | |
254 | + | |
255 | +# When enabled doxygen tries to link words that correspond to documented classes, | |
256 | +# or namespaces to their corresponding documentation. Such a link can be | |
257 | +# prevented in individual cases by by putting a % sign in front of the word or | |
258 | +# globally by setting AUTOLINK_SUPPORT to NO. | |
259 | + | |
260 | +AUTOLINK_SUPPORT = YES | |
261 | + | |
262 | +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | |
263 | +# to include (a tag file for) the STL sources as input, then you should | |
264 | +# set this tag to YES in order to let doxygen match functions declarations and | |
265 | +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. | |
266 | +# func(std::string) {}). This also makes the inheritance and collaboration | |
267 | +# diagrams that involve STL classes more complete and accurate. | |
268 | + | |
269 | +BUILTIN_STL_SUPPORT = NO | |
270 | + | |
271 | +# If you use Microsoft's C++/CLI language, you should set this option to YES to | |
272 | +# enable parsing support. | |
273 | + | |
274 | +CPP_CLI_SUPPORT = NO | |
275 | + | |
276 | +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. | |
277 | +# Doxygen will parse them like normal C++ but will assume all classes use public | |
278 | +# instead of private inheritance when no explicit protection keyword is present. | |
279 | + | |
280 | +SIP_SUPPORT = NO | |
281 | + | |
282 | +# For Microsoft's IDL there are propget and propput attributes to indicate | |
283 | +# getter and setter methods for a property. Setting this option to YES (the | |
284 | +# default) will make doxygen replace the get and set methods by a property in | |
285 | +# the documentation. This will only work if the methods are indeed getting or | |
286 | +# setting a simple type. If this is not the case, or you want to show the | |
287 | +# methods anyway, you should set this option to NO. | |
288 | + | |
289 | +IDL_PROPERTY_SUPPORT = NO | |
290 | + | |
291 | +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC | |
292 | +# tag is set to YES, then doxygen will reuse the documentation of the first | |
293 | +# member in the group (if any) for the other members of the group. By default | |
294 | +# all members of a group must be documented explicitly. | |
295 | + | |
296 | +DISTRIBUTE_GROUP_DOC = NO | |
297 | + | |
298 | +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of | |
299 | +# the same type (for instance a group of public functions) to be put as a | |
300 | +# subgroup of that type (e.g. under the Public Functions section). Set it to | |
301 | +# NO to prevent subgrouping. Alternatively, this can be done per class using | |
302 | +# the \nosubgrouping command. | |
303 | + | |
304 | +SUBGROUPING = YES | |
305 | + | |
306 | +# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and | |
307 | +# unions are shown inside the group in which they are included (e.g. using | |
308 | +# @ingroup) instead of on a separate page (for HTML and Man pages) or | |
309 | +# section (for LaTeX and RTF). | |
310 | + | |
311 | +INLINE_GROUPED_CLASSES = NO | |
312 | + | |
313 | +# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and | |
314 | +# unions with only public data fields will be shown inline in the documentation | |
315 | +# of the scope in which they are defined (i.e. file, namespace, or group | |
316 | +# documentation), provided this scope is documented. If set to NO (the default), | |
317 | +# structs, classes, and unions are shown on a separate page (for HTML and Man | |
318 | +# pages) or section (for LaTeX and RTF). | |
319 | + | |
320 | +INLINE_SIMPLE_STRUCTS = NO | |
321 | + | |
322 | +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum | |
323 | +# is documented as struct, union, or enum with the name of the typedef. So | |
324 | +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct | |
325 | +# with name TypeT. When disabled the typedef will appear as a member of a file, | |
326 | +# namespace, or class. And the struct will be named TypeS. This can typically | |
327 | +# be useful for C code in case the coding convention dictates that all compound | |
328 | +# types are typedef'ed and only the typedef is referenced, never the tag name. | |
329 | + | |
330 | +TYPEDEF_HIDES_STRUCT = NO | |
331 | + | |
332 | +# Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be | |
333 | +# set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given | |
334 | +# their name and scope. Since this can be an expensive process and often the | |
335 | +# same symbol appear multiple times in the code, doxygen keeps a cache of | |
336 | +# pre-resolved symbols. If the cache is too small doxygen will become slower. | |
337 | +# If the cache is too large, memory is wasted. The cache size is given by this | |
338 | +# formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0, | |
339 | +# corresponding to a cache size of 2^16 = 65536 symbols. | |
340 | + | |
341 | +LOOKUP_CACHE_SIZE = 0 | |
342 | + | |
343 | +#--------------------------------------------------------------------------- | |
344 | +# Build related configuration options | |
345 | +#--------------------------------------------------------------------------- | |
346 | + | |
347 | +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in | |
348 | +# documentation are documented, even if no documentation was available. | |
349 | +# Private class members and static file members will be hidden unless | |
350 | +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES | |
351 | + | |
352 | +EXTRACT_ALL = YES | |
353 | + | |
354 | +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class | |
355 | +# will be included in the documentation. | |
356 | + | |
357 | +EXTRACT_PRIVATE = NO | |
358 | + | |
359 | +# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | |
360 | +# scope will be included in the documentation. | |
361 | + | |
362 | +EXTRACT_PACKAGE = NO | |
363 | + | |
364 | +# If the EXTRACT_STATIC tag is set to YES all static members of a file | |
365 | +# will be included in the documentation. | |
366 | + | |
367 | +EXTRACT_STATIC = NO | |
368 | + | |
369 | +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) | |
370 | +# defined locally in source files will be included in the documentation. | |
371 | +# If set to NO only classes defined in header files are included. | |
372 | + | |
373 | +EXTRACT_LOCAL_CLASSES = YES | |
374 | + | |
375 | +# This flag is only useful for Objective-C code. When set to YES local | |
376 | +# methods, which are defined in the implementation section but not in | |
377 | +# the interface are included in the documentation. | |
378 | +# If set to NO (the default) only methods in the interface are included. | |
379 | + | |
380 | +EXTRACT_LOCAL_METHODS = NO | |
381 | + | |
382 | +# If this flag is set to YES, the members of anonymous namespaces will be | |
383 | +# extracted and appear in the documentation as a namespace called | |
384 | +# 'anonymous_namespace{file}', where file will be replaced with the base | |
385 | +# name of the file that contains the anonymous namespace. By default | |
386 | +# anonymous namespaces are hidden. | |
387 | + | |
388 | +EXTRACT_ANON_NSPACES = NO | |
389 | + | |
390 | +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all | |
391 | +# undocumented members of documented classes, files or namespaces. | |
392 | +# If set to NO (the default) these members will be included in the | |
393 | +# various overviews, but no documentation section is generated. | |
394 | +# This option has no effect if EXTRACT_ALL is enabled. | |
395 | + | |
396 | +HIDE_UNDOC_MEMBERS = NO | |
397 | + | |
398 | +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all | |
399 | +# undocumented classes that are normally visible in the class hierarchy. | |
400 | +# If set to NO (the default) these classes will be included in the various | |
401 | +# overviews. This option has no effect if EXTRACT_ALL is enabled. | |
402 | + | |
403 | +HIDE_UNDOC_CLASSES = NO | |
404 | + | |
405 | +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all | |
406 | +# friend (class|struct|union) declarations. | |
407 | +# If set to NO (the default) these declarations will be included in the | |
408 | +# documentation. | |
409 | + | |
410 | +HIDE_FRIEND_COMPOUNDS = NO | |
411 | + | |
412 | +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any | |
413 | +# documentation blocks found inside the body of a function. | |
414 | +# If set to NO (the default) these blocks will be appended to the | |
415 | +# function's detailed documentation block. | |
416 | + | |
417 | +HIDE_IN_BODY_DOCS = NO | |
418 | + | |
419 | +# The INTERNAL_DOCS tag determines if documentation | |
420 | +# that is typed after a \internal command is included. If the tag is set | |
421 | +# to NO (the default) then the documentation will be excluded. | |
422 | +# Set it to YES to include the internal documentation. | |
423 | + | |
424 | +INTERNAL_DOCS = NO | |
425 | + | |
426 | +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate | |
427 | +# file names in lower-case letters. If set to YES upper-case letters are also | |
428 | +# allowed. This is useful if you have classes or files whose names only differ | |
429 | +# in case and if your file system supports case sensitive file names. Windows | |
430 | +# and Mac users are advised to set this option to NO. | |
431 | + | |
432 | +CASE_SENSE_NAMES = YES | |
433 | + | |
434 | +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen | |
435 | +# will show members with their full class and namespace scopes in the | |
436 | +# documentation. If set to YES the scope will be hidden. | |
437 | + | |
438 | +HIDE_SCOPE_NAMES = NO | |
439 | + | |
440 | +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen | |
441 | +# will put a list of the files that are included by a file in the documentation | |
442 | +# of that file. | |
443 | + | |
444 | +SHOW_INCLUDE_FILES = NO | |
445 | + | |
446 | +# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen | |
447 | +# will list include files with double quotes in the documentation | |
448 | +# rather than with sharp brackets. | |
449 | + | |
450 | +FORCE_LOCAL_INCLUDES = NO | |
451 | + | |
452 | +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] | |
453 | +# is inserted in the documentation for inline members. | |
454 | + | |
455 | +INLINE_INFO = YES | |
456 | + | |
457 | +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen | |
458 | +# will sort the (detailed) documentation of file and class members | |
459 | +# alphabetically by member name. If set to NO the members will appear in | |
460 | +# declaration order. | |
461 | + | |
462 | +SORT_MEMBER_DOCS = YES | |
463 | + | |
464 | +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the | |
465 | +# brief documentation of file, namespace and class members alphabetically | |
466 | +# by member name. If set to NO (the default) the members will appear in | |
467 | +# declaration order. | |
468 | + | |
469 | +SORT_BRIEF_DOCS = NO | |
470 | + | |
471 | +# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen | |
472 | +# will sort the (brief and detailed) documentation of class members so that | |
473 | +# constructors and destructors are listed first. If set to NO (the default) | |
474 | +# the constructors will appear in the respective orders defined by | |
475 | +# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. | |
476 | +# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO | |
477 | +# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. | |
478 | + | |
479 | +SORT_MEMBERS_CTORS_1ST = NO | |
480 | + | |
481 | +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the | |
482 | +# hierarchy of group names into alphabetical order. If set to NO (the default) | |
483 | +# the group names will appear in their defined order. | |
484 | + | |
485 | +SORT_GROUP_NAMES = YES | |
486 | + | |
487 | +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be | |
488 | +# sorted by fully-qualified names, including namespaces. If set to | |
489 | +# NO (the default), the class list will be sorted only by class name, | |
490 | +# not including the namespace part. | |
491 | +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. | |
492 | +# Note: This option applies only to the class list, not to the | |
493 | +# alphabetical list. | |
494 | + | |
495 | +SORT_BY_SCOPE_NAME = NO | |
496 | + | |
497 | +# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to | |
498 | +# do proper type resolution of all parameters of a function it will reject a | |
499 | +# match between the prototype and the implementation of a member function even | |
500 | +# if there is only one candidate or it is obvious which candidate to choose | |
501 | +# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen | |
502 | +# will still accept a match between prototype and implementation in such cases. | |
503 | + | |
504 | +STRICT_PROTO_MATCHING = NO | |
505 | + | |
506 | +# The GENERATE_TODOLIST tag can be used to enable (YES) or | |
507 | +# disable (NO) the todo list. This list is created by putting \todo | |
508 | +# commands in the documentation. | |
509 | + | |
510 | +GENERATE_TODOLIST = YES | |
511 | + | |
512 | +# The GENERATE_TESTLIST tag can be used to enable (YES) or | |
513 | +# disable (NO) the test list. This list is created by putting \test | |
514 | +# commands in the documentation. | |
515 | + | |
516 | +GENERATE_TESTLIST = YES | |
517 | + | |
518 | +# The GENERATE_BUGLIST tag can be used to enable (YES) or | |
519 | +# disable (NO) the bug list. This list is created by putting \bug | |
520 | +# commands in the documentation. | |
521 | + | |
522 | +GENERATE_BUGLIST = YES | |
523 | + | |
524 | +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or | |
525 | +# disable (NO) the deprecated list. This list is created by putting | |
526 | +# \deprecated commands in the documentation. | |
527 | + | |
528 | +GENERATE_DEPRECATEDLIST= YES | |
529 | + | |
530 | +# The ENABLED_SECTIONS tag can be used to enable conditional | |
531 | +# documentation sections, marked by \if section-label ... \endif | |
532 | +# and \cond section-label ... \endcond blocks. | |
533 | + | |
534 | +ENABLED_SECTIONS = | |
535 | + | |
536 | +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines | |
537 | +# the initial value of a variable or macro consists of for it to appear in | |
538 | +# the documentation. If the initializer consists of more lines than specified | |
539 | +# here it will be hidden. Use a value of 0 to hide initializers completely. | |
540 | +# The appearance of the initializer of individual variables and macros in the | |
541 | +# documentation can be controlled using \showinitializer or \hideinitializer | |
542 | +# command in the documentation regardless of this setting. | |
543 | + | |
544 | +MAX_INITIALIZER_LINES = 30 | |
545 | + | |
546 | +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated | |
547 | +# at the bottom of the documentation of classes and structs. If set to YES the | |
548 | +# list will mention the files that were used to generate the documentation. | |
549 | + | |
550 | +SHOW_USED_FILES = YES | |
551 | + | |
552 | +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. | |
553 | +# This will remove the Files entry from the Quick Index and from the | |
554 | +# Folder Tree View (if specified). The default is YES. | |
555 | + | |
556 | +SHOW_FILES = YES | |
557 | + | |
558 | +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the | |
559 | +# Namespaces page. | |
560 | +# This will remove the Namespaces entry from the Quick Index | |
561 | +# and from the Folder Tree View (if specified). The default is YES. | |
562 | + | |
563 | +SHOW_NAMESPACES = NO | |
564 | + | |
565 | +# The FILE_VERSION_FILTER tag can be used to specify a program or script that | |
566 | +# doxygen should invoke to get the current version for each file (typically from | |
567 | +# the version control system). Doxygen will invoke the program by executing (via | |
568 | +# popen()) the command <command> <input-file>, where <command> is the value of | |
569 | +# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file | |
570 | +# provided by doxygen. Whatever the program writes to standard output | |
571 | +# is used as the file version. See the manual for examples. | |
572 | + | |
573 | +FILE_VERSION_FILTER = | |
574 | + | |
575 | +# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed | |
576 | +# by doxygen. The layout file controls the global structure of the generated | |
577 | +# output files in an output format independent way. To create the layout file | |
578 | +# that represents doxygen's defaults, run doxygen with the -l option. | |
579 | +# You can optionally specify a file name after the option, if omitted | |
580 | +# DoxygenLayout.xml will be used as the name of the layout file. | |
581 | + | |
582 | +LAYOUT_FILE = | |
583 | + | |
584 | +# The CITE_BIB_FILES tag can be used to specify one or more bib files | |
585 | +# containing the references data. This must be a list of .bib files. The | |
586 | +# .bib extension is automatically appended if omitted. Using this command | |
587 | +# requires the bibtex tool to be installed. See also | |
588 | +# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style | |
589 | +# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this | |
590 | +# feature you need bibtex and perl available in the search path. Do not use | |
591 | +# file names with spaces, bibtex cannot handle them. | |
592 | + | |
593 | +CITE_BIB_FILES = | |
594 | + | |
595 | +#--------------------------------------------------------------------------- | |
596 | +# configuration options related to warning and progress messages | |
597 | +#--------------------------------------------------------------------------- | |
598 | + | |
599 | +# The QUIET tag can be used to turn on/off the messages that are generated | |
600 | +# by doxygen. Possible values are YES and NO. If left blank NO is used. | |
601 | + | |
602 | +QUIET = YES | |
603 | + | |
604 | +# The WARNINGS tag can be used to turn on/off the warning messages that are | |
605 | +# generated by doxygen. Possible values are YES and NO. If left blank | |
606 | +# NO is used. | |
607 | + | |
608 | +WARNINGS = YES | |
609 | + | |
610 | +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings | |
611 | +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will | |
612 | +# automatically be disabled. | |
613 | + | |
614 | +WARN_IF_UNDOCUMENTED = YES | |
615 | + | |
616 | +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for | |
617 | +# potential errors in the documentation, such as not documenting some | |
618 | +# parameters in a documented function, or documenting parameters that | |
619 | +# don't exist or using markup commands wrongly. | |
620 | + | |
621 | +WARN_IF_DOC_ERROR = YES | |
622 | + | |
623 | +# The WARN_NO_PARAMDOC option can be enabled to get warnings for | |
624 | +# functions that are documented, but have no documentation for their parameters | |
625 | +# or return value. If set to NO (the default) doxygen will only warn about | |
626 | +# wrong or incomplete parameter documentation, but not about the absence of | |
627 | +# documentation. | |
628 | + | |
629 | +WARN_NO_PARAMDOC = YES | |
630 | + | |
631 | +# The WARN_FORMAT tag determines the format of the warning messages that | |
632 | +# doxygen can produce. The string should contain the $file, $line, and $text | |
633 | +# tags, which will be replaced by the file and line number from which the | |
634 | +# warning originated and the warning text. Optionally the format may contain | |
635 | +# $version, which will be replaced by the version of the file (if it could | |
636 | +# be obtained via FILE_VERSION_FILTER) | |
637 | + | |
638 | +WARN_FORMAT = "$file:$line: $text" | |
639 | + | |
640 | +# The WARN_LOGFILE tag can be used to specify a file to which warning | |
641 | +# and error messages should be written. If left blank the output is written | |
642 | +# to stderr. | |
643 | + | |
644 | +WARN_LOGFILE = /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/warnings.txt | |
645 | + | |
646 | +#--------------------------------------------------------------------------- | |
647 | +# configuration options related to the input files | |
648 | +#--------------------------------------------------------------------------- | |
649 | + | |
650 | +# The INPUT tag can be used to specify the files and/or directories that contain | |
651 | +# documented source files. You may enter file names like "myfile.cpp" or | |
652 | +# directories like "/usr/src/myproject". Separate the files or directories | |
653 | +# with spaces. | |
654 | + | |
655 | +INPUT = \ | |
656 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/include/GLFW/glfw3.h \ | |
657 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/include/GLFW/glfw3native.h \ | |
658 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/main.dox \ | |
659 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/news.dox \ | |
660 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/quick.dox \ | |
661 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/moving.dox \ | |
662 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/build.dox \ | |
663 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/context.dox \ | |
664 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/monitor.dox \ | |
665 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/window.dox \ | |
666 | + /home/quique/Documents/14-15/SETR/Craft/deps/glfw/docs/compat.dox | |
667 | + | |
668 | +# This tag can be used to specify the character encoding of the source files | |
669 | +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is | |
670 | +# also the default input encoding. Doxygen uses libiconv (or the iconv built | |
671 | +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for | |
672 | +# the list of possible encodings. | |
673 | + | |
674 | +INPUT_ENCODING = UTF-8 | |
675 | + | |
676 | +# If the value of the INPUT tag contains directories, you can use the | |
677 | +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp | |
678 | +# and *.h) to filter out the source-files in the directories. If left | |
679 | +# blank the following patterns are tested: | |
680 | +# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh | |
681 | +# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py | |
682 | +# *.f90 *.f *.for *.vhd *.vhdl | |
683 | + | |
684 | +FILE_PATTERNS = *.h *.dox | |
685 | + | |
686 | +# The RECURSIVE tag can be used to turn specify whether or not subdirectories | |
687 | +# should be searched for input files as well. Possible values are YES and NO. | |
688 | +# If left blank NO is used. | |
689 | + | |
690 | +RECURSIVE = NO | |
691 | + | |
692 | +# The EXCLUDE tag can be used to specify files and/or directories that should be | |
693 | +# excluded from the INPUT source files. This way you can easily exclude a | |
694 | +# subdirectory from a directory tree whose root is specified with the INPUT tag. | |
695 | +# Note that relative paths are relative to the directory from which doxygen is | |
696 | +# run. | |
697 | + | |
698 | +EXCLUDE = | |
699 | + | |
700 | +# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or | |
701 | +# directories that are symbolic links (a Unix file system feature) are excluded | |
702 | +# from the input. | |
703 | + | |
704 | +EXCLUDE_SYMLINKS = NO | |
705 | + | |
706 | +# If the value of the INPUT tag contains directories, you can use the | |
707 | +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude | |
708 | +# certain files from those directories. Note that the wildcards are matched | |
709 | +# against the file with absolute path, so to exclude all test directories | |
710 | +# for example use the pattern */test/* | |
711 | + | |
712 | +EXCLUDE_PATTERNS = | |
713 | + | |
714 | +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names | |
715 | +# (namespaces, classes, functions, etc.) that should be excluded from the | |
716 | +# output. The symbol name can be a fully qualified name, a word, or if the | |
717 | +# wildcard * is used, a substring. Examples: ANamespace, AClass, | |
718 | +# AClass::ANamespace, ANamespace::*Test | |
719 | + | |
720 | +EXCLUDE_SYMBOLS = APIENTRY GLFWAPI | |
721 | + | |
722 | +# The EXAMPLE_PATH tag can be used to specify one or more files or | |
723 | +# directories that contain example code fragments that are included (see | |
724 | +# the \include command). | |
725 | + | |
726 | +EXAMPLE_PATH = /home/quique/Documents/14-15/SETR/Craft/deps/glfw/examples | |
727 | + | |
728 | +# If the value of the EXAMPLE_PATH tag contains directories, you can use the | |
729 | +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp | |
730 | +# and *.h) to filter out the source-files in the directories. If left | |
731 | +# blank all files are included. | |
732 | + | |
733 | +EXAMPLE_PATTERNS = | |
734 | + | |
735 | +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be | |
736 | +# searched for input files to be used with the \include or \dontinclude | |
737 | +# commands irrespective of the value of the RECURSIVE tag. | |
738 | +# Possible values are YES and NO. If left blank NO is used. | |
739 | + | |
740 | +EXAMPLE_RECURSIVE = NO | |
741 | + | |
742 | +# The IMAGE_PATH tag can be used to specify one or more files or | |
743 | +# directories that contain image that are included in the documentation (see | |
744 | +# the \image command). | |
745 | + | |
746 | +IMAGE_PATH = | |
747 | + | |
748 | +# The INPUT_FILTER tag can be used to specify a program that doxygen should | |
749 | +# invoke to filter for each input file. Doxygen will invoke the filter program | |
750 | +# by executing (via popen()) the command <filter> <input-file>, where <filter> | |
751 | +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an | |
752 | +# input file. Doxygen will then use the output that the filter program writes | |
753 | +# to standard output. | |
754 | +# If FILTER_PATTERNS is specified, this tag will be | |
755 | +# ignored. | |
756 | + | |
757 | +INPUT_FILTER = | |
758 | + | |
759 | +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern | |
760 | +# basis. | |
761 | +# Doxygen will compare the file name with each pattern and apply the | |
762 | +# filter if there is a match. | |
763 | +# The filters are a list of the form: | |
764 | +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further | |
765 | +# info on how filters are used. If FILTER_PATTERNS is empty or if | |
766 | +# non of the patterns match the file name, INPUT_FILTER is applied. | |
767 | + | |
768 | +FILTER_PATTERNS = | |
769 | + | |
770 | +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using | |
771 | +# INPUT_FILTER) will be used to filter the input files when producing source | |
772 | +# files to browse (i.e. when SOURCE_BROWSER is set to YES). | |
773 | + | |
774 | +FILTER_SOURCE_FILES = NO | |
775 | + | |
776 | +# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file | |
777 | +# pattern. A pattern will override the setting for FILTER_PATTERN (if any) | |
778 | +# and it is also possible to disable source filtering for a specific pattern | |
779 | +# using *.ext= (so without naming a filter). This option only has effect when | |
780 | +# FILTER_SOURCE_FILES is enabled. | |
781 | + | |
782 | +FILTER_SOURCE_PATTERNS = | |
783 | + | |
784 | +# If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that | |
785 | +# is part of the input, its contents will be placed on the main page (index.html). | |
786 | +# This can be useful if you have a project on for instance GitHub and want reuse | |
787 | +# the introduction page also for the doxygen output. | |
788 | + | |
789 | +USE_MDFILE_AS_MAINPAGE = | |
790 | + | |
791 | +#--------------------------------------------------------------------------- | |
792 | +# configuration options related to source browsing | |
793 | +#--------------------------------------------------------------------------- | |
794 | + | |
795 | +# If the SOURCE_BROWSER tag is set to YES then a list of source files will | |
796 | +# be generated. Documented entities will be cross-referenced with these sources. | |
797 | +# Note: To get rid of all source code in the generated output, make sure also | |
798 | +# VERBATIM_HEADERS is set to NO. | |
799 | + | |
800 | +SOURCE_BROWSER = NO | |
801 | + | |
802 | +# Setting the INLINE_SOURCES tag to YES will include the body | |
803 | +# of functions and classes directly in the documentation. | |
804 | + | |
805 | +INLINE_SOURCES = NO | |
806 | + | |
807 | +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct | |
808 | +# doxygen to hide any special comment blocks from generated source code | |
809 | +# fragments. Normal C, C++ and Fortran comments will always remain visible. | |
810 | + | |
811 | +STRIP_CODE_COMMENTS = YES | |
812 | + | |
813 | +# If the REFERENCED_BY_RELATION tag is set to YES | |
814 | +# then for each documented function all documented | |
815 | +# functions referencing it will be listed. | |
816 | + | |
817 | +REFERENCED_BY_RELATION = NO | |
818 | + | |
819 | +# If the REFERENCES_RELATION tag is set to YES | |
820 | +# then for each documented function all documented entities | |
821 | +# called/used by that function will be listed. | |
822 | + | |
823 | +REFERENCES_RELATION = NO | |
824 | + | |
825 | +# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) | |
826 | +# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from | |
827 | +# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will | |
828 | +# link to the source code. | |
829 | +# Otherwise they will link to the documentation. | |
830 | + | |
831 | +REFERENCES_LINK_SOURCE = YES | |
832 | + | |
833 | +# If the USE_HTAGS tag is set to YES then the references to source code | |
834 | +# will point to the HTML generated by the htags(1) tool instead of doxygen | |
835 | +# built-in source browser. The htags tool is part of GNU's global source | |
836 | +# tagging system (see http://www.gnu.org/software/global/global.html). You | |
837 | +# will need version 4.8.6 or higher. | |
838 | + | |
839 | +USE_HTAGS = NO | |
840 | + | |
841 | +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen | |
842 | +# will generate a verbatim copy of the header file for each class for | |
843 | +# which an include is specified. Set to NO to disable this. | |
844 | + | |
845 | +VERBATIM_HEADERS = YES | |
846 | + | |
847 | +#--------------------------------------------------------------------------- | |
848 | +# configuration options related to the alphabetical class index | |
849 | +#--------------------------------------------------------------------------- | |
850 | + | |
851 | +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index | |
852 | +# of all compounds will be generated. Enable this if the project | |
853 | +# contains a lot of classes, structs, unions or interfaces. | |
854 | + | |
855 | +ALPHABETICAL_INDEX = YES | |
856 | + | |
857 | +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then | |
858 | +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns | |
859 | +# in which this list will be split (can be a number in the range [1..20]) | |
860 | + | |
861 | +COLS_IN_ALPHA_INDEX = 5 | |
862 | + | |
863 | +# In case all classes in a project start with a common prefix, all | |
864 | +# classes will be put under the same header in the alphabetical index. | |
865 | +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that | |
866 | +# should be ignored while generating the index headers. | |
867 | + | |
868 | +IGNORE_PREFIX = glfw GLFW_ | |
869 | + | |
870 | +#--------------------------------------------------------------------------- | |
871 | +# configuration options related to the HTML output | |
872 | +#--------------------------------------------------------------------------- | |
873 | + | |
874 | +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will | |
875 | +# generate HTML output. | |
876 | + | |
877 | +GENERATE_HTML = YES | |
878 | + | |
879 | +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. | |
880 | +# If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
881 | +# put in front of it. If left blank `html' will be used as the default path. | |
882 | + | |
883 | +HTML_OUTPUT = html | |
884 | + | |
885 | +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for | |
886 | +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank | |
887 | +# doxygen will generate files with .html extension. | |
888 | + | |
889 | +HTML_FILE_EXTENSION = .html | |
890 | + | |
891 | +# The HTML_HEADER tag can be used to specify a personal HTML header for | |
892 | +# each generated HTML page. If it is left blank doxygen will generate a | |
893 | +# standard header. Note that when using a custom header you are responsible | |
894 | +# for the proper inclusion of any scripts and style sheets that doxygen | |
895 | +# needs, which is dependent on the configuration options used. | |
896 | +# It is advised to generate a default header using "doxygen -w html | |
897 | +# header.html footer.html stylesheet.css YourConfigFile" and then modify | |
898 | +# that header. Note that the header is subject to change so you typically | |
899 | +# have to redo this when upgrading to a newer version of doxygen or when | |
900 | +# changing the value of configuration settings such as GENERATE_TREEVIEW! | |
901 | + | |
902 | +HTML_HEADER = | |
903 | + | |
904 | +# The HTML_FOOTER tag can be used to specify a personal HTML footer for | |
905 | +# each generated HTML page. If it is left blank doxygen will generate a | |
906 | +# standard footer. | |
907 | + | |
908 | +HTML_FOOTER = | |
909 | + | |
910 | +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading | |
911 | +# style sheet that is used by each HTML page. It can be used to | |
912 | +# fine-tune the look of the HTML output. If left blank doxygen will | |
913 | +# generate a default style sheet. Note that it is recommended to use | |
914 | +# HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | |
915 | +# tag will in the future become obsolete. | |
916 | + | |
917 | +HTML_STYLESHEET = | |
918 | + | |
919 | +# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | |
920 | +# user-defined cascading style sheet that is included after the standard | |
921 | +# style sheets created by doxygen. Using this option one can overrule | |
922 | +# certain style aspects. This is preferred over using HTML_STYLESHEET | |
923 | +# since it does not replace the standard style sheet and is therefor more | |
924 | +# robust against future updates. Doxygen will copy the style sheet file to | |
925 | +# the output directory. | |
926 | + | |
927 | +HTML_EXTRA_STYLESHEET = | |
928 | + | |
929 | +# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | |
930 | +# other source files which should be copied to the HTML output directory. Note | |
931 | +# that these files will be copied to the base HTML output directory. Use the | |
932 | +# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these | |
933 | +# files. In the HTML_STYLESHEET file, use the file name only. Also note that | |
934 | +# the files will be copied as-is; there are no commands or markers available. | |
935 | + | |
936 | +HTML_EXTRA_FILES = | |
937 | + | |
938 | +# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. | |
939 | +# Doxygen will adjust the colors in the style sheet and background images | |
940 | +# according to this color. Hue is specified as an angle on a colorwheel, | |
941 | +# see http://en.wikipedia.org/wiki/Hue for more information. | |
942 | +# For instance the value 0 represents red, 60 is yellow, 120 is green, | |
943 | +# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. | |
944 | +# The allowed range is 0 to 359. | |
945 | + | |
946 | +HTML_COLORSTYLE_HUE = 220 | |
947 | + | |
948 | +# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of | |
949 | +# the colors in the HTML output. For a value of 0 the output will use | |
950 | +# grayscales only. A value of 255 will produce the most vivid colors. | |
951 | + | |
952 | +HTML_COLORSTYLE_SAT = 100 | |
953 | + | |
954 | +# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to | |
955 | +# the luminance component of the colors in the HTML output. Values below | |
956 | +# 100 gradually make the output lighter, whereas values above 100 make | |
957 | +# the output darker. The value divided by 100 is the actual gamma applied, | |
958 | +# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, | |
959 | +# and 100 does not change the gamma. | |
960 | + | |