Package list readosm / 6d1ba6b
Imported Upstream version 1.0.0a+dfsg1 David Paleino 9 years ago
45 changed file(s) with 54444 addition(s) and 0 deletion(s). Raw diff Collapse all Expand all
0 Original Author:
1 Alessandro Furieri <a.furieri@lqt.it>
2
3 Contributors:
0 MOZILLA PUBLIC LICENSE
1 Version 1.1
2
3 ---------------
4
5 1. Definitions.
6
7 1.0.1. "Commercial Use" means distribution or otherwise making the
8 Covered Code available to a third party.
9
10 1.1. "Contributor" means each entity that creates or contributes to
11 the creation of Modifications.
12
13 1.2. "Contributor Version" means the combination of the Original
14 Code, prior Modifications used by a Contributor, and the Modifications
15 made by that particular Contributor.
16
17 1.3. "Covered Code" means the Original Code or Modifications or the
18 combination of the Original Code and Modifications, in each case
19 including portions thereof.
20
21 1.4. "Electronic Distribution Mechanism" means a mechanism generally
22 accepted in the software development community for the electronic
23 transfer of data.
24
25 1.5. "Executable" means Covered Code in any form other than Source
26 Code.
27
28 1.6. "Initial Developer" means the individual or entity identified
29 as the Initial Developer in the Source Code notice required by Exhibit
30 A.
31
32 1.7. "Larger Work" means a work which combines Covered Code or
33 portions thereof with code not governed by the terms of this License.
34
35 1.8. "License" means this document.
36
37 1.8.1. "Licensable" means having the right to grant, to the maximum
38 extent possible, whether at the time of the initial grant or
39 subsequently acquired, any and all of the rights conveyed herein.
40
41 1.9. "Modifications" means any addition to or deletion from the
42 substance or structure of either the Original Code or any previous
43 Modifications. When Covered Code is released as a series of files, a
44 Modification is:
45 A. Any addition to or deletion from the contents of a file
46 containing Original Code or previous Modifications.
47
48 B. Any new file that contains any part of the Original Code or
49 previous Modifications.
50
51 1.10. "Original Code" means Source Code of computer software code
52 which is described in the Source Code notice required by Exhibit A as
53 Original Code, and which, at the time of its release under this
54 License is not already Covered Code governed by this License.
55
56 1.10.1. "Patent Claims" means any patent claim(s), now owned or
57 hereafter acquired, including without limitation, method, process,
58 and apparatus claims, in any patent Licensable by grantor.
59
60 1.11. "Source Code" means the preferred form of the Covered Code for
61 making modifications to it, including all modules it contains, plus
62 any associated interface definition files, scripts used to control
63 compilation and installation of an Executable, or source code
64 differential comparisons against either the Original Code or another
65 well known, available Covered Code of the Contributor's choice. The
66 Source Code can be in a compressed or archival form, provided the
67 appropriate decompression or de-archiving software is widely available
68 for no charge.
69
70 1.12. "You" (or "Your") means an individual or a legal entity
71 exercising rights under, and complying with all of the terms of, this
72 License or a future version of this License issued under Section 6.1.
73 For legal entities, "You" includes any entity which controls, is
74 controlled by, or is under common control with You. For purposes of
75 this definition, "control" means (a) the power, direct or indirect,
76 to cause the direction or management of such entity, whether by
77 contract or otherwise, or (b) ownership of more than fifty percent
78 (50%) of the outstanding shares or beneficial ownership of such
79 entity.
80
81 2. Source Code License.
82
83 2.1. The Initial Developer Grant.
84 The Initial Developer hereby grants You a world-wide, royalty-free,
85 non-exclusive license, subject to third party intellectual property
86 claims:
87 (a) under intellectual property rights (other than patent or
88 trademark) Licensable by Initial Developer to use, reproduce,
89 modify, display, perform, sublicense and distribute the Original
90 Code (or portions thereof) with or without Modifications, and/or
91 as part of a Larger Work; and
92
93 (b) under Patents Claims infringed by the making, using or
94 selling of Original Code, to make, have made, use, practice,
95 sell, and offer for sale, and/or otherwise dispose of the
96 Original Code (or portions thereof).
97
98 (c) the licenses granted in this Section 2.1(a) and (b) are
99 effective on the date Initial Developer first distributes
100 Original Code under the terms of this License.
101
102 (d) Notwithstanding Section 2.1(b) above, no patent license is
103 granted: 1) for code that You delete from the Original Code; 2)
104 separate from the Original Code; or 3) for infringements caused
105 by: i) the modification of the Original Code or ii) the
106 combination of the Original Code with other software or devices.
107
108 2.2. Contributor Grant.
109 Subject to third party intellectual property claims, each Contributor
110 hereby grants You a world-wide, royalty-free, non-exclusive license
111
112 (a) under intellectual property rights (other than patent or
113 trademark) Licensable by Contributor, to use, reproduce, modify,
114 display, perform, sublicense and distribute the Modifications
115 created by such Contributor (or portions thereof) either on an
116 unmodified basis, with other Modifications, as Covered Code
117 and/or as part of a Larger Work; and
118
119 (b) under Patent Claims infringed by the making, using, or
120 selling of Modifications made by that Contributor either alone
121 and/or in combination with its Contributor Version (or portions
122 of such combination), to make, use, sell, offer for sale, have
123 made, and/or otherwise dispose of: 1) Modifications made by that
124 Contributor (or portions thereof); and 2) the combination of
125 Modifications made by that Contributor with its Contributor
126 Version (or portions of such combination).
127
128 (c) the licenses granted in Sections 2.2(a) and 2.2(b) are
129 effective on the date Contributor first makes Commercial Use of
130 the Covered Code.
131
132 (d) Notwithstanding Section 2.2(b) above, no patent license is
133 granted: 1) for any code that Contributor has deleted from the
134 Contributor Version; 2) separate from the Contributor Version;
135 3) for infringements caused by: i) third party modifications of
136 Contributor Version or ii) the combination of Modifications made
137 by that Contributor with other software (except as part of the
138 Contributor Version) or other devices; or 4) under Patent Claims
139 infringed by Covered Code in the absence of Modifications made by
140 that Contributor.
141
142 3. Distribution Obligations.
143
144 3.1. Application of License.
145 The Modifications which You create or to which You contribute are
146 governed by the terms of this License, including without limitation
147 Section 2.2. The Source Code version of Covered Code may be
148 distributed only under the terms of this License or a future version
149 of this License released under Section 6.1, and You must include a
150 copy of this License with every copy of the Source Code You
151 distribute. You may not offer or impose any terms on any Source Code
152 version that alters or restricts the applicable version of this
153 License or the recipients' rights hereunder. However, You may include
154 an additional document offering the additional rights described in
155 Section 3.5.
156
157 3.2. Availability of Source Code.
158 Any Modification which You create or to which You contribute must be
159 made available in Source Code form under the terms of this License
160 either on the same media as an Executable version or via an accepted
161 Electronic Distribution Mechanism to anyone to whom you made an
162 Executable version available; and if made available via Electronic
163 Distribution Mechanism, must remain available for at least twelve (12)
164 months after the date it initially became available, or at least six
165 (6) months after a subsequent version of that particular Modification
166 has been made available to such recipients. You are responsible for
167 ensuring that the Source Code version remains available even if the
168 Electronic Distribution Mechanism is maintained by a third party.
169
170 3.3. Description of Modifications.
171 You must cause all Covered Code to which You contribute to contain a
172 file documenting the changes You made to create that Covered Code and
173 the date of any change. You must include a prominent statement that
174 the Modification is derived, directly or indirectly, from Original
175 Code provided by the Initial Developer and including the name of the
176 Initial Developer in (a) the Source Code, and (b) in any notice in an
177 Executable version or related documentation in which You describe the
178 origin or ownership of the Covered Code.
179
180 3.4. Intellectual Property Matters
181 (a) Third Party Claims.
182 If Contributor has knowledge that a license under a third party's
183 intellectual property rights is required to exercise the rights
184 granted by such Contributor under Sections 2.1 or 2.2,
185 Contributor must include a text file with the Source Code
186 distribution titled "LEGAL" which describes the claim and the
187 party making the claim in sufficient detail that a recipient will
188 know whom to contact. If Contributor obtains such knowledge after
189 the Modification is made available as described in Section 3.2,
190 Contributor shall promptly modify the LEGAL file in all copies
191 Contributor makes available thereafter and shall take other steps
192 (such as notifying appropriate mailing lists or newsgroups)
193 reasonably calculated to inform those who received the Covered
194 Code that new knowledge has been obtained.
195
196 (b) Contributor APIs.
197 If Contributor's Modifications include an application programming
198 interface and Contributor has knowledge of patent licenses which
199 are reasonably necessary to implement that API, Contributor must
200 also include this information in the LEGAL file.
201
202 (c) Representations.
203 Contributor represents that, except as disclosed pursuant to
204 Section 3.4(a) above, Contributor believes that Contributor's
205 Modifications are Contributor's original creation(s) and/or
206 Contributor has sufficient rights to grant the rights conveyed by
207 this License.
208
209 3.5. Required Notices.
210 You must duplicate the notice in Exhibit A in each file of the Source
211 Code. If it is not possible to put such notice in a particular Source
212 Code file due to its structure, then You must include such notice in a
213 location (such as a relevant directory) where a user would be likely
214 to look for such a notice. If You created one or more Modification(s)
215 You may add your name as a Contributor to the notice described in
216 Exhibit A. You must also duplicate this License in any documentation
217 for the Source Code where You describe recipients' rights or ownership
218 rights relating to Covered Code. You may choose to offer, and to
219 charge a fee for, warranty, support, indemnity or liability
220 obligations to one or more recipients of Covered Code. However, You
221 may do so only on Your own behalf, and not on behalf of the Initial
222 Developer or any Contributor. You must make it absolutely clear than
223 any such warranty, support, indemnity or liability obligation is
224 offered by You alone, and You hereby agree to indemnify the Initial
225 Developer and every Contributor for any liability incurred by the
226 Initial Developer or such Contributor as a result of warranty,
227 support, indemnity or liability terms You offer.
228
229 3.6. Distribution of Executable Versions.
230 You may distribute Covered Code in Executable form only if the
231 requirements of Section 3.1-3.5 have been met for that Covered Code,
232 and if You include a notice stating that the Source Code version of
233 the Covered Code is available under the terms of this License,
234 including a description of how and where You have fulfilled the
235 obligations of Section 3.2. The notice must be conspicuously included
236 in any notice in an Executable version, related documentation or
237 collateral in which You describe recipients' rights relating to the
238 Covered Code. You may distribute the Executable version of Covered
239 Code or ownership rights under a license of Your choice, which may
240 contain terms different from this License, provided that You are in
241 compliance with the terms of this License and that the license for the
242 Executable version does not attempt to limit or alter the recipient's
243 rights in the Source Code version from the rights set forth in this
244 License. If You distribute the Executable version under a different
245 license You must make it absolutely clear that any terms which differ
246 from this License are offered by You alone, not by the Initial
247 Developer or any Contributor. You hereby agree to indemnify the
248 Initial Developer and every Contributor for any liability incurred by
249 the Initial Developer or such Contributor as a result of any such
250 terms You offer.
251
252 3.7. Larger Works.
253 You may create a Larger Work by combining Covered Code with other code
254 not governed by the terms of this License and distribute the Larger
255 Work as a single product. In such a case, You must make sure the
256 requirements of this License are fulfilled for the Covered Code.
257
258 4. Inability to Comply Due to Statute or Regulation.
259
260 If it is impossible for You to comply with any of the terms of this
261 License with respect to some or all of the Covered Code due to
262 statute, judicial order, or regulation then You must: (a) comply with
263 the terms of this License to the maximum extent possible; and (b)
264 describe the limitations and the code they affect. Such description
265 must be included in the LEGAL file described in Section 3.4 and must
266 be included with all distributions of the Source Code. Except to the
267 extent prohibited by statute or regulation, such description must be
268 sufficiently detailed for a recipient of ordinary skill to be able to
269 understand it.
270
271 5. Application of this License.
272
273 This License applies to code to which the Initial Developer has
274 attached the notice in Exhibit A and to related Covered Code.
275
276 6. Versions of the License.
277
278 6.1. New Versions.
279 Netscape Communications Corporation ("Netscape") may publish revised
280 and/or new versions of the License from time to time. Each version
281 will be given a distinguishing version number.
282
283 6.2. Effect of New Versions.
284 Once Covered Code has been published under a particular version of the
285 License, You may always continue to use it under the terms of that
286 version. You may also choose to use such Covered Code under the terms
287 of any subsequent version of the License published by Netscape. No one
288 other than Netscape has the right to modify the terms applicable to
289 Covered Code created under this License.
290
291 6.3. Derivative Works.
292 If You create or use a modified version of this License (which you may
293 only do in order to apply it to code which is not already Covered Code
294 governed by this License), You must (a) rename Your license so that
295 the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape",
296 "MPL", "NPL" or any confusingly similar phrase do not appear in your
297 license (except to note that your license differs from this License)
298 and (b) otherwise make it clear that Your version of the license
299 contains terms which differ from the Mozilla Public License and
300 Netscape Public License. (Filling in the name of the Initial
301 Developer, Original Code or Contributor in the notice described in
302 Exhibit A shall not of themselves be deemed to be modifications of
303 this License.)
304
305 7. DISCLAIMER OF WARRANTY.
306
307 COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
308 WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
309 WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
310 DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
311 THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
312 IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT,
313 YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE
314 COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
315 OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
316 ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
317
318 8. TERMINATION.
319
320 8.1. This License and the rights granted hereunder will terminate
321 automatically if You fail to comply with terms herein and fail to cure
322 such breach within 30 days of becoming aware of the breach. All
323 sublicenses to the Covered Code which are properly granted shall
324 survive any termination of this License. Provisions which, by their
325 nature, must remain in effect beyond the termination of this License
326 shall survive.
327
328 8.2. If You initiate litigation by asserting a patent infringement
329 claim (excluding declatory judgment actions) against Initial Developer
330 or a Contributor (the Initial Developer or Contributor against whom
331 You file such action is referred to as "Participant") alleging that:
332
333 (a) such Participant's Contributor Version directly or indirectly
334 infringes any patent, then any and all rights granted by such
335 Participant to You under Sections 2.1 and/or 2.2 of this License
336 shall, upon 60 days notice from Participant terminate prospectively,
337 unless if within 60 days after receipt of notice You either: (i)
338 agree in writing to pay Participant a mutually agreeable reasonable
339 royalty for Your past and future use of Modifications made by such
340 Participant, or (ii) withdraw Your litigation claim with respect to
341 the Contributor Version against such Participant. If within 60 days
342 of notice, a reasonable royalty and payment arrangement are not
343 mutually agreed upon in writing by the parties or the litigation claim
344 is not withdrawn, the rights granted by Participant to You under
345 Sections 2.1 and/or 2.2 automatically terminate at the expiration of
346 the 60 day notice period specified above.
347
348 (b) any software, hardware, or device, other than such Participant's
349 Contributor Version, directly or indirectly infringes any patent, then
350 any rights granted to You by such Participant under Sections 2.1(b)
351 and 2.2(b) are revoked effective as of the date You first made, used,
352 sold, distributed, or had made, Modifications made by that
353 Participant.
354
355 8.3. If You assert a patent infringement claim against Participant
356 alleging that such Participant's Contributor Version directly or
357 indirectly infringes any patent where such claim is resolved (such as
358 by license or settlement) prior to the initiation of patent
359 infringement litigation, then the reasonable value of the licenses
360 granted by such Participant under Sections 2.1 or 2.2 shall be taken
361 into account in determining the amount or value of any payment or
362 license.
363
364 8.4. In the event of termination under Sections 8.1 or 8.2 above,
365 all end user license agreements (excluding distributors and resellers)
366 which have been validly granted by You or any distributor hereunder
367 prior to termination shall survive termination.
368
369 9. LIMITATION OF LIABILITY.
370
371 UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
372 (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
373 DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
374 OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR
375 ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
376 CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
377 WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
378 COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
379 INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
380 LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
381 RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
382 PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
383 EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
384 THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
385
386 10. U.S. GOVERNMENT END USERS.
387
388 The Covered Code is a "commercial item," as that term is defined in
389 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
390 software" and "commercial computer software documentation," as such
391 terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
392 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
393 all U.S. Government End Users acquire Covered Code with only those
394 rights set forth herein.
395
396 11. MISCELLANEOUS.
397
398 This License represents the complete agreement concerning subject
399 matter hereof. If any provision of this License is held to be
400 unenforceable, such provision shall be reformed only to the extent
401 necessary to make it enforceable. This License shall be governed by
402 California law provisions (except to the extent applicable law, if
403 any, provides otherwise), excluding its conflict-of-law provisions.
404 With respect to disputes in which at least one party is a citizen of,
405 or an entity chartered or registered to do business in the United
406 States of America, any litigation relating to this License shall be
407 subject to the jurisdiction of the Federal Courts of the Northern
408 District of California, with venue lying in Santa Clara County,
409 California, with the losing party responsible for costs, including
410 without limitation, court costs and reasonable attorneys' fees and
411 expenses. The application of the United Nations Convention on
412 Contracts for the International Sale of Goods is expressly excluded.
413 Any law or regulation which provides that the language of a contract
414 shall be construed against the drafter shall not apply to this
415 License.
416
417 12. RESPONSIBILITY FOR CLAIMS.
418
419 As between Initial Developer and the Contributors, each party is
420 responsible for claims and damages arising, directly or indirectly,
421 out of its utilization of rights under this License and You agree to
422 work with Initial Developer and Contributors to distribute such
423 responsibility on an equitable basis. Nothing herein is intended or
424 shall be deemed to constitute any admission of liability.
425
426 13. MULTIPLE-LICENSED CODE.
427
428 Initial Developer may designate portions of the Covered Code as
429 "Multiple-Licensed". "Multiple-Licensed" means that the Initial
430 Developer permits you to utilize portions of the Covered Code under
431 Your choice of the NPL or the alternative licenses, if any, specified
432 by the Initial Developer in the file described in Exhibit A.
433
434 EXHIBIT A -Mozilla Public License.
435
436 ``The contents of this file are subject to the Mozilla Public License
437 Version 1.1 (the "License"); you may not use this file except in
438 compliance with the License. You may obtain a copy of the License at
439 http://www.mozilla.org/MPL/
440
441 Software distributed under the License is distributed on an "AS IS"
442 basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
443 License for the specific language governing rights and limitations
444 under the License.
445
446 The Original Code is the ReadOSM library.
447
448 The Initial Developer of the Original Code is Alessandro Furieri.
449 Portions created by the Initial Developer are Copyright (C) 2012
450 the Initial Developer. All Rights Reserved.
451
452 Contributor(s):
453
454 Alternatively, the contents of this file may be used under the terms of
455 either the GNU General Public License Version 2 or later (the "GPL"), or
456 the GNU Lesser General Public License Version 2.1 or later (the "LGPL"),
457 in which case the provisions of the GPL or the LGPL are applicable instead
458 of those above. If you wish to allow use of your version of this file only
459 under the terms of either the GPL or the LGPL, and not to allow others to
460 use your version of this file under the terms of the MPL, indicate your
461 decision by deleting the provisions above and replace them with the notice
462 and other provisions required by the GPL or the LGPL. If you do not delete
463 the provisions above, a recipient may use your version of this file under
464 the terms of any one of the MPL, the GPL or the LGPL.
465
466 [NOTE: The text of this Exhibit A may differ slightly from the text of
467 the notices in the Source Code files of the Original Code. You should
468 use the text of this Exhibit A rather than the text found in the
469 Original Code Source Code for Your Modifications.]
470
(New empty file)
0 # Doxyfile 1.7.3
1
2 # This file describes the settings to be used by the documentation system
3 # doxygen (www.doxygen.org) for a project.
4 #
5 # All text after a hash (#) is considered a comment and will be ignored.
6 # The format is:
7 # TAG = value [value, ...]
8 # For lists items can also be appended using:
9 # TAG += value [value, ...]
10 # Values that contain spaces should be placed between quotes (" ").
11
12 #---------------------------------------------------------------------------
13 # Project related configuration options
14 #---------------------------------------------------------------------------
15
16 # This tag specifies the encoding used for all characters in the config file
17 # that follow. The default is UTF-8 which is also the encoding used for all
18 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
19 # iconv built into libc) for the transcoding. See
20 # http://www.gnu.org/software/libiconv for the list of possible encodings.
21
22 DOXYFILE_ENCODING = UTF-8
23
24 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
25 # by quotes) that should identify the project.
26
27 PROJECT_NAME = readosm
28
29 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
30 # This could be handy for archiving the generated documentation or
31 # if some version control system is used.
32
33 PROJECT_NUMBER = @VERSION@
34
35 # Using the PROJECT_BRIEF tag one can provide an optional one line description for a project that appears at the top of each page and should give viewer a quick idea about the purpose of the project. Keep the description short.
36
37 PROJECT_BRIEF =
38
39 # With the PROJECT_LOGO tag one can specify an logo or icon that is
40 # included in the documentation. The maximum height of the logo should not
41 # exceed 55 pixels and the maximum width should not exceed 200 pixels.
42 # Doxygen will copy the logo to the output directory.
43
44 PROJECT_LOGO =
45
46 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
47 # base path where the generated documentation will be put.
48 # If a relative path is entered, it will be relative to the location
49 # where doxygen was started. If left blank the current directory will be used.
50
51 OUTPUT_DIRECTORY =
52
53 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
54 # 4096 sub-directories (in 2 levels) under the output directory of each output
55 # format and will distribute the generated files over these directories.
56 # Enabling this option can be useful when feeding doxygen a huge amount of
57 # source files, where putting all generated files in the same directory would
58 # otherwise cause performance problems for the file system.
59
60 CREATE_SUBDIRS = NO
61
62 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
63 # documentation generated by doxygen is written. Doxygen will use this
64 # information to generate all constant output in the proper language.
65 # The default language is English, other supported languages are:
66 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
67 # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
68 # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
69 # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
70 # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
71 # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
72
73 OUTPUT_LANGUAGE = English
74
75 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
76 # include brief member descriptions after the members that are listed in
77 # the file and class documentation (similar to JavaDoc).
78 # Set to NO to disable this.
79
80 BRIEF_MEMBER_DESC = YES
81
82 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
83 # the brief description of a member or function before the detailed description.
84 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
85 # brief descriptions will be completely suppressed.
86
87 REPEAT_BRIEF = YES
88
89 # This tag implements a quasi-intelligent brief description abbreviator
90 # that is used to form the text in various listings. Each string
91 # in this list, if found as the leading text of the brief description, will be
92 # stripped from the text and the result after processing the whole list, is
93 # used as the annotated text. Otherwise, the brief description is used as-is.
94 # If left blank, the following values are used ("$name" is automatically
95 # replaced with the name of the entity): "The $name class" "The $name widget"
96 # "The $name file" "is" "provides" "specifies" "contains"
97 # "represents" "a" "an" "the"
98
99 ABBREVIATE_BRIEF =
100
101 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
102 # Doxygen will generate a detailed section even if there is only a brief
103 # description.
104
105 ALWAYS_DETAILED_SEC = NO
106
107 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
108 # inherited members of a class in the documentation of that class as if those
109 # members were ordinary class members. Constructors, destructors and assignment
110 # operators of the base classes will not be shown.
111
112 INLINE_INHERITED_MEMB = NO
113
114 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
115 # path before files name in the file list and in the header files. If set
116 # to NO the shortest path that makes the file name unique will be used.
117
118 FULL_PATH_NAMES = YES
119
120 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
121 # can be used to strip a user-defined part of the path. Stripping is
122 # only done if one of the specified strings matches the left-hand part of
123 # the path. The tag can be used to show relative paths in the file list.
124 # If left blank the directory from which doxygen is run is used as the
125 # path to strip.
126
127 STRIP_FROM_PATH =
128
129 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
130 # the path mentioned in the documentation of a class, which tells
131 # the reader which header file to include in order to use a class.
132 # If left blank only the name of the header file containing the class
133 # definition is used. Otherwise one should specify the include paths that
134 # are normally passed to the compiler using the -I flag.
135
136 STRIP_FROM_INC_PATH =
137
138 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
139 # (but less readable) file names. This can be useful if your file system
140 # doesn't support long names like on DOS, Mac, or CD-ROM.
141
142 SHORT_NAMES = NO
143
144 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
145 # will interpret the first line (until the first dot) of a JavaDoc-style
146 # comment as the brief description. If set to NO, the JavaDoc
147 # comments will behave just like regular Qt-style comments
148 # (thus requiring an explicit @brief command for a brief description.)
149
150 JAVADOC_AUTOBRIEF = YES
151
152 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will
153 # interpret the first line (until the first dot) of a Qt-style
154 # comment as the brief description. If set to NO, the comments
155 # will behave just like regular Qt-style comments (thus requiring
156 # an explicit \brief command for a brief description.)
157
158 QT_AUTOBRIEF = NO
159
160 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
161 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
162 # comments) as a brief description. This used to be the default behaviour.
163 # The new default is to treat a multi-line C++ comment block as a detailed
164 # description. Set this tag to YES if you prefer the old behaviour instead.
165
166 MULTILINE_CPP_IS_BRIEF = NO
167
168 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
169 # member inherits the documentation from any documented member that it
170 # re-implements.
171
172 INHERIT_DOCS = YES
173
174 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
175 # a new page for each member. If set to NO, the documentation of a member will
176 # be part of the file/class/namespace that contains it.
177
178 SEPARATE_MEMBER_PAGES = NO
179
180 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
181 # Doxygen uses this value to replace tabs by spaces in code fragments.
182
183 TAB_SIZE = 8
184
185 # This tag can be used to specify a number of aliases that acts
186 # as commands in the documentation. An alias has the form "name=value".
187 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
188 # put the command \sideeffect (or @sideeffect) in the documentation, which
189 # will result in a user-defined paragraph with heading "Side Effects:".
190 # You can put \n's in the value part of an alias to insert newlines.
191
192 ALIASES =
193
194 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
195 # sources only. Doxygen will then generate output that is more tailored for C.
196 # For instance, some of the names that are used will be different. The list
197 # of all members will be omitted, etc.
198
199 OPTIMIZE_OUTPUT_FOR_C = YES
200
201 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
202 # sources only. Doxygen will then generate output that is more tailored for
203 # Java. For instance, namespaces will be presented as packages, qualified
204 # scopes will look different, etc.
205
206 OPTIMIZE_OUTPUT_JAVA = NO
207
208 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
209 # sources only. Doxygen will then generate output that is more tailored for
210 # Fortran.
211
212 OPTIMIZE_FOR_FORTRAN = NO
213
214 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
215 # sources. Doxygen will then generate output that is tailored for
216 # VHDL.
217
218 OPTIMIZE_OUTPUT_VHDL = NO
219
220 # Doxygen selects the parser to use depending on the extension of the files it
221 # parses. With this tag you can assign which parser to use for a given extension.
222 # Doxygen has a built-in mapping, but you can override or extend it using this
223 # tag. The format is ext=language, where ext is a file extension, and language
224 # is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
225 # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
226 # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
227 # (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
228 # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
229
230 EXTENSION_MAPPING =
231
232 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
233 # to include (a tag file for) the STL sources as input, then you should
234 # set this tag to YES in order to let doxygen match functions declarations and
235 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
236 # func(std::string) {}). This also makes the inheritance and collaboration
237 # diagrams that involve STL classes more complete and accurate.
238
239 BUILTIN_STL_SUPPORT = NO
240
241 # If you use Microsoft's C++/CLI language, you should set this option to YES to
242 # enable parsing support.
243
244 CPP_CLI_SUPPORT = NO
245
246 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
247 # Doxygen will parse them like normal C++ but will assume all classes use public
248 # instead of private inheritance when no explicit protection keyword is present.
249
250 SIP_SUPPORT = NO
251
252 # For Microsoft's IDL there are propget and propput attributes to indicate getter
253 # and setter methods for a property. Setting this option to YES (the default)
254 # will make doxygen replace the get and set methods by a property in the
255 # documentation. This will only work if the methods are indeed getting or
256 # setting a simple type. If this is not the case, or you want to show the
257 # methods anyway, you should set this option to NO.
258
259 IDL_PROPERTY_SUPPORT = YES
260
261 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
262 # tag is set to YES, then doxygen will reuse the documentation of the first
263 # member in the group (if any) for the other members of the group. By default
264 # all members of a group must be documented explicitly.
265
266 DISTRIBUTE_GROUP_DOC = NO
267
268 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
269 # the same type (for instance a group of public functions) to be put as a
270 # subgroup of that type (e.g. under the Public Functions section). Set it to
271 # NO to prevent subgrouping. Alternatively, this can be done per class using
272 # the \nosubgrouping command.
273
274 SUBGROUPING = YES
275
276 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
277 # is documented as struct, union, or enum with the name of the typedef. So
278 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
279 # with name TypeT. When disabled the typedef will appear as a member of a file,
280 # namespace, or class. And the struct will be named TypeS. This can typically
281 # be useful for C code in case the coding convention dictates that all compound
282 # types are typedef'ed and only the typedef is referenced, never the tag name.
283
284 TYPEDEF_HIDES_STRUCT = NO
285
286 # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
287 # determine which symbols to keep in memory and which to flush to disk.
288 # When the cache is full, less often used symbols will be written to disk.
289 # For small to medium size projects (<1000 input files) the default value is
290 # probably good enough. For larger projects a too small cache size can cause
291 # doxygen to be busy swapping symbols to and from disk most of the time
292 # causing a significant performance penalty.
293 # If the system has enough physical memory increasing the cache will improve the
294 # performance by keeping more symbols in memory. Note that the value works on
295 # a logarithmic scale so increasing the size by one will roughly double the
296 # memory usage. The cache size is given by this formula:
297 # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
298 # corresponding to a cache size of 2^16 = 65536 symbols
299
300 SYMBOL_CACHE_SIZE = 0
301
302 #---------------------------------------------------------------------------
303 # Build related configuration options
304 #---------------------------------------------------------------------------
305
306 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
307 # documentation are documented, even if no documentation was available.
308 # Private class members and static file members will be hidden unless
309 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
310
311 EXTRACT_ALL = NO
312
313 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
314 # will be included in the documentation.
315
316 EXTRACT_PRIVATE = NO
317
318 # If the EXTRACT_STATIC tag is set to YES all static members of a file
319 # will be included in the documentation.
320
321 EXTRACT_STATIC = NO
322
323 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
324 # defined locally in source files will be included in the documentation.
325 # If set to NO only classes defined in header files are included.
326
327 EXTRACT_LOCAL_CLASSES = YES
328
329 # This flag is only useful for Objective-C code. When set to YES local
330 # methods, which are defined in the implementation section but not in
331 # the interface are included in the documentation.
332 # If set to NO (the default) only methods in the interface are included.
333
334 EXTRACT_LOCAL_METHODS = NO
335
336 # If this flag is set to YES, the members of anonymous namespaces will be
337 # extracted and appear in the documentation as a namespace called
338 # 'anonymous_namespace{file}', where file will be replaced with the base
339 # name of the file that contains the anonymous namespace. By default
340 # anonymous namespaces are hidden.
341
342 EXTRACT_ANON_NSPACES = NO
343
344 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
345 # undocumented members of documented classes, files or namespaces.
346 # If set to NO (the default) these members will be included in the
347 # various overviews, but no documentation section is generated.
348 # This option has no effect if EXTRACT_ALL is enabled.
349
350 HIDE_UNDOC_MEMBERS = NO
351
352 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
353 # undocumented classes that are normally visible in the class hierarchy.
354 # If set to NO (the default) these classes will be included in the various
355 # overviews. This option has no effect if EXTRACT_ALL is enabled.
356
357 HIDE_UNDOC_CLASSES = NO
358
359 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
360 # friend (class|struct|union) declarations.
361 # If set to NO (the default) these declarations will be included in the
362 # documentation.
363
364 HIDE_FRIEND_COMPOUNDS = NO
365
366 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
367 # documentation blocks found inside the body of a function.
368 # If set to NO (the default) these blocks will be appended to the
369 # function's detailed documentation block.
370
371 HIDE_IN_BODY_DOCS = NO
372
373 # The INTERNAL_DOCS tag determines if documentation
374 # that is typed after a \internal command is included. If the tag is set
375 # to NO (the default) then the documentation will be excluded.
376 # Set it to YES to include the internal documentation.
377
378 INTERNAL_DOCS = NO
379
380 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
381 # file names in lower-case letters. If set to YES upper-case letters are also
382 # allowed. This is useful if you have classes or files whose names only differ
383 # in case and if your file system supports case sensitive file names. Windows
384 # and Mac users are advised to set this option to NO.
385
386 CASE_SENSE_NAMES = YES
387
388 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
389 # will show members with their full class and namespace scopes in the
390 # documentation. If set to YES the scope will be hidden.
391
392 HIDE_SCOPE_NAMES = NO
393
394 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
395 # will put a list of the files that are included by a file in the documentation
396 # of that file.
397
398 SHOW_INCLUDE_FILES = YES
399
400 # If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
401 # will list include files with double quotes in the documentation
402 # rather than with sharp brackets.
403
404 FORCE_LOCAL_INCLUDES = NO
405
406 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
407 # is inserted in the documentation for inline members.
408
409 INLINE_INFO = YES
410
411 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
412 # will sort the (detailed) documentation of file and class members
413 # alphabetically by member name. If set to NO the members will appear in
414 # declaration order.
415
416 SORT_MEMBER_DOCS = YES
417
418 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
419 # brief documentation of file, namespace and class members alphabetically
420 # by member name. If set to NO (the default) the members will appear in
421 # declaration order.
422
423 SORT_BRIEF_DOCS = NO
424
425 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
426 # will sort the (brief and detailed) documentation of class members so that
427 # constructors and destructors are listed first. If set to NO (the default)
428 # the constructors will appear in the respective orders defined by
429 # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
430 # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
431 # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
432
433 SORT_MEMBERS_CTORS_1ST = NO
434
435 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
436 # hierarchy of group names into alphabetical order. If set to NO (the default)
437 # the group names will appear in their defined order.
438
439 SORT_GROUP_NAMES = NO
440
441 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
442 # sorted by fully-qualified names, including namespaces. If set to
443 # NO (the default), the class list will be sorted only by class name,
444 # not including the namespace part.
445 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
446 # Note: This option applies only to the class list, not to the
447 # alphabetical list.
448
449 SORT_BY_SCOPE_NAME = NO
450
451 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper type resolution of all parameters of a function it will reject a
452 # match between the prototype and the implementation of a member function even if there is only one candidate or it is obvious which candidate to choose by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
453 # will still accept a match between prototype and implementation in such cases.
454
455 STRICT_PROTO_MATCHING = NO
456
457 # The GENERATE_TODOLIST tag can be used to enable (YES) or
458 # disable (NO) the todo list. This list is created by putting \todo
459 # commands in the documentation.
460
461 GENERATE_TODOLIST = YES
462
463 # The GENERATE_TESTLIST tag can be used to enable (YES) or
464 # disable (NO) the test list. This list is created by putting \test
465 # commands in the documentation.
466
467 GENERATE_TESTLIST = YES
468
469 # The GENERATE_BUGLIST tag can be used to enable (YES) or
470 # disable (NO) the bug list. This list is created by putting \bug
471 # commands in the documentation.
472
473 GENERATE_BUGLIST = YES
474
475 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
476 # disable (NO) the deprecated list. This list is created by putting
477 # \deprecated commands in the documentation.
478
479 GENERATE_DEPRECATEDLIST= YES
480
481 # The ENABLED_SECTIONS tag can be used to enable conditional
482 # documentation sections, marked by \if sectionname ... \endif.
483
484 ENABLED_SECTIONS =
485
486 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
487 # the initial value of a variable or macro consists of for it to appear in
488 # the documentation. If the initializer consists of more lines than specified
489 # here it will be hidden. Use a value of 0 to hide initializers completely.
490 # The appearance of the initializer of individual variables and macros in the
491 # documentation can be controlled using \showinitializer or \hideinitializer
492 # command in the documentation regardless of this setting.
493
494 MAX_INITIALIZER_LINES = 30
495
496 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
497 # at the bottom of the documentation of classes and structs. If set to YES the
498 # list will mention the files that were used to generate the documentation.
499
500 SHOW_USED_FILES = YES
501
502 # If the sources in your project are distributed over multiple directories
503 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
504 # in the documentation. The default is NO.
505
506 SHOW_DIRECTORIES = NO
507
508 # Set the SHOW_FILES tag to NO to disable the generation of the Files page.
509 # This will remove the Files entry from the Quick Index and from the
510 # Folder Tree View (if specified). The default is YES.
511
512 SHOW_FILES = YES
513
514 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the
515 # Namespaces page.
516 # This will remove the Namespaces entry from the Quick Index
517 # and from the Folder Tree View (if specified). The default is YES.
518
519 SHOW_NAMESPACES = YES
520
521 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
522 # doxygen should invoke to get the current version for each file (typically from
523 # the version control system). Doxygen will invoke the program by executing (via
524 # popen()) the command <command> <input-file>, where <command> is the value of
525 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
526 # provided by doxygen. Whatever the program writes to standard output
527 # is used as the file version. See the manual for examples.
528
529 FILE_VERSION_FILTER =
530
531 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
532 # by doxygen. The layout file controls the global structure of the generated
533 # output files in an output format independent way. The create the layout file
534 # that represents doxygen's defaults, run doxygen with the -l option.
535 # You can optionally specify a file name after the option, if omitted
536 # DoxygenLayout.xml will be used as the name of the layout file.
537
538 LAYOUT_FILE =
539
540 #---------------------------------------------------------------------------
541 # configuration options related to warning and progress messages
542 #---------------------------------------------------------------------------
543
544 # The QUIET tag can be used to turn on/off the messages that are generated
545 # by doxygen. Possible values are YES and NO. If left blank NO is used.
546
547 QUIET = NO
548
549 # The WARNINGS tag can be used to turn on/off the warning messages that are
550 # generated by doxygen. Possible values are YES and NO. If left blank
551 # NO is used.
552
553 WARNINGS = YES
554
555 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
556 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
557 # automatically be disabled.
558
559 WARN_IF_UNDOCUMENTED = YES
560
561 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
562 # potential errors in the documentation, such as not documenting some
563 # parameters in a documented function, or documenting parameters that
564 # don't exist or using markup commands wrongly.
565
566 WARN_IF_DOC_ERROR = YES
567
568 # The WARN_NO_PARAMDOC option can be enabled to get warnings for
569 # functions that are documented, but have no documentation for their parameters
570 # or return value. If set to NO (the default) doxygen will only warn about
571 # wrong or incomplete parameter documentation, but not about the absence of
572 # documentation.
573
574 WARN_NO_PARAMDOC = NO
575
576 # The WARN_FORMAT tag determines the format of the warning messages that
577 # doxygen can produce. The string should contain the $file, $line, and $text
578 # tags, which will be replaced by the file and line number from which the
579 # warning originated and the warning text. Optionally the format may contain
580 # $version, which will be replaced by the version of the file (if it could
581 # be obtained via FILE_VERSION_FILTER)
582
583 WARN_FORMAT = "$file:$line: $text"
584
585 # The WARN_LOGFILE tag can be used to specify a file to which warning
586 # and error messages should be written. If left blank the output is written
587 # to stderr.
588
589 WARN_LOGFILE =
590
591 #---------------------------------------------------------------------------
592 # configuration options related to the input files
593 #---------------------------------------------------------------------------
594
595 # The INPUT tag can be used to specify the files and/or directories that contain
596 # documented source files. You may enter file names like "myfile.cpp" or
597 # directories like "/usr/src/myproject". Separate the files or directories
598 # with spaces.
599
600 INPUT = headers/readosm.h \
601 examples/examples.doxy \
602 mainpage.doxy
603
604 # This tag can be used to specify the character encoding of the source files
605 # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
606 # also the default input encoding. Doxygen uses libiconv (or the iconv built
607 # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
608 # the list of possible encodings.
609
610 INPUT_ENCODING = UTF-8
611
612 # If the value of the INPUT tag contains directories, you can use the
613 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
614 # and *.h) to filter out the source-files in the directories. If left
615 # blank the following patterns are tested:
616 # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
617 # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
618 # *.f90 *.f *.for *.vhd *.vhdl
619
620 FILE_PATTERNS =
621
622 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
623 # should be searched for input files as well. Possible values are YES and NO.
624 # If left blank NO is used.
625
626 RECURSIVE = NO
627
628 # The EXCLUDE tag can be used to specify files and/or directories that should
629 # excluded from the INPUT source files. This way you can easily exclude a
630 # subdirectory from a directory tree whose root is specified with the INPUT tag.
631
632 EXCLUDE =
633
634 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
635 # directories that are symbolic links (a Unix file system feature) are excluded
636 # from the input.
637
638 EXCLUDE_SYMLINKS = NO
639
640 # If the value of the INPUT tag contains directories, you can use the
641 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
642 # certain files from those directories. Note that the wildcards are matched
643 # against the file with absolute path, so to exclude all test directories
644 # for example use the pattern */test/*
645
646 EXCLUDE_PATTERNS =
647
648 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
649 # (namespaces, classes, functions, etc.) that should be excluded from the
650 # output. The symbol name can be a fully qualified name, a word, or if the
651 # wildcard * is used, a substring. Examples: ANamespace, AClass,
652 # AClass::ANamespace, ANamespace::*Test
653
654 EXCLUDE_SYMBOLS =
655
656 # The EXAMPLE_PATH tag can be used to specify one or more files or
657 # directories that contain example code fragments that are included (see
658 # the \include command).
659
660 EXAMPLE_PATH = examples
661
662 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
663 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
664 # and *.h) to filter out the source-files in the directories. If left
665 # blank all files are included.
666
667 EXAMPLE_PATTERNS =
668
669 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
670 # searched for input files to be used with the \include or \dontinclude
671 # commands irrespective of the value of the RECURSIVE tag.
672 # Possible values are YES and NO. If left blank NO is used.
673
674 EXAMPLE_RECURSIVE = NO
675
676 # The IMAGE_PATH tag can be used to specify one or more files or
677 # directories that contain image that are included in the documentation (see
678 # the \image command).
679
680 IMAGE_PATH = images
681
682 # The INPUT_FILTER tag can be used to specify a program that doxygen should
683 # invoke to filter for each input file. Doxygen will invoke the filter program
684 # by executing (via popen()) the command <filter> <input-file>, where <filter>
685 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
686 # input file. Doxygen will then use the output that the filter program writes
687 # to standard output.
688 # If FILTER_PATTERNS is specified, this tag will be
689 # ignored.
690
691 INPUT_FILTER =
692
693 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
694 # basis.
695 # Doxygen will compare the file name with each pattern and apply the
696 # filter if there is a match.
697 # The filters are a list of the form:
698 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
699 # info on how filters are used. If FILTER_PATTERNS is empty or if
700 # non of the patterns match the file name, INPUT_FILTER is applied.
701
702 FILTER_PATTERNS =
703
704 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
705 # INPUT_FILTER) will be used to filter the input files when producing source
706 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
707
708 FILTER_SOURCE_FILES = NO
709
710 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
711 # pattern. A pattern will override the setting for FILTER_PATTERN (if any)
712 # and it is also possible to disable source filtering for a specific pattern
713 # using *.ext= (so without naming a filter). This option only has effect when
714 # FILTER_SOURCE_FILES is enabled.
715
716 FILTER_SOURCE_PATTERNS =
717
718 #---------------------------------------------------------------------------
719 # configuration options related to source browsing
720 #---------------------------------------------------------------------------
721
722 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
723 # be generated. Documented entities will be cross-referenced with these sources.
724 # Note: To get rid of all source code in the generated output, make sure also
725 # VERBATIM_HEADERS is set to NO.
726
727 SOURCE_BROWSER = NO
728
729 # Setting the INLINE_SOURCES tag to YES will include the body
730 # of functions and classes directly in the documentation.
731
732 INLINE_SOURCES = NO
733
734 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
735 # doxygen to hide any special comment blocks from generated source code
736 # fragments. Normal C and C++ comments will always remain visible.
737
738 STRIP_CODE_COMMENTS = YES
739
740 # If the REFERENCED_BY_RELATION tag is set to YES
741 # then for each documented function all documented
742 # functions referencing it will be listed.
743
744 REFERENCED_BY_RELATION = NO
745
746 # If the REFERENCES_RELATION tag is set to YES
747 # then for each documented function all documented entities
748 # called/used by that function will be listed.
749
750 REFERENCES_RELATION = NO
751
752 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
753 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
754 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
755 # link to the source code.
756 # Otherwise they will link to the documentation.
757
758 REFERENCES_LINK_SOURCE = YES
759
760 # If the USE_HTAGS tag is set to YES then the references to source code
761 # will point to the HTML generated by the htags(1) tool instead of doxygen
762 # built-in source browser. The htags tool is part of GNU's global source
763 # tagging system (see http://www.gnu.org/software/global/global.html). You
764 # will need version 4.8.6 or higher.
765
766 USE_HTAGS = NO
767
768 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
769 # will generate a verbatim copy of the header file for each class for
770 # which an include is specified. Set to NO to disable this.
771
772 VERBATIM_HEADERS = YES
773
774 #---------------------------------------------------------------------------
775 # configuration options related to the alphabetical class index
776 #---------------------------------------------------------------------------
777
778 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
779 # of all compounds will be generated. Enable this if the project
780 # contains a lot of classes, structs, unions or interfaces.
781
782 ALPHABETICAL_INDEX = YES
783
784 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
785 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
786 # in which this list will be split (can be a number in the range [1..20])
787
788 COLS_IN_ALPHA_INDEX = 5
789
790 # In case all classes in a project start with a common prefix, all
791 # classes will be put under the same header in the alphabetical index.
792 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
793 # should be ignored while generating the index headers.
794
795 IGNORE_PREFIX =
796
797 #---------------------------------------------------------------------------
798 # configuration options related to the HTML output
799 #---------------------------------------------------------------------------
800
801 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
802 # generate HTML output.
803
804 GENERATE_HTML = YES
805
806 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
807 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
808 # put in front of it. If left blank `html' will be used as the default path.
809
810 HTML_OUTPUT = html
811
812 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
813 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
814 # doxygen will generate files with .html extension.
815
816 HTML_FILE_EXTENSION = .html
817
818 # The HTML_HEADER tag can be used to specify a personal HTML header for
819 # each generated HTML page. If it is left blank doxygen will generate a
820 # standard header.
821
822 HTML_HEADER =
823
824 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
825 # each generated HTML page. If it is left blank doxygen will generate a
826 # standard footer.
827
828 HTML_FOOTER =
829
830 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
831 # style sheet that is used by each HTML page. It can be used to
832 # fine-tune the look of the HTML output. If the tag is left blank doxygen
833 # will generate a default style sheet. Note that doxygen will try to copy
834 # the style sheet file to the HTML output directory, so don't put your own
835 # stylesheet in the HTML output directory as well, or it will be erased!
836
837 HTML_STYLESHEET =
838
839 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
840 # Doxygen will adjust the colors in the stylesheet and background images
841 # according to this color. Hue is specified as an angle on a colorwheel,
842 # see http://en.wikipedia.org/wiki/Hue for more information.
843 # For instance the value 0 represents red, 60 is yellow, 120 is green,
844 # 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
845 # The allowed range is 0 to 359.
846
847 HTML_COLORSTYLE_HUE = 220
848
849 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
850 # the colors in the HTML output. For a value of 0 the output will use
851 # grayscales only. A value of 255 will produce the most vivid colors.
852
853 HTML_COLORSTYLE_SAT = 100
854
855 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
856 # the luminance component of the colors in the HTML output. Values below
857 # 100 gradually make the output lighter, whereas values above 100 make
858 # the output darker. The value divided by 100 is the actual gamma applied,
859 # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
860 # and 100 does not change the gamma.
861
862 HTML_COLORSTYLE_GAMMA = 80
863
864 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
865 # page will contain the date and time when the page was generated. Setting
866 # this to NO can help when comparing the output of multiple runs.
867
868 HTML_TIMESTAMP = YES
869
870 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
871 # files or namespaces will be aligned in HTML using tables. If set to
872 # NO a bullet list will be used.
873
874 HTML_ALIGN_MEMBERS = YES
875
876 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
877 # documentation will contain sections that can be hidden and shown after the
878 # page has loaded. For this to work a browser that supports
879 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
880 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
881
882 HTML_DYNAMIC_SECTIONS = NO
883
884 # If the GENERATE_DOCSET tag is set to YES, additional index files
885 # will be generated that can be used as input for Apple's Xcode 3
886 # integrated development environment, introduced with OSX 10.5 (Leopard).
887 # To create a documentation set, doxygen will generate a Makefile in the
888 # HTML output directory. Running make will produce the docset in that
889 # directory and running "make install" will install the docset in
890 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
891 # it at startup.
892 # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
893 # for more information.
894
895 GENERATE_DOCSET = NO
896
897 # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
898 # feed. A documentation feed provides an umbrella under which multiple
899 # documentation sets from a single provider (such as a company or product suite)
900 # can be grouped.
901
902 DOCSET_FEEDNAME = "Doxygen generated docs"
903
904 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
905 # should uniquely identify the documentation set bundle. This should be a
906 # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
907 # will append .docset to the name.
908
909 DOCSET_BUNDLE_ID = org.doxygen.Project
910
911 # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
912 # the documentation publisher. This should be a reverse domain-name style
913 # string, e.g. com.mycompany.MyDocSet.documentation.
914
915 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
916
917 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
918
919 DOCSET_PUBLISHER_NAME = Publisher
920
921 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
922 # will be generated that can be used as input for tools like the
923 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
924 # of the generated HTML documentation.
925
926 GENERATE_HTMLHELP = NO
927
928 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
929 # be used to specify the file name of the resulting .chm file. You
930 # can add a path in front of the file if the result should not be
931 # written to the html output directory.
932
933 CHM_FILE =
934
935 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
936 # be used to specify the location (absolute path including file name) of
937 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
938 # the HTML help compiler on the generated index.hhp.
939
940 HHC_LOCATION =
941
942 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
943 # controls if a separate .chi index file is generated (YES) or that
944 # it should be included in the master .chm file (NO).
945
946 GENERATE_CHI = NO
947
948 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
949 # is used to encode HtmlHelp index (hhk), content (hhc) and project file
950 # content.
951
952 CHM_INDEX_ENCODING =
953
954 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
955 # controls whether a binary table of contents is generated (YES) or a
956 # normal table of contents (NO) in the .chm file.
957
958 BINARY_TOC = NO
959
960 # The TOC_EXPAND flag can be set to YES to add extra items for group members
961 # to the contents of the HTML help documentation and to the tree view.
962
963 TOC_EXPAND = NO
964
965 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
966 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
967 # that can be used as input for Qt's qhelpgenerator to generate a
968 # Qt Compressed Help (.qch) of the generated HTML documentation.
969
970 GENERATE_QHP = NO
971
972 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can
973 # be used to specify the file name of the resulting .qch file.
974 # The path specified is relative to the HTML output folder.
975
976 QCH_FILE =
977
978 # The QHP_NAMESPACE tag specifies the namespace to use when generating
979 # Qt Help Project output. For more information please see
980 # http://doc.trolltech.com/qthelpproject.html#namespace
981
982 QHP_NAMESPACE = org.doxygen.Project
983
984 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
985 # Qt Help Project output. For more information please see
986 # http://doc.trolltech.com/qthelpproject.html#virtual-folders
987
988 QHP_VIRTUAL_FOLDER = doc
989
990 # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
991 # add. For more information please see
992 # http://doc.trolltech.com/qthelpproject.html#custom-filters
993
994 QHP_CUST_FILTER_NAME =
995
996 # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
997 # custom filter to add. For more information please see
998 # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
999 # Qt Help Project / Custom Filters</a>.
1000
1001 QHP_CUST_FILTER_ATTRS =
1002
1003 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1004 # project's
1005 # filter section matches.
1006 # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1007 # Qt Help Project / Filter Attributes</a>.
1008
1009 QHP_SECT_FILTER_ATTRS =
1010
1011 # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
1012 # be used to specify the location of Qt's qhelpgenerator.
1013 # If non-empty doxygen will try to run qhelpgenerator on the generated
1014 # .qhp file.
1015
1016 QHG_LOCATION =
1017
1018 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1019 # will be generated, which together with the HTML files, form an Eclipse help
1020 # plugin. To install this plugin and make it available under the help contents
1021 # menu in Eclipse, the contents of the directory containing the HTML and XML
1022 # files needs to be copied into the plugins directory of eclipse. The name of
1023 # the directory within the plugins directory should be the same as
1024 # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1025 # the help appears.
1026
1027 GENERATE_ECLIPSEHELP = NO
1028
1029 # A unique identifier for the eclipse help plugin. When installing the plugin
1030 # the directory name containing the HTML and XML files should also have
1031 # this name.
1032
1033 ECLIPSE_DOC_ID = org.doxygen.Project
1034
1035 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1036 # top of each HTML page. The value NO (the default) enables the index and
1037 # the value YES disables it.
1038
1039 DISABLE_INDEX = NO
1040
1041 # This tag can be used to set the number of enum values (range [0,1..20])
1042 # that doxygen will group on one line in the generated HTML documentation.
1043 # Note that a value of 0 will completely suppress the enum values from appearing in the overview section.
1044
1045 ENUM_VALUES_PER_LINE = 4
1046
1047 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1048 # structure should be generated to display hierarchical information.
1049 # If the tag value is set to YES, a side panel will be generated
1050 # containing a tree-like index structure (just like the one that
1051 # is generated for HTML Help). For this to work a browser that supports
1052 # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1053 # Windows users are probably better off using the HTML help feature.
1054
1055 GENERATE_TREEVIEW = NO
1056
1057 # By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1058 # and Class Hierarchy pages using a tree view instead of an ordered list.
1059
1060 USE_INLINE_TREES = NO
1061
1062 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1063 # used to set the initial width (in pixels) of the frame in which the tree
1064 # is shown.
1065
1066 TREEVIEW_WIDTH = 250
1067
1068 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1069 # links to external symbols imported via tag files in a separate window.
1070
1071 EXT_LINKS_IN_WINDOW = NO
1072
1073 # Use this tag to change the font size of Latex formulas included
1074 # as images in the HTML documentation. The default is 10. Note that
1075 # when you change the font size after a successful doxygen run you need
1076 # to manually remove any form_*.png images from the HTML output directory
1077 # to force them to be regenerated.
1078
1079 FORMULA_FONTSIZE = 10
1080
1081 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1082 # generated for formulas are transparent PNGs. Transparent PNGs are
1083 # not supported properly for IE 6.0, but are supported on all modern browsers.
1084 # Note that when changing this option you need to delete any form_*.png files
1085 # in the HTML output before the changes have effect.
1086
1087 FORMULA_TRANSPARENT = YES
1088
1089 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1090 # (see http://www.mathjax.org) which uses client side Javascript for the
1091 # rendering instead of using prerendered bitmaps. Use this if you do not
1092 # have LaTeX installed or if you want to formulas look prettier in the HTML
1093 # output. When enabled you also need to install MathJax separately and
1094 # configure the path to it using the MATHJAX_RELPATH option.
1095
1096 USE_MATHJAX = NO
1097
1098 # When MathJax is enabled you need to specify the location relative to the
1099 # HTML output directory using the MATHJAX_RELPATH option. The destination
1100 # directory should contain the MathJax.js script. For instance, if the mathjax
1101 # directory is located at the same level as the HTML output directory, then
1102 # MATHJAX_RELPATH should be ../mathjax. The default value points to the mathjax.org site, so you can quickly see the result without installing
1103 # MathJax, but it is strongly recommended to install a local copy of MathJax
1104 # before deployment.
1105
1106 MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1107
1108 # When the SEARCHENGINE tag is enabled doxygen will generate a search box
1109 # for the HTML output. The underlying search engine uses javascript
1110 # and DHTML and should work on any modern browser. Note that when using
1111 # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1112 # (GENERATE_DOCSET) there is already a search function so this one should
1113 # typically be disabled. For large projects the javascript based search engine
1114 # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1115
1116 SEARCHENGINE = YES
1117
1118 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1119 # implemented using a PHP enabled web server instead of at the web client
1120 # using Javascript. Doxygen will generate the search PHP script and index
1121 # file to put on the web server. The advantage of the server
1122 # based approach is that it scales better to large projects and allows
1123 # full text search. The disadvantages are that it is more difficult to setup
1124 # and does not have live searching capabilities.
1125
1126 SERVER_BASED_SEARCH = NO
1127
1128 #---------------------------------------------------------------------------
1129 # configuration options related to the LaTeX output
1130 #---------------------------------------------------------------------------
1131
1132 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1133 # generate Latex output.
1134
1135 GENERATE_LATEX = YES
1136
1137 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1138 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1139 # put in front of it. If left blank `latex' will be used as the default path.
1140
1141 LATEX_OUTPUT = latex
1142
1143 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1144 # invoked. If left blank `latex' will be used as the default command name.
1145 # Note that when enabling USE_PDFLATEX this option is only used for
1146 # generating bitmaps for formulas in the HTML output, but not in the
1147 # Makefile that is written to the output directory.
1148
1149 LATEX_CMD_NAME = latex
1150
1151 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1152 # generate index for LaTeX. If left blank `makeindex' will be used as the
1153 # default command name.
1154
1155 MAKEINDEX_CMD_NAME = makeindex
1156
1157 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1158 # LaTeX documents. This may be useful for small projects and may help to
1159 # save some trees in general.
1160
1161 COMPACT_LATEX = NO
1162
1163 # The PAPER_TYPE tag can be used to set the paper type that is used
1164 # by the printer. Possible values are: a4, letter, legal and
1165 # executive. If left blank a4wide will be used.
1166
1167 PAPER_TYPE = a4
1168
1169 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1170 # packages that should be included in the LaTeX output.
1171
1172 EXTRA_PACKAGES =
1173
1174 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1175 # the generated latex document. The header should contain everything until
1176 # the first chapter. If it is left blank doxygen will generate a
1177 # standard header. Notice: only use this tag if you know what you are doing!
1178
1179 LATEX_HEADER =
1180
1181 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1182 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1183 # contain links (just like the HTML output) instead of page references
1184 # This makes the output suitable for online browsing using a pdf viewer.
1185
1186 PDF_HYPERLINKS = YES
1187
1188 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1189 # plain latex in the generated Makefile. Set this option to YES to get a
1190 # higher quality PDF documentation.
1191
1192 USE_PDFLATEX = YES
1193
1194 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1195 # command to the generated LaTeX files. This will instruct LaTeX to keep
1196 # running if errors occur, instead of asking the user for help.
1197 # This option is also used when generating formulas in HTML.
1198
1199 LATEX_BATCHMODE = NO
1200
1201 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
1202 # include the index chapters (such as File Index, Compound Index, etc.)
1203 # in the output.
1204
1205 LATEX_HIDE_INDICES = NO
1206
1207 # If LATEX_SOURCE_CODE is set to YES then doxygen will include
1208 # source code with syntax highlighting in the LaTeX output.
1209 # Note that which sources are shown also depends on other settings
1210 # such as SOURCE_BROWSER.
1211
1212 LATEX_SOURCE_CODE = NO
1213
1214 #---------------------------------------------------------------------------
1215 # configuration options related to the RTF output
1216 #---------------------------------------------------------------------------
1217
1218 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1219 # The RTF output is optimized for Word 97 and may not look very pretty with
1220 # other RTF readers or editors.
1221
1222 GENERATE_RTF = NO
1223
1224 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1225 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1226 # put in front of it. If left blank `rtf' will be used as the default path.
1227
1228 RTF_OUTPUT = rtf
1229
1230 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1231 # RTF documents. This may be useful for small projects and may help to
1232 # save some trees in general.
1233
1234 COMPACT_RTF = NO
1235
1236 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1237 # will contain hyperlink fields. The RTF file will
1238 # contain links (just like the HTML output) instead of page references.
1239 # This makes the output suitable for online browsing using WORD or other
1240 # programs which support those fields.
1241 # Note: wordpad (write) and others do not support links.
1242
1243 RTF_HYPERLINKS = NO
1244
1245 # Load stylesheet definitions from file. Syntax is similar to doxygen's
1246 # config file, i.e. a series of assignments. You only have to provide
1247 # replacements, missing definitions are set to their default value.
1248
1249 RTF_STYLESHEET_FILE =
1250
1251 # Set optional variables used in the generation of an rtf document.
1252 # Syntax is similar to doxygen's config file.
1253
1254 RTF_EXTENSIONS_FILE =
1255
1256 #---------------------------------------------------------------------------
1257 # configuration options related to the man page output
1258 #---------------------------------------------------------------------------
1259
1260 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1261 # generate man pages
1262
1263 GENERATE_MAN = NO
1264
1265 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
1266 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1267 # put in front of it. If left blank `man' will be used as the default path.
1268
1269 MAN_OUTPUT = man
1270
1271 # The MAN_EXTENSION tag determines the extension that is added to
1272 # the generated man pages (default is the subroutine's section .3)
1273
1274 MAN_EXTENSION = .3
1275
1276 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1277 # then it will generate one additional man file for each entity
1278 # documented in the real man page(s). These additional files
1279 # only source the real man page, but without them the man command
1280 # would be unable to find the correct page. The default is NO.
1281
1282 MAN_LINKS = NO
1283
1284 #---------------------------------------------------------------------------
1285 # configuration options related to the XML output
1286 #---------------------------------------------------------------------------
1287
1288 # If the GENERATE_XML tag is set to YES Doxygen will
1289 # generate an XML file that captures the structure of
1290 # the code including all documentation.
1291
1292 GENERATE_XML = NO
1293
1294 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
1295 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1296 # put in front of it. If left blank `xml' will be used as the default path.
1297
1298 XML_OUTPUT = xml
1299
1300 # The XML_SCHEMA tag can be used to specify an XML schema,
1301 # which can be used by a validating XML parser to check the
1302 # syntax of the XML files.
1303
1304 XML_SCHEMA =
1305
1306 # The XML_DTD tag can be used to specify an XML DTD,
1307 # which can be used by a validating XML parser to check the
1308 # syntax of the XML files.
1309
1310 XML_DTD =
1311
1312 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1313 # dump the program listings (including syntax highlighting
1314 # and cross-referencing information) to the XML output. Note that
1315 # enabling this will significantly increase the size of the XML output.
1316
1317 XML_PROGRAMLISTING = YES
1318
1319 #---------------------------------------------------------------------------
1320 # configuration options for the AutoGen Definitions output
1321 #---------------------------------------------------------------------------
1322
1323 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1324 # generate an AutoGen Definitions (see autogen.sf.net) file
1325 # that captures the structure of the code including all
1326 # documentation. Note that this feature is still experimental
1327 # and incomplete at the moment.
1328
1329 GENERATE_AUTOGEN_DEF = NO
1330
1331 #---------------------------------------------------------------------------
1332 # configuration options related to the Perl module output
1333 #---------------------------------------------------------------------------
1334
1335 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
1336 # generate a Perl module file that captures the structure of
1337 # the code including all documentation. Note that this
1338 # feature is still experimental and incomplete at the
1339 # moment.
1340
1341 GENERATE_PERLMOD = NO
1342
1343 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1344 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
1345 # to generate PDF and DVI output from the Perl module output.
1346
1347 PERLMOD_LATEX = NO
1348
1349 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1350 # nicely formatted so it can be parsed by a human reader.
1351 # This is useful
1352 # if you want to understand what is going on.
1353 # On the other hand, if this
1354 # tag is set to NO the size of the Perl module output will be much smaller
1355 # and Perl will parse it just the same.
1356
1357 PERLMOD_PRETTY = YES
1358
1359 # The names of the make variables in the generated doxyrules.make file
1360 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1361 # This is useful so different doxyrules.make files included by the same
1362 # Makefile don't overwrite each other's variables.
1363
1364 PERLMOD_MAKEVAR_PREFIX =
1365
1366 #---------------------------------------------------------------------------
1367 # Configuration options related to the preprocessor
1368 #---------------------------------------------------------------------------
1369
1370 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1371 # evaluate all C-preprocessor directives found in the sources and include
1372 # files.
1373
1374 ENABLE_PREPROCESSING = YES
1375
1376 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1377 # names in the source code. If set to NO (the default) only conditional
1378 # compilation will be performed. Macro expansion can be done in a controlled
1379 # way by setting EXPAND_ONLY_PREDEF to YES.
1380
1381 MACRO_EXPANSION = NO
1382
1383 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1384 # then the macro expansion is limited to the macros specified with the
1385 # PREDEFINED and EXPAND_AS_DEFINED tags.
1386
1387 EXPAND_ONLY_PREDEF = NO
1388
1389 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1390 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1391
1392 SEARCH_INCLUDES = YES
1393
1394 # The INCLUDE_PATH tag can be used to specify one or more directories that
1395 # contain include files that are not input files but should be processed by
1396 # the preprocessor.
1397
1398 INCLUDE_PATH =
1399
1400 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1401 # patterns (like *.h and *.hpp) to filter out the header-files in the
1402 # directories. If left blank, the patterns specified with FILE_PATTERNS will
1403 # be used.
1404
1405 INCLUDE_FILE_PATTERNS =
1406
1407 # The PREDEFINED tag can be used to specify one or more macro names that
1408 # are defined before the preprocessor is started (similar to the -D option of
1409 # gcc). The argument of the tag is a list of macros of the form: name
1410 # or name=definition (no spaces). If the definition and the = are
1411 # omitted =1 is assumed. To prevent a macro definition from being
1412 # undefined via #undef or recursively expanded use the := operator
1413 # instead of the = operator.
1414
1415 PREDEFINED = DOXYGEN_SHOULD_SKIP_THIS
1416
1417 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1418 # this tag can be used to specify a list of macro names that should be expanded.
1419 # The macro definition that is found in the sources will be used.
1420 # Use the PREDEFINED tag if you want to use a different macro definition that overrules the definition found in the source code.
1421
1422 EXPAND_AS_DEFINED =
1423
1424 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1425 # doxygen's preprocessor will remove all references to function-like macros
1426 # that are alone on a line, have an all uppercase name, and do not end with a
1427 # semicolon, because these will confuse the parser if not removed.
1428
1429 SKIP_FUNCTION_MACROS = YES
1430
1431 #---------------------------------------------------------------------------
1432 # Configuration::additions related to external references
1433 #---------------------------------------------------------------------------
1434
1435 # The TAGFILES option can be used to specify one or more tagfiles.
1436 # Optionally an initial location of the external documentation
1437 # can be added for each tagfile. The format of a tag file without
1438 # this location is as follows:
1439 #
1440 # TAGFILES = file1 file2 ...
1441 # Adding location for the tag files is done as follows:
1442 #
1443 # TAGFILES = file1=loc1 "file2 = loc2" ...
1444 # where "loc1" and "loc2" can be relative or absolute paths or
1445 # URLs. If a location is present for each tag, the installdox tool
1446 # does not have to be run to correct the links.
1447 # Note that each tag file must have a unique name
1448 # (where the name does NOT include the path)
1449 # If a tag file is not located in the directory in which doxygen
1450 # is run, you must also specify the path to the tagfile here.
1451
1452 TAGFILES =
1453
1454 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1455 # a tag file that is based on the input files it reads.
1456
1457 GENERATE_TAGFILE =
1458
1459 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1460 # in the class index. If set to NO only the inherited external classes
1461 # will be listed.
1462
1463 ALLEXTERNALS = NO
1464
1465 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1466 # in the modules index. If set to NO, only the current project's groups will
1467 # be listed.
1468
1469 EXTERNAL_GROUPS = YES
1470
1471 # The PERL_PATH should be the absolute path and name of the perl script
1472 # interpreter (i.e. the result of `which perl').
1473
1474 PERL_PATH = /usr/bin/perl
1475
1476 #---------------------------------------------------------------------------
1477 # Configuration options related to the dot tool
1478 #---------------------------------------------------------------------------
1479
1480 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1481 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1482 # or super classes. Setting the tag to NO turns the diagrams off. Note that
1483 # this option also works with HAVE_DOT disabled, but it is recommended to
1484 # install and use dot, since it yields more powerful graphs.
1485
1486 CLASS_DIAGRAMS = YES
1487
1488 # You can define message sequence charts within doxygen comments using the \msc
1489 # command. Doxygen will then run the mscgen tool (see
1490 # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1491 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1492 # the mscgen tool resides. If left empty the tool is assumed to be found in the
1493 # default search path.
1494
1495 MSCGEN_PATH =
1496
1497 # If set to YES, the inheritance and collaboration graphs will hide
1498 # inheritance and usage relations if the target is undocumented
1499 # or is not a class.
1500
1501 HIDE_UNDOC_RELATIONS = YES
1502
1503 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1504 # available from the path. This tool is part of Graphviz, a graph visualization
1505 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
1506 # have no effect if this option is set to NO (the default)
1507
1508 HAVE_DOT = YES
1509
1510 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1511 # allowed to run in parallel. When set to 0 (the default) doxygen will
1512 # base this on the number of processors available in the system. You can set it
1513 # explicitly to a value larger than 0 to get control over the balance
1514 # between CPU load and processing speed.
1515
1516 DOT_NUM_THREADS = 0
1517
1518 # By default doxygen will write a font called Helvetica to the output
1519 # directory and reference it in all dot files that doxygen generates.
1520 # When you want a differently looking font you can specify the font name
1521 # using DOT_FONTNAME. You need to make sure dot is able to find the font,
1522 # which can be done by putting it in a standard location or by setting the
1523 # DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1524 # containing the font.
1525
1526 DOT_FONTNAME = Helvetica
1527
1528 # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1529 # The default size is 10pt.
1530
1531 DOT_FONTSIZE = 10
1532
1533 # By default doxygen will tell dot to use the output directory to look for the
1534 # FreeSans.ttf font (which doxygen will put there itself). If you specify a
1535 # different font using DOT_FONTNAME you can set the path where dot
1536 # can find it using this tag.
1537
1538 DOT_FONTPATH =
1539
1540 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1541 # will generate a graph for each documented class showing the direct and
1542 # indirect inheritance relations. Setting this tag to YES will force the
1543 # the CLASS_DIAGRAMS tag to NO.
1544
1545 CLASS_GRAPH = YES
1546
1547 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1548 # will generate a graph for each documented class showing the direct and
1549 # indirect implementation dependencies (inheritance, containment, and
1550 # class references variables) of the class with other documented classes.
1551
1552 COLLABORATION_GRAPH = YES
1553
1554 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1555 # will generate a graph for groups, showing the direct groups dependencies
1556
1557 GROUP_GRAPHS = YES
1558
1559 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1560 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1561 # Language.
1562
1563 UML_LOOK = NO
1564
1565 # If set to YES, the inheritance and collaboration graphs will show the
1566 # relations between templates and their instances.
1567
1568 TEMPLATE_RELATIONS = NO
1569
1570 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1571 # tags are set to YES then doxygen will generate a graph for each documented
1572 # file showing the direct and indirect include dependencies of the file with
1573 # other documented files.
1574
1575 INCLUDE_GRAPH = YES
1576
1577 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1578 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1579 # documented header file showing the documented files that directly or
1580 # indirectly include this file.
1581
1582 INCLUDED_BY_GRAPH = YES
1583
1584 # If the CALL_GRAPH and HAVE_DOT options are set to YES then
1585 # doxygen will generate a call dependency graph for every global function
1586 # or class method. Note that enabling this option will significantly increase
1587 # the time of a run. So in most cases it will be better to enable call graphs
1588 # for selected functions only using the \callgraph command.
1589
1590 CALL_GRAPH = NO
1591
1592 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1593 # doxygen will generate a caller dependency graph for every global function
1594 # or class method. Note that enabling this option will significantly increase
1595 # the time of a run. So in most cases it will be better to enable caller
1596 # graphs for selected functions only using the \callergraph command.
1597
1598 CALLER_GRAPH = NO
1599
1600 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1601 # will generate a graphical hierarchy of all classes instead of a textual one.
1602
1603 GRAPHICAL_HIERARCHY = YES
1604
1605 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1606 # then doxygen will show the dependencies a directory has on other directories
1607 # in a graphical way. The dependency relations are determined by the #include
1608 # relations between the files in the directories.
1609
1610 DIRECTORY_GRAPH = YES
1611
1612 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1613 # generated by dot. Possible values are png, svg, gif or svg.
1614 # If left blank png will be used.
1615
1616 DOT_IMAGE_FORMAT = png
1617
1618 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1619 # found. If left blank, it is assumed the dot tool can be found in the path.
1620
1621 DOT_PATH =
1622
1623 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1624 # contain dot files that are included in the documentation (see the
1625 # \dotfile command).
1626
1627 DOTFILE_DIRS =
1628
1629 # The MSCFILE_DIRS tag can be used to specify one or more directories that
1630 # contain msc files that are included in the documentation (see the
1631 # \mscfile command).
1632
1633 MSCFILE_DIRS =
1634
1635 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1636 # nodes that will be shown in the graph. If the number of nodes in a graph
1637 # becomes larger than this value, doxygen will truncate the graph, which is
1638 # visualized by representing a node as a red box. Note that doxygen if the
1639 # number of direct children of the root node in a graph is already larger than
1640 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1641 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1642
1643 DOT_GRAPH_MAX_NODES = 50
1644
1645 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1646 # graphs generated by dot. A depth value of 3 means that only nodes reachable
1647 # from the root by following a path via at most 3 edges will be shown. Nodes
1648 # that lay further from the root node will be omitted. Note that setting this
1649 # option to 1 or 2 may greatly reduce the computation time needed for large
1650 # code bases. Also note that the size of a graph can be further restricted by
1651 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1652
1653 MAX_DOT_GRAPH_DEPTH = 0
1654
1655 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1656 # background. This is disabled by default, because dot on Windows does not
1657 # seem to support this out of the box. Warning: Depending on the platform used,
1658 # enabling this option may lead to badly anti-aliased labels on the edges of
1659 # a graph (i.e. they become hard to read).
1660
1661 DOT_TRANSPARENT = NO
1662
1663 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1664 # files in one run (i.e. multiple -o and -T options on the command line). This
1665 # makes dot run faster, but since only newer versions of dot (>1.8.10)
1666 # support this, this feature is disabled by default.
1667
1668 DOT_MULTI_TARGETS = YES
1669
1670 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1671 # generate a legend page explaining the meaning of the various boxes and
1672 # arrows in the dot generated graphs.
1673
1674 GENERATE_LEGEND = YES
1675
1676 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1677 # remove the intermediate dot files that are used to generate
1678 # the various graphs.
1679
1680 DOT_CLEANUP = YES
0 Basic Installation
1 ==================
2
3 These are generic installation instructions.
4
5 The `configure' shell script attempts to guess correct values for
6 various system-dependent variables used during compilation. It uses
7 those values to create a `Makefile' in each directory of the package.
8 It may also create one or more `.h' files containing system-dependent
9 definitions. Finally, it creates a shell script `config.status' that
10 you can run in the future to recreate the current configuration, a file
11 `config.cache' that saves the results of its tests to speed up
12 reconfiguring, and a file `config.log' containing compiler output
13 (useful mainly for debugging `configure').
14
15 If you need to do unusual things to compile the package, please try
16 to figure out how `configure' could check whether to do them, and mail
17 diffs or instructions to the address given in the `README' so they can
18 be considered for the next release. If at some point `config.cache'
19 contains results you don't want to keep, you may remove or edit it.
20
21 The file `configure.in' is used to create `configure' by a program
22 called `autoconf'. You only need `configure.in' if you want to change
23 it or regenerate `configure' using a newer version of `autoconf'.
24
25 The simplest way to compile this package is:
26
27 1. `cd' to the directory containing the package's source code and type
28 `./configure' to configure the package for your system. If you're
29 using `csh' on an old version of System V, you might need to type
30 `sh ./configure' instead to prevent `csh' from trying to execute
31 `configure' itself.
32
33 Running `configure' takes awhile. While running, it prints some
34 messages telling which features it is checking for.
35
36 2. Type `make' to compile the package.
37
38 3. Optionally, type `make check' to run any self-tests that come with
39 the package.
40
41 4. Type `make install' to install the programs and any data files and
42 documentation.
43
44 5. You can remove the program binaries and object files from the
45 source code directory by typing `make clean'. To also remove the
46 files that `configure' created (so you can compile the package for
47 a different kind of computer), type `make distclean'. There is
48 also a `make maintainer-clean' target, but that is intended mainly
49 for the package's developers. If you use it, you may have to get
50 all sorts of other programs in order to regenerate files that came
51 with the distribution.
52
53 Compilers and Options
54 =====================
55
56 Some systems require unusual options for compilation or linking that
57 the `configure' script does not know about. You can give `configure'
58 initial values for variables by setting them in the environment. Using
59 a Bourne-compatible shell, you can do that on the command line like
60 this:
61 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
62
63 Or on systems that have the `env' program, you can do it like this:
64 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
65
66 Compiling For Multiple Architectures
67 ====================================
68
69 You can compile the package for more than one kind of computer at the
70 same time, by placing the object files for each architecture in their
71 own directory. To do this, you must use a version of `make' that
72 supports the `VPATH' variable, such as GNU `make'. `cd' to the
73 directory where you want the object files and executables to go and run
74 the `configure' script. `configure' automatically checks for the
75 source code in the directory that `configure' is in and in `..'.
76
77 If you have to use a `make' that does not supports the `VPATH'
78 variable, you have to compile the package for one architecture at a time
79 in the source code directory. After you have installed the package for
80 one architecture, use `make distclean' before reconfiguring for another
81 architecture.
82
83 Installation Names
84 ==================
85
86 By default, `make install' will install the package's files in
87 `/usr/local/bin', `/usr/local/man', etc. You can specify an
88 installation prefix other than `/usr/local' by giving `configure' the
89 option `--prefix=PATH'.
90
91 You can specify separate installation prefixes for
92 architecture-specific files and architecture-independent files. If you
93 give `configure' the option `--exec-prefix=PATH', the package will use
94 PATH as the prefix for installing programs and libraries.
95 Documentation and other data files will still use the regular prefix.
96
97 In addition, if you use an unusual directory layout you can give
98 options like `--bindir=PATH' to specify different values for particular
99 kinds of files. Run `configure --help' for a list of the directories
100 you can set and what kinds of files go in them.
101
102 If the package supports it, you can cause programs to be installed
103 with an extra prefix or suffix on their names by giving `configure' the
104 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
105
106 Optional Features
107 =================
108
109 Some packages pay attention to `--enable-FEATURE' options to
110 `configure', where FEATURE indicates an optional part of the package.
111 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
112 is something like `gnu-as' or `x' (for the X Window System). The
113 `README' should mention any `--enable-' and `--with-' options that the
114 package recognizes.
115
116 For packages that use the X Window System, `configure' can usually
117 find the X include and library files automatically, but if it doesn't,
118 you can use the `configure' options `--x-includes=DIR' and
119 `--x-libraries=DIR' to specify their locations.
120
121 Specifying the System Type
122 ==========================
123
124 There may be some features `configure' can not figure out
125 automatically, but needs to determine by the type of host the package
126 will run on. Usually `configure' can figure that out, but if it prints
127 a message saying it can not guess the host type, give it the
128 `--host=TYPE' option. TYPE can either be a short name for the system
129 type, such as `sun4', or a canonical name with three fields:
130 CPU-COMPANY-SYSTEM
131
132 See the file `config.sub' for the possible values of each field. If
133 `config.sub' isn't included in this package, then this package doesn't
134 need to know the host type.
135
136 If you are building compiler tools for cross-compiling, you can also
137 use the `--target=TYPE' option to select the type of system they will
138 produce code for and the `--build=TYPE' option to select the type of
139 system on which you are compiling the package.
140
141 Sharing Defaults
142 ================
143
144 If you want to set default values for `configure' scripts to share,
145 you can create a site shell script called `config.site' that gives
146 default values for variables like `CC', `cache_file', and `prefix'.
147 `configure' looks for `PREFIX/share/config.site' if it exists, then
148 `PREFIX/etc/config.site' if it exists. Or, you can set the
149 `CONFIG_SITE' environment variable to the location of the site script.
150 A warning: not all `configure' scripts look for a site script.
151
152 Operation Controls
153 ==================
154
155 `configure' recognizes the following options to control how it
156 operates.
157
158 `--cache-file=FILE'
159 Use and save the results of the tests in FILE instead of
160 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
161 debugging `configure'.
162
163 `--help'
164 Print a summary of the options to `configure', and exit.
165
166 `--quiet'
167 `--silent'
168 `-q'
169 Do not print messages saying which checks are being made. To
170 suppress all normal output, redirect it to `/dev/null' (any error
171 messages will still be shown).
172
173 `--srcdir=DIR'
174 Look for the package's source code in directory DIR. Usually
175 `configure' can determine that directory automatically.
176
177 `--version'
178 Print the version of Autoconf used to generate the `configure'
179 script, and exit.
180
181 `configure' also accepts some other, not widely useful, options.
182
0 ACLOCAL_AMFLAGS = -I m4
1
2 SUBDIRS = headers src tests examples
3
4 EXTRA_DIST = makefile.vc nmake.opt mainpage.doxy
5
6 AUTOMAKE_OPTIONS = dist-zip
7
8 pkgconfigdir = $(libdir)/pkgconfig
9 pkgconfig_DATA = readosm.pc
10
11 coverage-init:
12 lcov --directory . --capture --initial --output-file readosm_cov.info
13
14 coverage::
15 lcov --directory . --output-file readosm_cov.info --capture
16 genhtml -o covresults readosm_cov.info
17
18 MOSTLYCLEANFILES = readosm_cov.info
0 # Makefile.in generated by automake 1.11.1 from Makefile.am.
1 # @configure_input@
2
3 # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
4 # 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation,
5 # Inc.
6 # This Makefile.in is free software; the Free Software Foundation
7 # gives unlimited permission to copy and/or distribute it,
8 # with or without modifications, as long as this notice is preserved.
9
10 # This program is distributed in the hope that it will be useful,
11 # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
12 # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
13 # PARTICULAR PURPOSE.
14
15 @SET_MAKE@
16
17 VPATH = @srcdir@
18 pkgdatadir = $(datadir)/@PACKAGE@
19 pkgincludedir = $(includedir)/@PACKAGE@
20 pkglibdir = $(libdir)/@PACKAGE@
21 pkglibexecdir = $(libexecdir)/@PACKAGE@
22 am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
23 install_sh_DATA = $(install_sh) -c -m 644
24 install_sh_PROGRAM = $(install_sh) -c
25 install_sh_SCRIPT = $(install_sh) -c
26 INSTALL_HEADER = $(INSTALL_DATA)
27 transform = $(program_transform_name)
28 NORMAL_INSTALL = :
29 PRE_INSTALL = :
30 POST_INSTALL = :
31 NORMAL_UNINSTALL = :
32 PRE_UNINSTALL = :
33 POST_UNINSTALL = :
34 build_triplet = @build@
35 host_triplet = @host@
36 subdir = .
37 DIST_COMMON = README $(am__configure_deps) $(srcdir)/Doxyfile.in \
38 $(srcdir)/Makefile.am $(srcdir)/Makefile.in \
39 $(srcdir)/config.h.in $(srcdir)/readosm.pc.in \
40 $(top_srcdir)/configure AUTHORS COPYING ChangeLog INSTALL NEWS \
41 config.guess config.sub depcomp install-sh ltmain.sh missing
42 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
43 am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
44 $(top_srcdir)/m4/ltoptions.m4 $(top_srcdir)/m4/ltsugar.m4 \
45 $(top_srcdir)/m4/ltversion.m4 $(top_srcdir)/m4/lt~obsolete.m4 \
46 $(top_srcdir)/configure.ac
47 am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
48 $(ACLOCAL_M4)
49 am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
50 configure.lineno config.status.lineno
51 mkinstalldirs = $(install_sh) -d
52 CONFIG_HEADER = config.h
53 CONFIG_CLEAN_FILES = Doxyfile readosm.pc
54 CONFIG_CLEAN_VPATH_FILES =
55 SOURCES =
56 DIST_SOURCES =
57 RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
58 html-recursive info-recursive install-data-recursive \
59 install-dvi-recursive install-exec-recursive \
60 install-html-recursive install-info-recursive \
61 install-pdf-recursive install-ps-recursive install-recursive \
62 installcheck-recursive installdirs-recursive pdf-recursive \
63 ps-recursive uninstall-recursive
64 am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
65 am__vpath_adj = case $$p in \
66 $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
67 *) f=$$p;; \
68 esac;
69 am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
70 am__install_max = 40
71 am__nobase_strip_setup = \
72 srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
73 am__nobase_strip = \
74 for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
75 am__nobase_list = $(am__nobase_strip_setup); \
76 for p in $$list; do echo "$$p $$p"; done | \
77 sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
78 $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
79 if (++n[$$2] == $(am__install_max)) \
80 { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
81 END { for (dir in files) print dir, files[dir] }'
82 am__base_list = \
83 sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
84 sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
85 am__installdirs = "$(DESTDIR)$(pkgconfigdir)"
86 DATA = $(pkgconfig_DATA)
87 RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \
88 distclean-recursive maintainer-clean-recursive
89 AM_RECURSIVE_TARGETS = $(RECURSIVE_TARGETS:-recursive=) \
90 $(RECURSIVE_CLEAN_TARGETS:-recursive=) tags TAGS ctags CTAGS \
91 distdir dist dist-all distcheck
92 ETAGS = etags
93 CTAGS = ctags
94 DIST_SUBDIRS = $(SUBDIRS)
95 DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
96 distdir = $(PACKAGE)-$(VERSION)
97 top_distdir = $(distdir)
98 am__remove_distdir = \
99 { test ! -d "$(distdir)" \
100 || { find "$(distdir)" -type d ! -perm -200 -exec chmod u+w {} ';' \
101 && rm -fr "$(distdir)"; }; }
102 am__relativize = \
103 dir0=`pwd`; \
104 sed_first='s,^\([^/]*\)/.*$$,\1,'; \
105 sed_rest='s,^[^/]*/*,,'; \
106 sed_last='s,^.*/\([^/]*\)$$,\1,'; \
107 sed_butlast='s,/*[^/]*$$,,'; \
108 while test -n "$$dir1"; do \
109 first=`echo "$$dir1" | sed -e "$$sed_first"`; \
110 if test "$$first" != "."; then \
111 if test "$$first" = ".."; then \
112 dir2=`echo "$$dir0" | sed -e "$$sed_last"`/"$$dir2"; \
113 dir0=`echo "$$dir0" | sed -e "$$sed_butlast"`; \
114 else \
115 first2=`echo "$$dir2" | sed -e "$$sed_first"`; \
116 if test "$$first2" = "$$first"; then \
117 dir2=`echo "$$dir2" | sed -e "$$sed_rest"`; \
118 else \
119 dir2="../$$dir2"; \
120 fi; \
121 dir0="$$dir0"/"$$first"; \
122 fi; \
123 fi; \
124 dir1=`echo "$$dir1" | sed -e "$$sed_rest"`; \
125 done; \
126 reldir="$$dir2"
127 DIST_ARCHIVES = $(distdir).tar.gz $(distdir).zip
128 GZIP_ENV = --best
129 distuninstallcheck_listfiles = find . -type f -print
130 distcleancheck_listfiles = find . -type f -print
131 ACLOCAL = @ACLOCAL@
132 AMTAR = @AMTAR@
133 AR = @AR@
134 AS = @AS@
135 AUTOCONF = @AUTOCONF@
136 AUTOHEADER = @AUTOHEADER@
137 AUTOMAKE = @AUTOMAKE@
138 AWK = @AWK@
139 CC = @CC@
140 CCDEPMODE = @CCDEPMODE@
141 CFLAGS = @CFLAGS@
142 CPP = @CPP@
143 CPPFLAGS = @CPPFLAGS@
144 CXX = @CXX@
145 CXXCPP = @CXXCPP@
146 CXXDEPMODE = @CXXDEPMODE@
147 CXXFLAGS = @CXXFLAGS@
148 CYGPATH_W = @CYGPATH_W@
149 DEFS = @DEFS@
150 DEPDIR = @DEPDIR@
151 DLLTOOL = @DLLTOOL@
152 DSYMUTIL = @DSYMUTIL@
153 DUMPBIN = @DUMPBIN@
154 ECHO_C = @ECHO_C@
155 ECHO_N = @ECHO_N@
156 ECHO_T = @ECHO_T@
157 EGREP = @EGREP@
158 EXEEXT = @EXEEXT@
159 FGREP = @FGREP@
160 GREP = @GREP@
161 INSTALL = @INSTALL@
162 INSTALL_DATA = @INSTALL_DATA@
163 INSTALL_PROGRAM = @INSTALL_PROGRAM@
164 INSTALL_SCRIPT = @INSTALL_SCRIPT@
165 INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
166 LD = @LD@
167 LDFLAGS = @LDFLAGS@
168 LIBOBJS = @LIBOBJS@
169 LIBS = @LIBS@
170 LIBTOOL = @LIBTOOL@
171 LIPO = @LIPO@
172 LN_S = @LN_S@
173 LTLIBOBJS = @LTLIBOBJS@
174 MAINT = @MAINT@
175 MAKEINFO = @MAKEINFO@
176 MANIFEST_TOOL = @MANIFEST_TOOL@
177 MKDIR_P = @MKDIR_P@
178 NM = @NM@
179 NMEDIT = @NMEDIT@
180 OBJDUMP = @OBJDUMP@
181 OBJEXT = @OBJEXT@
182 OTOOL = @OTOOL@
183 OTOOL64 = @OTOOL64@
184 PACKAGE = @PACKAGE@
185 PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
186 PACKAGE_NAME = @PACKAGE_NAME@
187 PACKAGE_STRING = @PACKAGE_STRING@
188 PACKAGE_TARNAME = @PACKAGE_TARNAME@
189 PACKAGE_URL = @PACKAGE_URL@
190 PACKAGE_VERSION = @PACKAGE_VERSION@
191 PATH_SEPARATOR = @PATH_SEPARATOR@
192 RANLIB = @RANLIB@
193 SED = @SED@
194 SET_MAKE = @SET_MAKE@
195 SHELL = @SHELL@
196 STRIP = @STRIP@
197 VERSION = @VERSION@
198 abs_builddir = @abs_builddir@
199 abs_srcdir = @abs_srcdir@
200 abs_top_builddir = @abs_top_builddir@
201 abs_top_srcdir = @abs_top_srcdir@
202 ac_ct_AR = @ac_ct_AR@
203 ac_ct_CC = @ac_ct_CC@
204 ac_ct_CXX = @ac_ct_CXX@
205 ac_ct_DUMPBIN = @ac_ct_DUMPBIN@
206 am__include = @am__include@
207 am__leading_dot = @am__leading_dot@
208 am__quote = @am__quote@
209 am__tar = @am__tar@
210 am__untar = @am__untar@
211 bindir = @bindir@
212 build = @build@
213 build_alias = @build_alias@
214 build_cpu = @build_cpu@
215 build_os = @build_os@
216 build_vendor = @build_vendor@
217 builddir = @builddir@
218 datadir = @datadir@
219 datarootdir = @datarootdir@
220 docdir = @docdir@
221 dvidir = @dvidir@
222 exec_prefix = @exec_prefix@
223 host = @host@
224 host_alias = @host_alias@
225 host_cpu = @host_cpu@
226 host_os = @host_os@
227 host_vendor = @host_vendor@
228 htmldir = @htmldir@
229 includedir = @includedir@
230 infodir = @infodir@
231 install_sh = @install_sh@
232 libdir = @libdir@
233 libexecdir = @libexecdir@
234 localedir = @localedir@
235 localstatedir = @localstatedir@
236 mandir = @mandir@
237 mkdir_p = @mkdir_p@
238 oldincludedir = @oldincludedir@
239 pdfdir = @pdfdir@
240 prefix = @prefix@
241 program_transform_name = @program_transform_name@
242 psdir = @psdir@
243 sbindir = @sbindir@
244 sharedstatedir = @sharedstatedir@
245 srcdir = @srcdir@
246 sysconfdir = @sysconfdir@
247 target_alias = @target_alias@
248 top_build_prefix = @top_build_prefix@
249 top_builddir = @top_builddir@
250 top_srcdir = @top_srcdir@
251 ACLOCAL_AMFLAGS = -I m4
252 SUBDIRS = headers src tests examples
253 EXTRA_DIST = makefile.vc nmake.opt mainpage.doxy
254 AUTOMAKE_OPTIONS = dist-zip
255 pkgconfigdir = $(libdir)/pkgconfig
256 pkgconfig_DATA = readosm.pc
257 MOSTLYCLEANFILES = readosm_cov.info
258 all: config.h
259 $(MAKE) $(AM_MAKEFLAGS) all-recursive
260
261 .SUFFIXES:
262 am--refresh:
263 @:
264 $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps)
265 @for dep in $?; do \
266 case '$(am__configure_deps)' in \
267 *$$dep*) \
268 echo ' cd $(srcdir) && $(AUTOMAKE) --gnu'; \
269 $(am__cd) $(srcdir) && $(AUTOMAKE) --gnu \
270 && exit 0; \
271 exit 1;; \
272 esac; \
273 done; \
274 echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu Makefile'; \
275 $(am__cd) $(top_srcdir) && \
276 $(AUTOMAKE) --gnu Makefile
277 .PRECIOUS: Makefile
278 Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
279 @case '$?' in \
280 *config.status*) \
281 echo ' $(SHELL) ./config.status'; \
282 $(SHELL) ./config.status;; \
283 *) \
284 echo ' cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)'; \
285 cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe);; \
286 esac;
287
288 $(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
289 $(SHELL) ./config.status --recheck
290
291 $(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps)
292 $(am__cd) $(srcdir) && $(AUTOCONF)
293 $(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps)
294 $(am__cd) $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
295 $(am__aclocal_m4_deps):
296
297 config.h: stamp-h1
298 @if test ! -f $@; then \
299 rm -f stamp-h1; \
300 $(MAKE) $(AM_MAKEFLAGS) stamp-h1; \
301 else :; fi
302
303 stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status
304 @rm -f stamp-h1
305 cd $(top_builddir) && $(SHELL) ./config.status config.h
306 $(srcdir)/config.h.in: @MAINTAINER_MODE_TRUE@ $(am__configure_deps)
307 ($(am__cd) $(top_srcdir) && $(AUTOHEADER))
308 rm -f stamp-h1
309 touch $@
310
311 distclean-hdr:
312 -rm -f config.h stamp-h1
313 Doxyfile: $(top_builddir)/config.status $(srcdir)/Doxyfile.in
314 cd $(top_builddir) && $(SHELL) ./config.status $@
315 readosm.pc: $(top_builddir)/config.status $(srcdir)/readosm.pc.in
316 cd $(top_builddir) && $(SHELL) ./config.status $@
317
318 mostlyclean-libtool:
319 -rm -f *.lo
320
321 clean-libtool:
322 -rm -rf .libs _libs
323
324 distclean-libtool:
325 -rm -f libtool config.lt
326 install-pkgconfigDATA: $(pkgconfig_DATA)
327 @$(NORMAL_INSTALL)
328 test -z "$(pkgconfigdir)" || $(MKDIR_P) "$(DESTDIR)$(pkgconfigdir)"
329 @list='$(pkgconfig_DATA)'; test -n "$(pkgconfigdir)" || list=; \
330 for p in $$list; do \
331 if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
332 echo "$$d$$p"; \
333 done | $(am__base_list) | \
334 while read files; do \
335 echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(pkgconfigdir)'"; \
336 $(INSTALL_DATA) $$files "$(DESTDIR)$(pkgconfigdir)" || exit $$?; \
337 done
338
339 uninstall-pkgconfigDATA:
340 @$(NORMAL_UNINSTALL)
341 @list='$(pkgconfig_DATA)'; test -n "$(pkgconfigdir)" || list=; \
342 files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
343 test -n "$$files" || exit 0; \
344 echo " ( cd '$(DESTDIR)$(pkgconfigdir)' && rm -f" $$files ")"; \
345 cd "$(DESTDIR)$(pkgconfigdir)" && rm -f $$files
346
347 # This directory's subdirectories are mostly independent; you can cd
348 # into them and run `make' without going through this Makefile.
349 # To change the values of `make' variables: instead of editing Makefiles,
350 # (1) if the variable is set in `config.status', edit `config.status'
351 # (which will cause the Makefiles to be regenerated when you run `make');
352 # (2) otherwise, pass the desired values on the `make' command line.
353 $(RECURSIVE_TARGETS):
354 @fail= failcom='exit 1'; \
355 for f in x $$MAKEFLAGS; do \
356 case $$f in \
357 *=* | --[!k]*);; \
358 *k*) failcom='fail=yes';; \
359 esac; \
360 done; \
361 dot_seen=no; \
362 target=`echo $@ | sed s/-recursive//`; \
363 list='$(SUBDIRS)'; for subdir in $$list; do \
364 echo "Making $$target in $$subdir"; \
365 if test "$$subdir" = "."; then \
366 dot_seen=yes; \
367 local_target="$$target-am"; \
368 else \
369 local_target="$$target"; \
370 fi; \
371 ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
372 || eval $$failcom; \
373 done; \
374 if test "$$dot_seen" = "no"; then \
375 $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
376 fi; test -z "$$fail"
377
378 $(RECURSIVE_CLEAN_TARGETS):
379 @fail= failcom='exit 1'; \
380 for f in x $$MAKEFLAGS; do \
381 case $$f in \
382 *=* | --[!k]*);; \
383 *k*) failcom='fail=yes';; \
384 esac; \
385 done; \
386 dot_seen=no; \
387 case "$@" in \
388 distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
389 *) list='$(SUBDIRS)' ;; \
390 esac; \
391 rev=''; for subdir in $$list; do \
392 if test "$$subdir" = "."; then :; else \
393 rev="$$subdir $$rev"; \
394 fi; \
395 done; \
396 rev="$$rev ."; \
397 target=`echo $@ | sed s/-recursive//`; \
398 for subdir in $$rev; do \
399 echo "Making $$target in $$subdir"; \
400 if test "$$subdir" = "."; then \
401 local_target="$$target-am"; \
402 else \
403 local_target="$$target"; \
404 fi; \
405 ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
406 || eval $$failcom; \
407 done && test -z "$$fail"
408 tags-recursive:
409 list='$(SUBDIRS)'; for subdir in $$list; do \
410 test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
411 done
412 ctags-recursive:
413 list='$(SUBDIRS)'; for subdir in $$list; do \
414 test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
415 done
416
417 ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
418 list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
419 unique=`for i in $$list; do \
420 if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
421 done | \
422 $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
423 END { if (nonempty) { for (i in files) print i; }; }'`; \
424 mkid -fID $$unique
425 tags: TAGS
426
427 TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \
428 $(TAGS_FILES) $(LISP)
429 set x; \
430 here=`pwd`; \
431 if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
432 include_option=--etags-include; \
433 empty_fix=.; \
434 else \
435 include_option=--include; \
436 empty_fix=; \
437 fi; \
438 list='$(SUBDIRS)'; for subdir in $$list; do \
439 if test "$$subdir" = .; then :; else \
440 test ! -f $$subdir/TAGS || \
441 set "$$@" "$$include_option=$$here/$$subdir/TAGS"; \
442 fi; \
443 done; \
444 list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \
445 unique=`for i in $$list; do \
446 if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
447 done | \
448 $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
449 END { if (nonempty) { for (i in files) print i; }; }'`; \
450 shift; \
451 if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \
452 test -n "$$unique" || unique=$$empty_fix; \
453 if test $$# -gt 0; then \
454 $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
455 "$$@" $$unique; \
456 else \
457 $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
458 $$unique; \
459 fi; \
460 fi
461 ctags: CTAGS
462 CTAGS: ctags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \
463 $(TAGS_FILES) $(LISP)
464 list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \
465 unique=`for i in $$list; do \
466 if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
467 done | \
468 $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
469 END { if (nonempty) { for (i in files) print i; }; }'`; \
470 test -z "$(CTAGS_ARGS)$$unique" \
471 || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
472 $$unique
473
474 GTAGS:
475 here=`$(am__cd) $(top_builddir) && pwd` \
476 && $(am__cd) $(top_srcdir) \
477 && gtags -i $(GTAGS_ARGS) "$$here"
478
479 distclean-tags:
480 -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
481
482 distdir: $(DISTFILES)
483 $(am__remove_distdir)
484 test -d "$(distdir)" || mkdir "$(distdir)"
485 @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
486 topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
487 list='$(DISTFILES)'; \
488 dist_files=`for file in $$list; do echo $$file; done | \
489 sed -e "s|^$$srcdirstrip/||;t" \
490 -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
491 case $$dist_files in \
492 */*) $(MKDIR_P) `echo "$$dist_files" | \
493 sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
494 sort -u` ;; \
495 esac; \
496 for file in $$dist_files; do \
497 if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
498 if test -d $$d/$$file; then \
499 dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
500 if test -d "$(distdir)/$$file"; then \
501 find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
502 fi; \
503 if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
504 cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
505 find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
506 fi; \
507 cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
508 else \
509 test -f "$(distdir)/$$file" \
510 || cp -p $$d/$$file "$(distdir)/$$file" \
511 || exit 1; \
512 fi; \
513 done
514 @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
515 if test "$$subdir" = .; then :; else \
516 test -d "$(distdir)/$$subdir" \
517 || $(MKDIR_P) "$(distdir)/$$subdir" \
518 || exit 1; \
519 fi; \
520 done
521 @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
522 if test "$$subdir" = .; then :; else \
523 dir1=$$subdir; dir2="$(distdir)/$$subdir"; \
524 $(am__relativize); \
525 new_distdir=$$reldir; \
526 dir1=$$subdir; dir2="$(top_distdir)"; \
527 $(am__relativize); \
528 new_top_distdir=$$reldir; \
529 echo " (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) top_distdir="$$new_top_distdir" distdir="$$new_distdir" \\"; \
530 echo " am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)"; \
531 ($(am__cd) $$subdir && \
532 $(MAKE) $(AM_MAKEFLAGS) \
533 top_distdir="$$new_top_distdir" \
534 distdir="$$new_distdir" \
535 am__remove_distdir=: \
536 am__skip_length_check=: \
537 am__skip_mode_fix=: \
538 distdir) \
539 || exit 1; \
540 fi; \
541 done
542 -test -n "$(am__skip_mode_fix)" \
543 || find "$(distdir)" -type d ! -perm -755 \
544 -exec chmod u+rwx,go+rx {} \; -o \
545 ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
546 ! -type d ! -perm -400 -exec chmod a+r {} \; -o \
547 ! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \
548 || chmod -R a+r "$(distdir)"
549 dist-gzip: distdir
550 tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
551 $(am__remove_distdir)
552
553 dist-bzip2: distdir
554 tardir=$(distdir) && $(am__tar) | bzip2 -9 -c >$(distdir).tar.bz2
555 $(am__remove_distdir)
556
557 dist-lzma: distdir
558 tardir=$(distdir) && $(am__tar) | lzma -9 -c >$(distdir).tar.lzma
559 $(am__remove_distdir)
560
561 dist-xz: distdir
562 tardir=$(distdir) && $(am__tar) | xz -c >$(distdir).tar.xz
563 $(am__remove_distdir)
564
565 dist-tarZ: distdir
566 tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z
567 $(am__remove_distdir)
568
569 dist-shar: distdir
570 shar $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).shar.gz
571 $(am__remove_distdir)
572 dist-zip: distdir
573 -rm -f $(distdir).zip
574 zip -rq $(distdir).zip $(distdir)
575 $(am__remove_distdir)
576
577 dist dist-all: distdir
578 tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
579 -rm -f $(distdir).zip
580 zip -rq $(distdir).zip $(distdir)
581 $(am__remove_distdir)
582
583 # This target untars the dist file and tries a VPATH configuration. Then
584 # it guarantees that the distribution is self-contained by making another
585 # tarfile.
586 distcheck: dist
587 case '$(DIST_ARCHIVES)' in \
588 *.tar.gz*) \
589 GZIP=$(GZIP_ENV) gzip -dc $(distdir).tar.gz | $(am__untar) ;;\
590 *.tar.bz2*) \
591 bzip2 -dc $(distdir).tar.bz2 | $(am__untar) ;;\
592 *.tar.lzma*) \
593 lzma -dc $(distdir).tar.lzma | $(am__untar) ;;\
594 *.tar.xz*) \
595 xz -dc $(distdir).tar.xz | $(am__untar) ;;\
596 *.tar.Z*) \
597 uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
598 *.shar.gz*) \
599 GZIP=$(GZIP_ENV) gzip -dc $(distdir).shar.gz | unshar ;;\
600 *.zip*) \
601 unzip $(distdir).zip ;;\
602 esac
603 chmod -R a-w $(distdir); chmod a+w $(distdir)
604 mkdir $(distdir)/_build
605 mkdir $(distdir)/_inst
606 chmod a-w $(distdir)
607 test -d $(distdir)/_build || exit 0; \
608 dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \
609 && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \
610 && am__cwd=`pwd` \
611 && $(am__cd) $(distdir)/_build \
612 && ../configure --srcdir=.. --prefix="$$dc_install_base" \
613 $(DISTCHECK_CONFIGURE_FLAGS) \
614 && $(MAKE) $(AM_MAKEFLAGS) \
615 && $(MAKE) $(AM_MAKEFLAGS) dvi \
616 && $(MAKE) $(AM_MAKEFLAGS) check \
617 && $(MAKE) $(AM_MAKEFLAGS) install \
618 && $(MAKE) $(AM_MAKEFLAGS) installcheck \
619 && $(MAKE) $(AM_MAKEFLAGS) uninstall \
620 && $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \
621 distuninstallcheck \
622 && chmod -R a-w "$$dc_install_base" \
623 && ({ \
624 (cd ../.. && umask 077 && mkdir "$$dc_destdir") \
625 && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \
626 && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \
627 && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \
628 distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \
629 } || { rm -rf "$$dc_destdir"; exit 1; }) \
630 && rm -rf "$$dc_destdir" \
631 && $(MAKE) $(AM_MAKEFLAGS) dist \
632 && rm -rf $(DIST_ARCHIVES) \
633 && $(MAKE) $(AM_MAKEFLAGS) distcleancheck \
634 && cd "$$am__cwd" \
635 || exit 1
636 $(am__remove_distdir)
637 @(echo "$(distdir) archives ready for distribution: "; \
638 list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \
639 sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x'
640 distuninstallcheck:
641 @$(am__cd) '$(distuninstallcheck_dir)' \
642 && test `$(distuninstallcheck_listfiles) | wc -l` -le 1 \
643 || { echo "ERROR: files left after uninstall:" ; \
644 if test -n "$(DESTDIR)"; then \
645 echo " (check DESTDIR support)"; \
646 fi ; \
647 $(distuninstallcheck_listfiles) ; \
648 exit 1; } >&2
649 distcleancheck: distclean
650 @if test '$(srcdir)' = . ; then \
651 echo "ERROR: distcleancheck can only run from a VPATH build" ; \
652 exit 1 ; \
653 fi
654 @test `$(distcleancheck_listfiles) | wc -l` -eq 0 \
655 || { echo "ERROR: files left in build directory after distclean:" ; \
656 $(distcleancheck_listfiles) ; \
657 exit 1; } >&2
658 check-am: all-am
659 check: check-recursive
660 all-am: Makefile $(DATA) config.h
661 installdirs: installdirs-recursive
662 installdirs-am:
663 for dir in "$(DESTDIR)$(pkgconfigdir)"; do \
664 test -z "$$dir" || $(MKDIR_P) "$$dir"; \
665 done
666 install: install-recursive
667 install-exec: install-exec-recursive
668 install-data: install-data-recursive
669 uninstall: uninstall-recursive
670
671 install-am: all-am
672 @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
673
674 installcheck: installcheck-recursive
675