Package list libhdate / b46e66a
New upstream version 1.6 Lior Kaplan 3 years ago
1088 changed file(s) with 79362 addition(s) and 587487 deletion(s). Raw diff Collapse all Expand all
+0
-324
1.3.0/ABOUT-NLS less more
0 Notes on the Free Translation Project
1 *************************************
2
3 Free software is going international! The Free Translation Project
4 is a way to get maintainers of free software, translators, and users all
5 together, so that will gradually become able to speak many languages.
6 A few packages already provide translations for their messages.
7
8 If you found this `ABOUT-NLS' file inside a distribution, you may
9 assume that the distributed package does use GNU `gettext' internally,
10 itself available at your nearest GNU archive site. But you do _not_
11 need to install GNU `gettext' prior to configuring, installing or using
12 this package with messages translated.
13
14 Installers will find here some useful hints. These notes also
15 explain how users should proceed for getting the programs to use the
16 available translations. They tell how people wanting to contribute and
17 work at translations should contact the appropriate team.
18
19 When reporting bugs in the `intl/' directory or bugs which may be
20 related to internationalization, you should tell about the version of
21 `gettext' which is used. The information can be found in the
22 `intl/VERSION' file, in internationalized packages.
23
24 Quick configuration advice
25 ==========================
26
27 If you want to exploit the full power of internationalization, you
28 should configure it using
29
30 ./configure --with-included-gettext
31
32 to force usage of internationalizing routines provided within this
33 package, despite the existence of internationalizing capabilities in the
34 operating system where this package is being installed. So far, only
35 the `gettext' implementation in the GNU C library version 2 provides as
36 many features (such as locale alias, message inheritance, automatic
37 charset conversion or plural form handling) as the implementation here.
38 It is also not possible to offer this additional functionality on top
39 of a `catgets' implementation. Future versions of GNU `gettext' will
40 very likely convey even more functionality. So it might be a good idea
41 to change to GNU `gettext' as soon as possible.
42
43 So you need _not_ provide this option if you are using GNU libc 2 or
44 you have installed a recent copy of the GNU gettext package with the
45 included `libintl'.
46
47 INSTALL Matters
48 ===============
49
50 Some packages are "localizable" when properly installed; the
51 programs they contain can be made to speak your own native language.
52 Most such packages use GNU `gettext'. Other packages have their own
53 ways to internationalization, predating GNU `gettext'.
54
55 By default, this package will be installed to allow translation of
56 messages. It will automatically detect whether the system already
57 provides the GNU `gettext' functions. If not, the GNU `gettext' own
58 library will be used. This library is wholly contained within this
59 package, usually in the `intl/' subdirectory, so prior installation of
60 the GNU `gettext' package is _not_ required. Installers may use
61 special options at configuration time for changing the default
62 behaviour. The commands:
63
64 ./configure --with-included-gettext
65 ./configure --disable-nls
66
67 will respectively bypass any pre-existing `gettext' to use the
68 internationalizing routines provided within this package, or else,
69 _totally_ disable translation of messages.
70
71 When you already have GNU `gettext' installed on your system and run
72 configure without an option for your new package, `configure' will
73 probably detect the previously built and installed `libintl.a' file and
74 will decide to use this. This might be not what is desirable. You
75 should use the more recent version of the GNU `gettext' library. I.e.
76 if the file `intl/VERSION' shows that the library which comes with this
77 package is more recent, you should use
78
79 ./configure --with-included-gettext
80
81 to prevent auto-detection.
82
83 The configuration process will not test for the `catgets' function
84 and therefore it will not be used. The reason is that even an
85 emulation of `gettext' on top of `catgets' could not provide all the
86 extensions of the GNU `gettext' library.
87
88 Internationalized packages have usually many `po/LL.po' files, where
89 LL gives an ISO 639 two-letter code identifying the language. Unless
90 translations have been forbidden at `configure' time by using the
91 `--disable-nls' switch, all available translations are installed
92 together with the package. However, the environment variable `LINGUAS'
93 may be set, prior to configuration, to limit the installed set.
94 `LINGUAS' should then contain a space separated list of two-letter
95 codes, stating which languages are allowed.
96
97 Using This Package
98 ==================
99
100 As a user, if your language has been installed for this package, you
101 only have to set the `LANG' environment variable to the appropriate
102 `LL_CC' combination. Here `LL' is an ISO 639 two-letter language code,
103 and `CC' is an ISO 3166 two-letter country code. For example, let's
104 suppose that you speak German and live in Germany. At the shell
105 prompt, merely execute `setenv LANG de_DE' (in `csh'),
106 `export LANG; LANG=de_DE' (in `sh') or `export LANG=de_DE' (in `bash').
107 This can be done from your `.login' or `.profile' file, once and for
108 all.
109
110 You might think that the country code specification is redundant.
111 But in fact, some languages have dialects in different countries. For
112 example, `de_AT' is used for Austria, and `pt_BR' for Brazil. The
113 country code serves to distinguish the dialects.
114
115 Not all programs have translations for all languages. By default, an
116 English message is shown in place of a nonexistent translation. If you
117 understand other languages, you can set up a priority list of languages.
118 This is done through a different environment variable, called
119 `LANGUAGE'. GNU `gettext' gives preference to `LANGUAGE' over `LANG'
120 for the purpose of message handling, but you still need to have `LANG'
121 set to the primary language; this is required by other parts of the
122 system libraries. For example, some Swedish users who would rather
123 read translations in German than English for when Swedish is not
124 available, set `LANGUAGE' to `sv:de' while leaving `LANG' to `sv_SE'.
125
126 In the `LANGUAGE' environment variable, but not in the `LANG'
127 environment variable, `LL_CC' combinations can be abbreviated as `LL'
128 to denote the language's main dialect. For example, `de' is equivalent
129 to `de_DE' (German as spoken in Germany), and `pt' to `pt_PT'
130 (Portuguese as spoken in Portugal) in this context.
131
132 Translating Teams
133 =================
134
135 For the Free Translation Project to be a success, we need interested
136 people who like their own language and write it well, and who are also
137 able to synergize with other translators speaking the same language.
138 Each translation team has its own mailing list. The up-to-date list of
139 teams can be found at the Free Translation Project's homepage,
140 `http://www.iro.umontreal.ca/contrib/po/HTML/', in the "National teams"
141 area.
142
143 If you'd like to volunteer to _work_ at translating messages, you
144 should become a member of the translating team for your own language.
145 The subscribing address is _not_ the same as the list itself, it has
146 `-request' appended. For example, speakers of Swedish can send a
147 message to `sv-request@li.org', having this message body:
148
149 subscribe
150
151 Keep in mind that team members are expected to participate
152 _actively_ in translations, or at solving translational difficulties,
153 rather than merely lurking around. If your team does not exist yet and
154 you want to start one, or if you are unsure about what to do or how to
155 get started, please write to `translation@iro.umontreal.ca' to reach the
156 coordinator for all translator teams.
157
158 The English team is special. It works at improving and uniformizing
159 the terminology in use. Proven linguistic skill are praised more than
160 programming skill, here.
161
162 Available Packages
163 ==================
164
165 Languages are not equally supported in all packages. The following
166 matrix shows the current state of internationalization, as of September
167 2001. The matrix shows, in regard of each package, for which languages
168 PO files have been submitted to translation coordination, with a
169 translation percentage of at least 50%.
170
171 Ready PO files bg cs da de el en eo es et fi fr gl he hr id it ja
172 +----------------------------------------------------+
173 a2ps | [] [] [] |
174 bash | [] [] [] [] |
175 bfd | |
176 binutils | [] |
177 bison | [] [] [] [] [] |
178 clisp | [] [] [] [] |
179 cpio | [] [] [] [] [] |
180 diffutils | [] [] [] [] [] [] [] |
181 enscript | [] [] |
182 error | [] [] |
183 fetchmail | |
184 fileutils | [] [] [] [] [] [] [] [] |
185 findutils | [] [] [] [] [] [] [] [] |
186 flex | [] [] [] |
187 freetype | |
188 gas | |
189 gawk | [] [] |
190 gcal | |
191 gcc | |
192 gettext | [] [] [] [] [] [] [] [] [] [] |
193 gnupg | [] [] [] [] [] [] [] |
194 gprof | |
195 grep | [] [] [] [] [] [] [] [] |
196 hello | [] [] [] [] [] [] [] [] [] [] [] |
197 id-utils | [] [] [] |
198 indent | [] [] [] [] [] |
199 jpilot | [] |
200 kbd | |
201 ld | [] |
202 libc | [] [] [] [] [] [] [] [] |
203 lilypond | [] |
204 lynx | [] [] [] [] |
205 m4 | [] [] [] [] [] [] [] [] |
206 make | [] [] [] [] [] [] |
207 mysecretdiary | [] |
208 nano | [] [] [] |
209 opcodes | |
210 parted | [] [] [] |
211 ptx | [] [] [] [] [] [] [] |
212 python | |
213 recode | [] [] [] [] [] [] [] [] [] |
214 sed | [] [] [] [] [] [] [] [] [] [] [] [] |
215 sh-utils | [] [] [] [] [] [] [] [] [] [] |
216 sharutils | [] [] [] [] [] [] [] [] |
217 sketch | |
218 soundtracker | [] [] [] |
219 sp | |
220 tar | [] [] [] [] [] [] [] [] |
221 texinfo | [] [] [] [] [] [] |
222 textutils | [] [] [] [] [] [] [] [] |
223 util-linux | [] [] |
224 wdiff | [] [] [] |
225 wget | [] [] [] [] [] [] [] [] [] [] |
226 +----------------------------------------------------+
227 bg cs da de el en eo es et fi fr gl he hr id it ja
228 0 14 24 32 11 1 8 23 13 1 33 22 4 0 7 9 18
229
230 ko lv nb nl nn no pl pt pt_BR ru sk sl sv tr uk zh
231 +----------------------------------------------------+
232 a2ps | [] [] [] | 6
233 bash | | 4
234 bfd | | 0
235 binutils | | 1
236 bison | [] | 6
237 clisp | [] | 5
238 cpio | [] [] [] [] [] | 10
239 diffutils | [] [] [] [] | 11
240 enscript | [] [] [] | 5
241 error | [] [] | 4
242 fetchmail | | 0
243 fileutils | [] [] [] [] [] [] [] [] [] | 17
244 findutils | [] [] [] [] [] [] [] [] | 16
245 flex | [] [] [] | 6
246 freetype | | 0
247 gas | | 0
248 gawk | [] | 3
249 gcal | | 0
250 gcc | | 0
251 gettext | [] [] [] [] [] [] [] [] | 18
252 gnupg | [] [] [] | 10
253 gprof | | 0
254 grep | [] [] [] [] | 12
255 hello | [] [] [] [] [] [] [] [] [] [] [] | 22
256 id-utils | [] [] [] | 6
257 indent | [] [] [] [] [] [] [] | 12
258 jpilot | | 1
259 kbd | [] | 1
260 ld | | 1
261 libc | [] [] [] [] [] [] [] [] | 16
262 lilypond | [] [] | 3
263 lynx | [] [] [] [] | 8
264 m4 | [] [] [] [] | 12
265 make | [] [] [] [] [] [] | 12
266 mysecretdiary | | 1
267 nano | [] | 4
268 opcodes | [] | 1
269 parted | [] [] | 5
270 ptx | [] [] [] [] [] [] [] [] | 15
271 python | | 0
272 recode | [] [] [] [] | 13
273 sed | [] [] [] [] [] [] [] | 19
274 sh-utils | [] [] [] [] [] [] [] [] [] [] [] | 21
275 sharutils | [] [] [] | 11
276 sketch | | 0
277 soundtracker | | 3
278 sp | | 0
279 tar | [] [] [] [] [] [] [] | 15
280 texinfo | [] | 7
281 textutils | [] [] [] [] [] [] [] [] | 16
282 util-linux | [] [] | 4
283 wdiff | [] [] [] [] | 7
284 wget | [] [] [] [] [] [] [] | 17
285 +----------------------------------------------------+
286 33 teams ko lv nb nl nn no pl pt pt_BR ru sk sl sv tr uk zh
287 53 domains 9 1 6 20 0 6 17 1 13 25 10 11 23 21 2 2 387
288
289 Some counters in the preceding matrix are higher than the number of
290 visible blocks let us expect. This is because a few extra PO files are
291 used for implementing regional variants of languages, or language
292 dialects.
293
294 For a PO file in the matrix above to be effective, the package to
295 which it applies should also have been internationalized and
296 distributed as such by its maintainer. There might be an observable
297 lag between the mere existence a PO file and its wide availability in a
298 distribution.
299
300 If September 2001 seems to be old, you may fetch a more recent copy
301 of this `ABOUT-NLS' file on most GNU archive sites. The most
302 up-to-date matrix with full percentage details can be found at
303 `http://www.iro.umontreal.ca/contrib/po/HTML/matrix.html'.
304
305 Using `gettext' in new packages
306 ===============================
307
308 If you are writing a freely available program and want to
309 internationalize it you are welcome to use GNU `gettext' in your
310 package. Of course you have to respect the GNU Library General Public
311 License which covers the use of the GNU `gettext' library. This means
312 in particular that even non-free programs can use `libintl' as a shared
313 library, whereas only free software can use `libintl' as a static
314 library or use modified versions of `libintl'.
315
316 Once the sources are changed appropriately and the setup can handle
317 to use of `gettext' the only thing missing are the translations. The
318 Free Translation Project is also available for packages which are not
319 developed inside the GNU project. Therefore the information given above
320 applies also for every other Free Software Project. Contact
321 `translation@iro.umontreal.ca' to make the `.pot' files available to
322 the translation teams.
323
+0
-1
1.3.0/AUTHORS less more
0 (C) Yaacov Zamir <kzamir@walla.co.il> 2003-2005.
+0
-340
1.3.0/COPYING less more
0 GNU GENERAL PUBLIC LICENSE
1 Version 2, June 1991
2
3 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
4 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
5 Everyone is permitted to copy and distribute verbatim copies
6 of this license document, but changing it is not allowed.
7
8 Preamble
9
10 The licenses for most software are designed to take away your
11 freedom to share and change it. By contrast, the GNU General Public
12 License is intended to guarantee your freedom to share and change free
13 software--to make sure the software is free for all its users. This
14 General Public License applies to most of the Free Software
15 Foundation's software and to any other program whose authors commit to
16 using it. (Some other Free Software Foundation software is covered by
17 the GNU Library General Public License instead.) You can apply it to
18 your programs, too.
19
20 When we speak of free software, we are referring to freedom, not
21 price. Our General Public Licenses are designed to make sure that you
22 have the freedom to distribute copies of free software (and charge for
23 this service if you wish), that you receive source code or can get it
24 if you want it, that you can change the software or use pieces of it
25 in new free programs; and that you know you can do these things.
26
27 To protect your rights, we need to make restrictions that forbid
28 anyone to deny you these rights or to ask you to surrender the rights.
29 These restrictions translate to certain responsibilities for you if you
30 distribute copies of the software, or if you modify it.
31
32 For example, if you distribute copies of such a program, whether
33 gratis or for a fee, you must give the recipients all the rights that
34 you have. You must make sure that they, too, receive or can get the
35 source code. And you must show them these terms so they know their
36 rights.
37
38 We protect your rights with two steps: (1) copyright the software, and
39 (2) offer you this license which gives you legal permission to copy,
40 distribute and/or modify the software.
41
42 Also, for each author's protection and ours, we want to make certain
43 that everyone understands that there is no warranty for this free
44 software. If the software is modified by someone else and passed on, we
45 want its recipients to know that what they have is not the original, so
46 that any problems introduced by others will not reflect on the original
47 authors' reputations.
48
49 Finally, any free program is threatened constantly by software
50 patents. We wish to avoid the danger that redistributors of a free
51 program will individually obtain patent licenses, in effect making the
52 program proprietary. To prevent this, we have made it clear that any
53 patent must be licensed for everyone's free use or not licensed at all.
54
55 The precise terms and conditions for copying, distribution and
56 modification follow.
57
58 GNU GENERAL PUBLIC LICENSE
59 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
60
61 0. This License applies to any program or other work which contains
62 a notice placed by the copyright holder saying it may be distributed
63 under the terms of this General Public License. The "Program", below,
64 refers to any such program or work, and a "work based on the Program"
65 means either the Program or any derivative work under copyright law:
66 that is to say, a work containing the Program or a portion of it,
67 either verbatim or with modifications and/or translated into another
68 language. (Hereinafter, translation is included without limitation in
69 the term "modification".) Each licensee is addressed as "you".
70
71 Activities other than copying, distribution and modification are not
72 covered by this License; they are outside its scope. The act of
73 running the Program is not restricted, and the output from the Program
74 is covered only if its contents constitute a work based on the
75 Program (independent of having been made by running the Program).
76 Whether that is true depends on what the Program does.
77
78 1. You may copy and distribute verbatim copies of the Program's
79 source code as you receive it, in any medium, provided that you
80 conspicuously and appropriately publish on each copy an appropriate
81 copyright notice and disclaimer of warranty; keep intact all the
82 notices that refer to this License and to the absence of any warranty;
83 and give any other recipients of the Program a copy of this License
84 along with the Program.
85
86 You may charge a fee for the physical act of transferring a copy, and
87 you may at your option offer warranty protection in exchange for a fee.
88
89 2. You may modify your copy or copies of the Program or any portion
90 of it, thus forming a work based on the Program, and copy and
91 distribute such modifications or work under the terms of Section 1
92 above, provided that you also meet all of these conditions:
93
94 a) You must cause the modified files to carry prominent notices
95 stating that you changed the files and the date of any change.
96
97 b) You must cause any work that you distribute or publish, that in
98 whole or in part contains or is derived from the Program or any
99 part thereof, to be licensed as a whole at no charge to all third
100 parties under the terms of this License.
101
102 c) If the modified program normally reads commands interactively
103 when run, you must cause it, when started running for such
104 interactive use in the most ordinary way, to print or display an
105 announcement including an appropriate copyright notice and a
106 notice that there is no warranty (or else, saying that you provide
107 a warranty) and that users may redistribute the program under
108 these conditions, and telling the user how to view a copy of this
109 License. (Exception: if the Program itself is interactive but
110 does not normally print such an announcement, your work based on
111 the Program is not required to print an announcement.)
112
113 These requirements apply to the modified work as a whole. If
114 identifiable sections of that work are not derived from the Program,
115 and can be reasonably considered independent and separate works in
116 themselves, then this License, and its terms, do not apply to those
117 sections when you distribute them as separate works. But when you
118 distribute the same sections as part of a whole which is a work based
119 on the Program, the distribution of the whole must be on the terms of
120 this License, whose permissions for other licensees extend to the
121 entire whole, and thus to each and every part regardless of who wrote it.
122
123 Thus, it is not the intent of this section to claim rights or contest
124 your rights to work written entirely by you; rather, the intent is to
125 exercise the right to control the distribution of derivative or
126 collective works based on the Program.
127
128 In addition, mere aggregation of another work not based on the Program
129 with the Program (or with a work based on the Program) on a volume of
130 a storage or distribution medium does not bring the other work under
131 the scope of this License.
132
133 3. You may copy and distribute the Program (or a work based on it,
134 under Section 2) in object code or executable form under the terms of
135 Sections 1 and 2 above provided that you also do one of the following:
136
137 a) Accompany it with the complete corresponding machine-readable
138 source code, which must be distributed under the terms of Sections
139 1 and 2 above on a medium customarily used for software interchange; or,
140
141 b) Accompany it with a written offer, valid for at least three
142 years, to give any third party, for a charge no more than your
143 cost of physically performing source distribution, a complete
144 machine-readable copy of the corresponding source code, to be
145 distributed under the terms of Sections 1 and 2 above on a medium
146 customarily used for software interchange; or,
147
148 c) Accompany it with the information you received as to the offer
149 to distribute corresponding source code. (This alternative is
150 allowed only for noncommercial distribution and only if you
151 received the program in object code or executable form with such
152 an offer, in accord with Subsection b above.)
153
154 The source code for a work means the preferred form of the work for
155 making modifications to it. For an executable work, complete source
156 code means all the source code for all modules it contains, plus any
157 associated interface definition files, plus the scripts used to
158 control compilation and installation of the executable. However, as a
159 special exception, the source code distributed need not include
160 anything that is normally distributed (in either source or binary
161 form) with the major components (compiler, kernel, and so on) of the
162 operating system on which the executable runs, unless that component
163 itself accompanies the executable.
164
165 If distribution of executable or object code is made by offering
166 access to copy from a designated place, then offering equivalent
167 access to copy the source code from the same place counts as
168 distribution of the source code, even though third parties are not
169 compelled to copy the source along with the object code.
170
171 4. You may not copy, modify, sublicense, or distribute the Program
172 except as expressly provided under this License. Any attempt
173 otherwise to copy, modify, sublicense or distribute the Program is
174 void, and will automatically terminate your rights under this License.
175 However, parties who have received copies, or rights, from you under
176 this License will not have their licenses terminated so long as such
177 parties remain in full compliance.
178
179 5. You are not required to accept this License, since you have not
180 signed it. However, nothing else grants you permission to modify or
181 distribute the Program or its derivative works. These actions are
182 prohibited by law if you do not accept this License. Therefore, by
183 modifying or distributing the Program (or any work based on the
184 Program), you indicate your acceptance of this License to do so, and
185 all its terms and conditions for copying, distributing or modifying
186 the Program or works based on it.
187
188 6. Each time you redistribute the Program (or any work based on the
189 Program), the recipient automatically receives a license from the
190 original licensor to copy, distribute or modify the Program subject to
191 these terms and conditions. You may not impose any further
192 restrictions on the recipients' exercise of the rights granted herein.
193 You are not responsible for enforcing compliance by third parties to
194 this License.
195
196 7. If, as a consequence of a court judgment or allegation of patent
197 infringement or for any other reason (not limited to patent issues),
198 conditions are imposed on you (whether by court order, agreement or
199 otherwise) that contradict the conditions of this License, they do not
200 excuse you from the conditions of this License. If you cannot
201 distribute so as to satisfy simultaneously your obligations under this
202 License and any other pertinent obligations, then as a consequence you
203 may not distribute the Program at all. For example, if a patent
204 license would not permit royalty-free redistribution of the Program by
205 all those who receive copies directly or indirectly through you, then
206 the only way you could satisfy both it and this License would be to
207 refrain entirely from distribution of the Program.
208
209 If any portion of this section is held invalid or unenforceable under
210 any particular circumstance, the balance of the section is intended to
211 apply and the section as a whole is intended to apply in other
212 circumstances.
213
214 It is not the purpose of this section to induce you to infringe any
215 patents or other property right claims or to contest validity of any
216 such claims; this section has the sole purpose of protecting the
217 integrity of the free software distribution system, which is
218 implemented by public license practices. Many people have made
219 generous contributions to the wide range of software distributed
220 through that system in reliance on consistent application of that
221 system; it is up to the author/donor to decide if he or she is willing
222 to distribute software through any other system and a licensee cannot
223 impose that choice.
224
225 This section is intended to make thoroughly clear what is believed to
226 be a consequence of the rest of this License.
227
228 8. If the distribution and/or use of the Program is restricted in
229 certain countries either by patents or by copyrighted interfaces, the
230 original copyright holder who places the Program under this License
231 may add an explicit geographical distribution limitation excluding
232 those countries, so that distribution is permitted only in or among
233 countries not thus excluded. In such case, this License incorporates
234 the limitation as if written in the body of this License.
235
236 9. The Free Software Foundation may publish revised and/or new versions
237 of the General Public License from time to time. Such new versions will
238 be similar in spirit to the present version, but may differ in detail to
239 address new problems or concerns.
240
241 Each version is given a distinguishing version number. If the Program
242 specifies a version number of this License which applies to it and "any
243 later version", you have the option of following the terms and conditions
244 either of that version or of any later version published by the Free
245 Software Foundation. If the Program does not specify a version number of
246 this License, you may choose any version ever published by the Free Software
247 Foundation.
248
249 10. If you wish to incorporate parts of the Program into other free
250 programs whose distribution conditions are different, write to the author
251 to ask for permission. For software which is copyrighted by the Free
252 Software Foundation, write to the Free Software Foundation; we sometimes
253 make exceptions for this. Our decision will be guided by the two goals
254 of preserving the free status of all derivatives of our free software and
255 of promoting the sharing and reuse of software generally.
256
257 NO WARRANTY
258
259 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
260 FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
261 OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
262 PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
263 OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
264 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
265 TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
266 PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
267 REPAIR OR CORRECTION.
268
269 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
270 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
271 REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
272 INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
273 OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
274 TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
275 YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
276 PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
277 POSSIBILITY OF SUCH DAMAGES.
278
279 END OF TERMS AND CONDITIONS
280
281 How to Apply These Terms to Your New Programs
282
283 If you develop a new program, and you want it to be of the greatest
284 possible use to the public, the best way to achieve this is to make it
285 free software which everyone can redistribute and change under these terms.
286
287 To do so, attach the following notices to the program. It is safest
288 to attach them to the start of each source file to most effectively
289 convey the exclusion of warranty; and each file should have at least
290 the "copyright" line and a pointer to where the full notice is found.
291
292 <one line to give the program's name and a brief idea of what it does.>
293 Copyright (C) <year> <name of author>
294
295 This program is free software; you can redistribute it and/or modify
296 it under the terms of the GNU General Public License as published by
297 the Free Software Foundation; either version 2 of the License, or
298 (at your option) any later version.
299
300 This program is distributed in the hope that it will be useful,
301 but WITHOUT ANY WARRANTY; without even the implied warranty of
302 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
303 GNU General Public License for more details.
304
305 You should have received a copy of the GNU General Public License
306 along with this program; if not, write to the Free Software
307 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
308
309
310 Also add information on how to contact you by electronic and paper mail.
311
312 If the program is interactive, make it output a short notice like this
313 when it starts in an interactive mode:
314
315 Gnomovision version 69, Copyright (C) year name of author
316 Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
317 This is free software, and you are welcome to redistribute it
318 under certain conditions; type `show c' for details.
319
320 The hypothetical commands `show w' and `show c' should show the appropriate
321 parts of the General Public License. Of course, the commands you use may
322 be called something other than `show w' and `show c'; they could even be
323 mouse-clicks or menu items--whatever suits your program.
324
325 You should also get your employer (if you work as a programmer) or your
326 school, if any, to sign a "copyright disclaimer" for the program, if
327 necessary. Here is a sample; alter the names:
328
329 Yoyodyne, Inc., hereby disclaims all copyright interest in the program
330 `Gnomovision' (which makes passes at compilers) written by James Hacker.
331
332 <signature of Ty Coon>, 1 April 1989
333 Ty Coon, President of Vice
334
335 This General Public License does not permit incorporating your program into
336 proprietary programs. If your program is a subroutine library, you may
337 consider it more useful to permit linking proprietary applications with the
338 library. If this is what you want to do, use the GNU Library General
339 Public License instead of this License.
+0
-84
1.3.0/ChangeLog less more
0 libhdate (1.3.0)
1
2 * Add examples to the doc directory
3 * doc directory is now /usr/doc/libhdate0 and no /usr/doc/hdate
4 * make int_to_string aware of LANGUAGE system variable, make it more gettext compatible
5
6 -- Yaacov Zamir <kzamir@wall.co.il> Wed, 27 Jul 2005 18:13
7
8 libhdate (1.0.1)
9
10 * first major reales number.
11 * start to number the shared library.
12 * stable api.
13 * updated utility programs hdate/hcal.
14 * added man files for library and utility programs.
15 * python and perl bindings.
16 * free pascal binding by Ido Kanner <idokan@gmail.com>
17 * ru, fr, he, es translations, thanks to Peled Esti and Boris Peterberg.
18 * added debian dir and RH spec file for easy packing, thanks to Oron Peled.
19
20 -- Yaacov Zamir <kzamir@wall.co.il> Tue, 08 March 2005 18:13
21
22 libhdate (0.30.0)
23
24 * add es_MX translation by Peled Esti <esti@actcom.co.il>
25 * initial russian translation by Boris Peterberg
26
27 -- Yaacov Zamir <kzamir@wall.co.il> Tue, 08 March 2005 18:13
28
29 libhdate (0.30.0)
30
31 * cpp, python and perl bindings
32 * examples for the new libhdate bindings
33
34 -- Yaacov Zamir <kzamir@wall.co.il> Fri, 04 March 2005 15:19:29
35
36 libhdate (0.22.0)
37
38 * Michael Kaminsky's patch to Shavot II on diaspora reading.
39
40 -- Yaacov Zamir <kzamir@wall.co.il> Mon, 28 Feb 2005 08:12:31
41
42 libhdate (0.22.0)
43
44 * New hebcal examples
45
46 -- Yaacov Zamir <kzamir@wall.co.il> Fri, 25 Feb 2005 11:15:18
47
48 libhdate (0.21.0)
49
50 * New spec file by Oron Peled
51 * Diaspora holydays/readings
52 * New sunrise sunset functions
53 * New html examples
54 * New configure options to build / not build the examples
55
56 -- Yaacov Zamir <kzamir@wall.co.il> Fri, 25 Feb 2005 11:15:18
57
58 libhdate (0.17.0)
59
60 * API chages.
61 * base struct change.
62
63 -- Yaacov Zamir <kzamir@wall.co.il> Mon, 22 Feb 2005 19:34:22
64
65 libhdate (0.16.3)
66
67 * Try to fix date conversion bug, thanks Michael Kaminsky.
68
69 -- Yaacov Zamir <kzamir@wall.co.il> Mon, 21 Feb 2005 09:03:12
70
71 libhdate (0.16.2)
72
73 * Syntax error, and weeks calculation bug fixed by Michael Kaminsky.
74
75 -- Yaacov Zamir <kzamir@wall.co.il> Sun, 20 Feb 2005 06:53:12
76
77 libhdate (0.16.1)
78
79 * Fix locale bug in int_to_string.
80 * Add examples directory.
81 * Minor bug fixes.
82
83 -- Yaacov Zamir <kzamir@wall.co.il> Sat, 19 Feb 2005 20:07:19
+0
-1212
1.3.0/Doxyfile less more
0 # Doxyfile 1.4.1
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 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
17 # by quotes) that should identify the project.
18
19 PROJECT_NAME = libhdate
20
21 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
22 # This could be handy for archiving the generated documentation or
23 # if some version control system is used.
24
25 PROJECT_NUMBER = 1.0
26
27 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
28 # base path where the generated documentation will be put.
29 # If a relative path is entered, it will be relative to the location
30 # where doxygen was started. If left blank the current directory will be used.
31
32 OUTPUT_DIRECTORY =
33
34 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
35 # 4096 sub-directories (in 2 levels) under the output directory of each output
36 # format and will distribute the generated files over these directories.
37 # Enabling this option can be useful when feeding doxygen a huge amount of
38 # source files, where putting all generated files in the same directory would
39 # otherwise cause performance problems for the file system.
40
41 CREATE_SUBDIRS = NO
42
43 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
44 # documentation generated by doxygen is written. Doxygen will use this
45 # information to generate all constant output in the proper language.
46 # The default language is English, other supported languages are:
47 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
48 # Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
49 # Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
50 # Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
51 # Swedish, and Ukrainian.
52
53 OUTPUT_LANGUAGE = English
54
55 # This tag can be used to specify the encoding used in the generated output.
56 # The encoding is not always determined by the language that is chosen,
57 # but also whether or not the output is meant for Windows or non-Windows users.
58 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
59 # forces the Windows encoding (this is the default for the Windows binary),
60 # whereas setting the tag to NO uses a Unix-style encoding (the default for
61 # all platforms other than Windows).
62
63 USE_WINDOWS_ENCODING = NO
64
65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
66 # include brief member descriptions after the members that are listed in
67 # the file and class documentation (similar to JavaDoc).
68 # Set to NO to disable this.
69
70 BRIEF_MEMBER_DESC = YES
71
72 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
73 # the brief description of a member or function before the detailed description.
74 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
75 # brief descriptions will be completely suppressed.
76
77 REPEAT_BRIEF = YES
78
79 # This tag implements a quasi-intelligent brief description abbreviator
80 # that is used to form the text in various listings. Each string
81 # in this list, if found as the leading text of the brief description, will be
82 # stripped from the text and the result after processing the whole list, is
83 # used as the annotated text. Otherwise, the brief description is used as-is.
84 # If left blank, the following values are used ("$name" is automatically
85 # replaced with the name of the entity): "The $name class" "The $name widget"
86 # "The $name file" "is" "provides" "specifies" "contains"
87 # "represents" "a" "an" "the"
88
89 ABBREVIATE_BRIEF =
90
91 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
92 # Doxygen will generate a detailed section even if there is only a brief
93 # description.
94
95 ALWAYS_DETAILED_SEC = NO
96
97 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
98 # inherited members of a class in the documentation of that class as if those
99 # members were ordinary class members. Constructors, destructors and assignment
100 # operators of the base classes will not be shown.
101
102 INLINE_INHERITED_MEMB = NO
103
104 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
105 # path before files name in the file list and in the header files. If set
106 # to NO the shortest path that makes the file name unique will be used.
107
108 FULL_PATH_NAMES = YES
109
110 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
111 # can be used to strip a user-defined part of the path. Stripping is
112 # only done if one of the specified strings matches the left-hand part of
113 # the path. The tag can be used to show relative paths in the file list.
114 # If left blank the directory from which doxygen is run is used as the
115 # path to strip.
116
117 STRIP_FROM_PATH =
118
119 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
120 # the path mentioned in the documentation of a class, which tells
121 # the reader which header file to include in order to use a class.
122 # If left blank only the name of the header file containing the class
123 # definition is used. Otherwise one should specify the include paths that
124 # are normally passed to the compiler using the -I flag.
125
126 STRIP_FROM_INC_PATH =
127
128 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
129 # (but less readable) file names. This can be useful is your file systems
130 # doesn't support long names like on DOS, Mac, or CD-ROM.
131
132 SHORT_NAMES = NO
133
134 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
135 # will interpret the first line (until the first dot) of a JavaDoc-style
136 # comment as the brief description. If set to NO, the JavaDoc
137 # comments will behave just like the Qt-style comments (thus requiring an
138 # explicit @brief command for a brief description.
139
140 JAVADOC_AUTOBRIEF = NO
141
142 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
143 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
144 # comments) as a brief description. This used to be the default behaviour.
145 # The new default is to treat a multi-line C++ comment block as a detailed
146 # description. Set this tag to YES if you prefer the old behaviour instead.
147
148 MULTILINE_CPP_IS_BRIEF = NO
149
150 # If the DETAILS_AT_TOP tag is set to YES then Doxygen
151 # will output the detailed description near the top, like JavaDoc.
152 # If set to NO, the detailed description appears after the member
153 # documentation.
154
155 DETAILS_AT_TOP = NO
156
157 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
158 # member inherits the documentation from any documented member that it
159 # re-implements.
160
161 INHERIT_DOCS = YES
162
163 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
164 # tag is set to YES, then doxygen will reuse the documentation of the first
165 # member in the group (if any) for the other members of the group. By default
166 # all members of a group must be documented explicitly.
167
168 DISTRIBUTE_GROUP_DOC = NO
169
170 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
171 # Doxygen uses this value to replace tabs by spaces in code fragments.
172
173 TAB_SIZE = 8
174
175 # This tag can be used to specify a number of aliases that acts
176 # as commands in the documentation. An alias has the form "name=value".
177 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
178 # put the command \sideeffect (or @sideeffect) in the documentation, which
179 # will result in a user-defined paragraph with heading "Side Effects:".
180 # You can put \n's in the value part of an alias to insert newlines.
181
182 ALIASES =
183
184 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
185 # sources only. Doxygen will then generate output that is more tailored for C.
186 # For instance, some of the names that are used will be different. The list
187 # of all members will be omitted, etc.
188
189 OPTIMIZE_OUTPUT_FOR_C = YES
190
191 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
192 # only. Doxygen will then generate output that is more tailored for Java.
193 # For instance, namespaces will be presented as packages, qualified scopes
194 # will look different, etc.
195
196 OPTIMIZE_OUTPUT_JAVA = NO
197
198 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
199 # the same type (for instance a group of public functions) to be put as a
200 # subgroup of that type (e.g. under the Public Functions section). Set it to
201 # NO to prevent subgrouping. Alternatively, this can be done per class using
202 # the \nosubgrouping command.
203
204 SUBGROUPING = YES
205
206 #---------------------------------------------------------------------------
207 # Build related configuration options
208 #---------------------------------------------------------------------------
209
210 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
211 # documentation are documented, even if no documentation was available.
212 # Private class members and static file members will be hidden unless
213 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
214
215 EXTRACT_ALL = YES
216
217 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
218 # will be included in the documentation.
219
220 EXTRACT_PRIVATE = NO
221
222 # If the EXTRACT_STATIC tag is set to YES all static members of a file
223 # will be included in the documentation.
224
225 EXTRACT_STATIC = NO
226
227 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
228 # defined locally in source files will be included in the documentation.
229 # If set to NO only classes defined in header files are included.
230
231 EXTRACT_LOCAL_CLASSES = YES
232
233 # This flag is only useful for Objective-C code. When set to YES local
234 # methods, which are defined in the implementation section but not in
235 # the interface are included in the documentation.
236 # If set to NO (the default) only methods in the interface are included.
237
238 EXTRACT_LOCAL_METHODS = YES
239
240 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
241 # undocumented members of documented classes, files or namespaces.
242 # If set to NO (the default) these members will be included in the
243 # various overviews, but no documentation section is generated.
244 # This option has no effect if EXTRACT_ALL is enabled.
245
246 HIDE_UNDOC_MEMBERS = NO
247
248 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
249 # undocumented classes that are normally visible in the class hierarchy.
250 # If set to NO (the default) these classes will be included in the various
251 # overviews. This option has no effect if EXTRACT_ALL is enabled.
252
253 HIDE_UNDOC_CLASSES = NO
254
255 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
256 # friend (class|struct|union) declarations.
257 # If set to NO (the default) these declarations will be included in the
258 # documentation.
259
260 HIDE_FRIEND_COMPOUNDS = NO
261
262 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
263 # documentation blocks found inside the body of a function.
264 # If set to NO (the default) these blocks will be appended to the
265 # function's detailed documentation block.
266
267 HIDE_IN_BODY_DOCS = NO
268
269 # The INTERNAL_DOCS tag determines if documentation
270 # that is typed after a \internal command is included. If the tag is set
271 # to NO (the default) then the documentation will be excluded.
272 # Set it to YES to include the internal documentation.
273
274 INTERNAL_DOCS = NO
275
276 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
277 # file names in lower-case letters. If set to YES upper-case letters are also
278 # allowed. This is useful if you have classes or files whose names only differ
279 # in case and if your file system supports case sensitive file names. Windows
280 # and Mac users are advised to set this option to NO.
281
282 CASE_SENSE_NAMES = YES
283
284 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
285 # will show members with their full class and namespace scopes in the
286 # documentation. If set to YES the scope will be hidden.
287
288 HIDE_SCOPE_NAMES = NO
289
290 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
291 # will put a list of the files that are included by a file in the documentation
292 # of that file.
293
294 SHOW_INCLUDE_FILES = YES
295
296 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
297 # is inserted in the documentation for inline members.
298
299 INLINE_INFO = YES
300
301 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
302 # will sort the (detailed) documentation of file and class members
303 # alphabetically by member name. If set to NO the members will appear in
304 # declaration order.
305
306 SORT_MEMBER_DOCS = NO
307
308 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
309 # brief documentation of file, namespace and class members alphabetically
310 # by member name. If set to NO (the default) the members will appear in
311 # declaration order.
312
313 SORT_BRIEF_DOCS = NO
314
315 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
316 # sorted by fully-qualified names, including namespaces. If set to
317 # NO (the default), the class list will be sorted only by class name,
318 # not including the namespace part.
319 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
320 # Note: This option applies only to the class list, not to the
321 # alphabetical list.
322
323 SORT_BY_SCOPE_NAME = NO
324
325 # The GENERATE_TODOLIST tag can be used to enable (YES) or
326 # disable (NO) the todo list. This list is created by putting \todo
327 # commands in the documentation.
328
329 GENERATE_TODOLIST = YES
330
331 # The GENERATE_TESTLIST tag can be used to enable (YES) or
332 # disable (NO) the test list. This list is created by putting \test
333 # commands in the documentation.
334
335 GENERATE_TESTLIST = YES
336
337 # The GENERATE_BUGLIST tag can be used to enable (YES) or
338 # disable (NO) the bug list. This list is created by putting \bug
339 # commands in the documentation.
340
341 GENERATE_BUGLIST = YES
342
343 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
344 # disable (NO) the deprecated list. This list is created by putting
345 # \deprecated commands in the documentation.
346
347 GENERATE_DEPRECATEDLIST= YES
348
349 # The ENABLED_SECTIONS tag can be used to enable conditional
350 # documentation sections, marked by \if sectionname ... \endif.
351
352 ENABLED_SECTIONS =
353
354 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
355 # the initial value of a variable or define consists of for it to appear in
356 # the documentation. If the initializer consists of more lines than specified
357 # here it will be hidden. Use a value of 0 to hide initializers completely.
358 # The appearance of the initializer of individual variables and defines in the
359 # documentation can be controlled using \showinitializer or \hideinitializer
360 # command in the documentation regardless of this setting.
361
362 MAX_INITIALIZER_LINES = 30
363
364 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
365 # at the bottom of the documentation of classes and structs. If set to YES the
366 # list will mention the files that were used to generate the documentation.
367
368 SHOW_USED_FILES = YES
369
370 # If the sources in your project are distributed over multiple directories
371 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
372 # in the documentation.
373
374 SHOW_DIRECTORIES = YES
375
376 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
377 # doxygen should invoke to get the current version for each file (typically from the
378 # version control system). Doxygen will invoke the program by executing (via
379 # popen()) the command <command> <input-file>, where <command> is the value of
380 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
381 # provided by doxygen. Whatever the progam writes to standard output
382 # is used as the file version. See the manual for examples.
383
384 FILE_VERSION_FILTER =
385
386 #---------------------------------------------------------------------------
387 # configuration options related to warning and progress messages
388 #---------------------------------------------------------------------------
389
390 # The QUIET tag can be used to turn on/off the messages that are generated
391 # by doxygen. Possible values are YES and NO. If left blank NO is used.
392
393 QUIET = NO
394
395 # The WARNINGS tag can be used to turn on/off the warning messages that are
396 # generated by doxygen. Possible values are YES and NO. If left blank
397 # NO is used.
398
399 WARNINGS = YES
400
401 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
402 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
403 # automatically be disabled.
404
405 WARN_IF_UNDOCUMENTED = YES
406
407 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
408 # potential errors in the documentation, such as not documenting some
409 # parameters in a documented function, or documenting parameters that
410 # don't exist or using markup commands wrongly.
411
412 WARN_IF_DOC_ERROR = YES
413
414 # This WARN_NO_PARAMDOC option can be abled to get warnings for
415 # functions that are documented, but have no documentation for their parameters
416 # or return value. If set to NO (the default) doxygen will only warn about
417 # wrong or incomplete parameter documentation, but not about the absence of
418 # documentation.
419
420 WARN_NO_PARAMDOC = NO
421
422 # The WARN_FORMAT tag determines the format of the warning messages that
423 # doxygen can produce. The string should contain the $file, $line, and $text
424 # tags, which will be replaced by the file and line number from which the
425 # warning originated and the warning text. Optionally the format may contain
426 # $version, which will be replaced by the version of the file (if it could
427 # be obtained via FILE_VERSION_FILTER)
428
429 WARN_FORMAT = "$file:$line: $text"
430
431 # The WARN_LOGFILE tag can be used to specify a file to which warning
432 # and error messages should be written. If left blank the output is written
433 # to stderr.
434
435 WARN_LOGFILE =
436
437 #---------------------------------------------------------------------------
438 # configuration options related to the input files
439 #---------------------------------------------------------------------------
440
441 # The INPUT tag can be used to specify the files and/or directories that contain
442 # documented source files. You may enter file names like "myfile.cpp" or
443 # directories like "/usr/src/myproject". Separate the files or directories
444 # with spaces.
445
446 INPUT = src
447
448 # If the value of the INPUT tag contains directories, you can use the
449 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
450 # and *.h) to filter out the source-files in the directories. If left
451 # blank the following patterns are tested:
452 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
453 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
454
455 FILE_PATTERNS = *.h
456
457 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
458 # should be searched for input files as well. Possible values are YES and NO.
459 # If left blank NO is used.
460
461 RECURSIVE = NO
462
463 # The EXCLUDE tag can be used to specify files and/or directories that should
464 # excluded from the INPUT source files. This way you can easily exclude a
465 # subdirectory from a directory tree whose root is specified with the INPUT tag.
466
467 EXCLUDE = src/support.h
468
469 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
470 # directories that are symbolic links (a Unix filesystem feature) are excluded
471 # from the input.
472
473 EXCLUDE_SYMLINKS = NO
474
475 # If the value of the INPUT tag contains directories, you can use the
476 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
477 # certain files from those directories.
478
479 EXCLUDE_PATTERNS = *.c
480
481 # The EXAMPLE_PATH tag can be used to specify one or more files or
482 # directories that contain example code fragments that are included (see
483 # the \include command).
484
485 EXAMPLE_PATH =
486
487 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
488 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
489 # and *.h) to filter out the source-files in the directories. If left
490 # blank all files are included.
491
492 EXAMPLE_PATTERNS =
493
494 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
495 # searched for input files to be used with the \include or \dontinclude
496 # commands irrespective of the value of the RECURSIVE tag.
497 # Possible values are YES and NO. If left blank NO is used.
498
499 EXAMPLE_RECURSIVE = NO
500
501 # The IMAGE_PATH tag can be used to specify one or more files or
502 # directories that contain image that are included in the documentation (see
503 # the \image command).
504
505 IMAGE_PATH =
506
507 # The INPUT_FILTER tag can be used to specify a program that doxygen should
508 # invoke to filter for each input file. Doxygen will invoke the filter program
509 # by executing (via popen()) the command <filter> <input-file>, where <filter>
510 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
511 # input file. Doxygen will then use the output that the filter program writes
512 # to standard output. If FILTER_PATTERNS is specified, this tag will be
513 # ignored.
514
515 INPUT_FILTER =
516
517 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
518 # basis. Doxygen will compare the file name with each pattern and apply the
519 # filter if there is a match. The filters are a list of the form:
520 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
521 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
522 # is applied to all files.
523
524 FILTER_PATTERNS =
525
526 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
527 # INPUT_FILTER) will be used to filter the input files when producing source
528 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
529
530 FILTER_SOURCE_FILES = NO
531
532 #---------------------------------------------------------------------------
533 # configuration options related to source browsing
534 #---------------------------------------------------------------------------
535
536 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
537 # be generated. Documented entities will be cross-referenced with these sources.
538 # Note: To get rid of all source code in the generated output, make sure also
539 # VERBATIM_HEADERS is set to NO.
540
541 SOURCE_BROWSER = NO
542
543 # Setting the INLINE_SOURCES tag to YES will include the body
544 # of functions and classes directly in the documentation.
545
546 INLINE_SOURCES = NO
547
548 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
549 # doxygen to hide any special comment blocks from generated source code
550 # fragments. Normal C and C++ comments will always remain visible.
551
552 STRIP_CODE_COMMENTS = YES
553
554 # If the REFERENCED_BY_RELATION tag is set to YES (the default)
555 # then for each documented function all documented
556 # functions referencing it will be listed.
557
558 REFERENCED_BY_RELATION = YES
559
560 # If the REFERENCES_RELATION tag is set to YES (the default)
561 # then for each documented function all documented entities
562 # called/used by that function will be listed.
563
564 REFERENCES_RELATION = YES
565
566 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
567 # will generate a verbatim copy of the header file for each class for
568 # which an include is specified. Set to NO to disable this.
569
570 VERBATIM_HEADERS = YES
571
572 #---------------------------------------------------------------------------
573 # configuration options related to the alphabetical class index
574 #---------------------------------------------------------------------------
575
576 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
577 # of all compounds will be generated. Enable this if the project
578 # contains a lot of classes, structs, unions or interfaces.
579
580 ALPHABETICAL_INDEX = NO
581
582 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
583 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
584 # in which this list will be split (can be a number in the range [1..20])
585
586 COLS_IN_ALPHA_INDEX = 5
587
588 # In case all classes in a project start with a common prefix, all
589 # classes will be put under the same header in the alphabetical index.
590 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
591 # should be ignored while generating the index headers.
592
593 IGNORE_PREFIX =
594
595 #---------------------------------------------------------------------------
596 # configuration options related to the HTML output
597 #---------------------------------------------------------------------------
598
599 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
600 # generate HTML output.
601
602 GENERATE_HTML = YES
603
604 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
605 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
606 # put in front of it. If left blank `html' will be used as the default path.
607
608 HTML_OUTPUT = html
609
610 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
611 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
612 # doxygen will generate files with .html extension.
613
614 HTML_FILE_EXTENSION = .html
615
616 # The HTML_HEADER tag can be used to specify a personal HTML header for
617 # each generated HTML page. If it is left blank doxygen will generate a
618 # standard header.
619
620 HTML_HEADER =
621
622 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
623 # each generated HTML page. If it is left blank doxygen will generate a
624 # standard footer.
625
626 HTML_FOOTER =
627
628 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
629 # style sheet that is used by each HTML page. It can be used to
630 # fine-tune the look of the HTML output. If the tag is left blank doxygen
631 # will generate a default style sheet. Note that doxygen will try to copy
632 # the style sheet file to the HTML output directory, so don't put your own
633 # stylesheet in the HTML output directory as well, or it will be erased!
634
635 HTML_STYLESHEET =
636
637 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
638 # files or namespaces will be aligned in HTML using tables. If set to
639 # NO a bullet list will be used.
640
641 HTML_ALIGN_MEMBERS = YES
642
643 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
644 # will be generated that can be used as input for tools like the
645 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
646 # of the generated HTML documentation.
647
648 GENERATE_HTMLHELP = NO
649
650 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
651 # be used to specify the file name of the resulting .chm file. You
652 # can add a path in front of the file if the result should not be
653 # written to the html output directory.
654
655 CHM_FILE =
656
657 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
658 # be used to specify the location (absolute path including file name) of
659 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
660 # the HTML help compiler on the generated index.hhp.
661
662 HHC_LOCATION =
663
664 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
665 # controls if a separate .chi index file is generated (YES) or that
666 # it should be included in the master .chm file (NO).
667
668 GENERATE_CHI = NO
669
670 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
671 # controls whether a binary table of contents is generated (YES) or a
672 # normal table of contents (NO) in the .chm file.
673
674 BINARY_TOC = NO
675
676 # The TOC_EXPAND flag can be set to YES to add extra items for group members
677 # to the contents of the HTML help documentation and to the tree view.
678
679 TOC_EXPAND = NO
680
681 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
682 # top of each HTML page. The value NO (the default) enables the index and
683 # the value YES disables it.
684
685 DISABLE_INDEX = NO
686
687 # This tag can be used to set the number of enum values (range [1..20])
688 # that doxygen will group on one line in the generated HTML documentation.
689
690 ENUM_VALUES_PER_LINE = 4
691
692 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
693 # generated containing a tree-like index structure (just like the one that
694 # is generated for HTML Help). For this to work a browser that supports
695 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
696 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
697 # probably better off using the HTML help feature.
698
699 GENERATE_TREEVIEW = NO
700
701 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
702 # used to set the initial width (in pixels) of the frame in which the tree
703 # is shown.
704
705 TREEVIEW_WIDTH = 250
706
707 #---------------------------------------------------------------------------
708 # configuration options related to the LaTeX output
709 #---------------------------------------------------------------------------
710
711 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
712 # generate Latex output.
713
714 GENERATE_LATEX = YES
715
716 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
717 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
718 # put in front of it. If left blank `latex' will be used as the default path.
719
720 LATEX_OUTPUT = latex
721
722 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
723 # invoked. If left blank `latex' will be used as the default command name.
724
725 LATEX_CMD_NAME = latex
726
727 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
728 # generate index for LaTeX. If left blank `makeindex' will be used as the
729 # default command name.
730
731 MAKEINDEX_CMD_NAME = makeindex
732
733 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
734 # LaTeX documents. This may be useful for small projects and may help to
735 # save some trees in general.
736
737 COMPACT_LATEX = NO
738
739 # The PAPER_TYPE tag can be used to set the paper type that is used
740 # by the printer. Possible values are: a4, a4wide, letter, legal and
741 # executive. If left blank a4wide will be used.
742
743 PAPER_TYPE = a4wide
744
745 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
746 # packages that should be included in the LaTeX output.
747
748 EXTRA_PACKAGES =
749
750 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
751 # the generated latex document. The header should contain everything until
752 # the first chapter. If it is left blank doxygen will generate a
753 # standard header. Notice: only use this tag if you know what you are doing!
754
755 LATEX_HEADER =
756
757 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
758 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
759 # contain links (just like the HTML output) instead of page references
760 # This makes the output suitable for online browsing using a pdf viewer.
761
762 PDF_HYPERLINKS = NO
763
764 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
765 # plain latex in the generated Makefile. Set this option to YES to get a
766 # higher quality PDF documentation.
767
768 USE_PDFLATEX = NO
769
770 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
771 # command to the generated LaTeX files. This will instruct LaTeX to keep
772 # running if errors occur, instead of asking the user for help.
773 # This option is also used when generating formulas in HTML.
774
775 LATEX_BATCHMODE = NO
776
777 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
778 # include the index chapters (such as File Index, Compound Index, etc.)
779 # in the output.
780
781 LATEX_HIDE_INDICES = NO
782
783 #---------------------------------------------------------------------------
784 # configuration options related to the RTF output
785 #---------------------------------------------------------------------------
786
787 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
788 # The RTF output is optimized for Word 97 and may not look very pretty with
789 # other RTF readers or editors.
790
791 GENERATE_RTF = NO
792
793 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
794 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
795 # put in front of it. If left blank `rtf' will be used as the default path.
796
797 RTF_OUTPUT = rtf
798
799 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
800 # RTF documents. This may be useful for small projects and may help to
801 # save some trees in general.
802
803 COMPACT_RTF = NO
804
805 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
806 # will contain hyperlink fields. The RTF file will
807 # contain links (just like the HTML output) instead of page references.
808 # This makes the output suitable for online browsing using WORD or other
809 # programs which support those fields.
810 # Note: wordpad (write) and others do not support links.
811
812 RTF_HYPERLINKS = NO
813
814 # Load stylesheet definitions from file. Syntax is similar to doxygen's
815 # config file, i.e. a series of assignments. You only have to provide
816 # replacements, missing definitions are set to their default value.
817
818 RTF_STYLESHEET_FILE =
819
820 # Set optional variables used in the generation of an rtf document.
821 # Syntax is similar to doxygen's config file.
822
823 RTF_EXTENSIONS_FILE =
824
825 #---------------------------------------------------------------------------
826 # configuration options related to the man page output
827 #---------------------------------------------------------------------------
828
829 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
830 # generate man pages
831
832 GENERATE_MAN = YES
833
834 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
835 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
836 # put in front of it. If left blank `man' will be used as the default path.
837
838 MAN_OUTPUT = man
839
840 # The MAN_EXTENSION tag determines the extension that is added to
841 # the generated man pages (default is the subroutine's section .3)
842
843 MAN_EXTENSION = .3
844
845 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
846 # then it will generate one additional man file for each entity
847 # documented in the real man page(s). These additional files
848 # only source the real man page, but without them the man command
849 # would be unable to find the correct page. The default is NO.
850
851 MAN_LINKS = NO
852
853 #---------------------------------------------------------------------------
854 # configuration options related to the XML output
855 #---------------------------------------------------------------------------
856
857 # If the GENERATE_XML tag is set to YES Doxygen will
858 # generate an XML file that captures the structure of
859 # the code including all documentation.
860
861 GENERATE_XML = NO
862
863 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
864 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
865 # put in front of it. If left blank `xml' will be used as the default path.
866
867 XML_OUTPUT = xml
868
869 # The XML_SCHEMA tag can be used to specify an XML schema,
870 # which can be used by a validating XML parser to check the
871 # syntax of the XML files.
872
873 XML_SCHEMA =
874
875 # The XML_DTD tag can be used to specify an XML DTD,
876 # which can be used by a validating XML parser to check the
877 # syntax of the XML files.
878
879 XML_DTD =
880
881 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
882 # dump the program listings (including syntax highlighting
883 # and cross-referencing information) to the XML output. Note that
884 # enabling this will significantly increase the size of the XML output.
885
886 XML_PROGRAMLISTING = YES
887
888 #---------------------------------------------------------------------------
889 # configuration options for the AutoGen Definitions output
890 #---------------------------------------------------------------------------
891
892 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
893 # generate an AutoGen Definitions (see autogen.sf.net) file
894 # that captures the structure of the code including all
895 # documentation. Note that this feature is still experimental
896 # and incomplete at the moment.
897
898 GENERATE_AUTOGEN_DEF = NO
899
900 #---------------------------------------------------------------------------
901 # configuration options related to the Perl module output
902 #---------------------------------------------------------------------------
903
904 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
905 # generate a Perl module file that captures the structure of
906 # the code including all documentation. Note that this
907 # feature is still experimental and incomplete at the
908 # moment.
909
910 GENERATE_PERLMOD = NO
911
912 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
913 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
914 # to generate PDF and DVI output from the Perl module output.
915
916 PERLMOD_LATEX = NO
917
918 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
919 # nicely formatted so it can be parsed by a human reader. This is useful
920 # if you want to understand what is going on. On the other hand, if this
921 # tag is set to NO the size of the Perl module output will be much smaller
922 # and Perl will parse it just the same.
923
924 PERLMOD_PRETTY = YES
925
926 # The names of the make variables in the generated doxyrules.make file
927 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
928 # This is useful so different doxyrules.make files included by the same
929 # Makefile don't overwrite each other's variables.
930
931 PERLMOD_MAKEVAR_PREFIX =
932
933 #---------------------------------------------------------------------------
934 # Configuration options related to the preprocessor
935 #---------------------------------------------------------------------------
936
937 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
938 # evaluate all C-preprocessor directives found in the sources and include
939 # files.
940
941 ENABLE_PREPROCESSING = YES
942
943 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
944 # names in the source code. If set to NO (the default) only conditional
945 # compilation will be performed. Macro expansion can be done in a controlled
946 # way by setting EXPAND_ONLY_PREDEF to YES.
947
948 MACRO_EXPANSION = NO
949
950 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
951 # then the macro expansion is limited to the macros specified with the
952 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
953
954 EXPAND_ONLY_PREDEF = NO
955
956 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
957 # in the INCLUDE_PATH (see below) will be search if a #include is found.
958
959 SEARCH_INCLUDES = YES
960
961 # The INCLUDE_PATH tag can be used to specify one or more directories that
962 # contain include files that are not input files but should be processed by
963 # the preprocessor.
964
965 INCLUDE_PATH =
966
967 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
968 # patterns (like *.h and *.hpp) to filter out the header-files in the
969 # directories. If left blank, the patterns specified with FILE_PATTERNS will
970 # be used.
971
972 INCLUDE_FILE_PATTERNS =
973
974 # The PREDEFINED tag can be used to specify one or more macro names that
975 # are defined before the preprocessor is started (similar to the -D option of
976 # gcc). The argument of the tag is a list of macros of the form: name
977 # or name=definition (no spaces). If the definition and the = are
978 # omitted =1 is assumed. To prevent a macro definition from being
979 # undefined via #undef or recursively expanded use the := operator
980 # instead of the = operator.
981
982 PREDEFINED =
983
984 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
985 # this tag can be used to specify a list of macro names that should be expanded.
986 # The macro definition that is found in the sources will be used.
987 # Use the PREDEFINED tag if you want to use a different macro definition.
988
989 EXPAND_AS_DEFINED =
990
991 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
992 # doxygen's preprocessor will remove all function-like macros that are alone
993 # on a line, have an all uppercase name, and do not end with a semicolon. Such
994 # function macros are typically used for boiler-plate code, and will confuse
995 # the parser if not removed.
996
997 SKIP_FUNCTION_MACROS = YES
998
999 #---------------------------------------------------------------------------
1000 # Configuration::additions related to external references
1001 #---------------------------------------------------------------------------
1002
1003 # The TAGFILES option can be used to specify one or more tagfiles.
1004 # Optionally an initial location of the external documentation
1005 # can be added for each tagfile. The format of a tag file without
1006 # this location is as follows:
1007 # TAGFILES = file1 file2 ...
1008 # Adding location for the tag files is done as follows:
1009 # TAGFILES = file1=loc1 "file2 = loc2" ...
1010 # where "loc1" and "loc2" can be relative or absolute paths or
1011 # URLs. If a location is present for each tag, the installdox tool
1012 # does not have to be run to correct the links.
1013 # Note that each tag file must have a unique name
1014 # (where the name does NOT include the path)
1015 # If a tag file is not located in the directory in which doxygen
1016 # is run, you must also specify the path to the tagfile here.
1017
1018 TAGFILES =
1019
1020 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1021 # a tag file that is based on the input files it reads.
1022
1023 GENERATE_TAGFILE =
1024
1025 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1026 # in the class index. If set to NO only the inherited external classes
1027 # will be listed.
1028
1029 ALLEXTERNALS = NO
1030
1031 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1032 # in the modules index. If set to NO, only the current project's groups will
1033 # be listed.
1034
1035 EXTERNAL_GROUPS = YES
1036
1037 # The PERL_PATH should be the absolute path and name of the perl script
1038 # interpreter (i.e. the result of `which perl').
1039
1040 PERL_PATH = /usr/bin/perl
1041
1042 #---------------------------------------------------------------------------
1043 # Configuration options related to the dot tool
1044 #---------------------------------------------------------------------------
1045
1046 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1047 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1048 # or super classes. Setting the tag to NO turns the diagrams off. Note that
1049 # this option is superseded by the HAVE_DOT option below. This is only a
1050 # fallback. It is recommended to install and use dot, since it yields more
1051 # powerful graphs.
1052
1053 CLASS_DIAGRAMS = YES
1054
1055 # If set to YES, the inheritance and collaboration graphs will hide
1056 # inheritance and usage relations if the target is undocumented
1057 # or is not a class.
1058
1059 HIDE_UNDOC_RELATIONS = YES
1060
1061 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1062 # available from the path. This tool is part of Graphviz, a graph visualization
1063 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
1064 # have no effect if this option is set to NO (the default)
1065
1066 HAVE_DOT = NO
1067
1068 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1069 # will generate a graph for each documented class showing the direct and
1070 # indirect inheritance relations. Setting this tag to YES will force the
1071 # the CLASS_DIAGRAMS tag to NO.
1072
1073 CLASS_GRAPH = YES
1074
1075 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1076 # will generate a graph for each documented class showing the direct and
1077 # indirect implementation dependencies (inheritance, containment, and
1078 # class references variables) of the class with other documented classes.
1079
1080 COLLABORATION_GRAPH = YES
1081
1082 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1083 # will generate a graph for groups, showing the direct groups dependencies
1084
1085 GROUP_GRAPHS = YES
1086
1087 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1088 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1089 # Language.
1090
1091 UML_LOOK = NO
1092
1093 # If set to YES, the inheritance and collaboration graphs will show the
1094 # relations between templates and their instances.
1095
1096 TEMPLATE_RELATIONS = NO
1097
1098 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1099 # tags are set to YES then doxygen will generate a graph for each documented
1100 # file showing the direct and indirect include dependencies of the file with
1101 # other documented files.
1102
1103 INCLUDE_GRAPH = YES
1104
1105 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1106 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1107 # documented header file showing the documented files that directly or
1108 # indirectly include this file.
1109
1110 INCLUDED_BY_GRAPH = YES
1111
1112 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1113 # generate a call dependency graph for every global function or class method.
1114 # Note that enabling this option will significantly increase the time of a run.
1115 # So in most cases it will be better to enable call graphs for selected
1116 # functions only using the \callgraph command.
1117
1118 CALL_GRAPH = NO
1119
1120 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1121 # will graphical hierarchy of all classes instead of a textual one.
1122
1123 GRAPHICAL_HIERARCHY = YES
1124
1125 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1126 # then doxygen will show the dependencies a directory has on other directories
1127 # in a graphical way. The dependency relations are determined by the #include
1128 # relations between the files in the directories.
1129
1130 DIRECTORY_GRAPH = YES
1131
1132 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1133 # generated by dot. Possible values are png, jpg, or gif
1134 # If left blank png will be used.
1135
1136 DOT_IMAGE_FORMAT = png
1137
1138 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1139 # found. If left blank, it is assumed the dot tool can be found in the path.
1140
1141 DOT_PATH =
1142
1143 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1144 # contain dot files that are included in the documentation (see the
1145 # \dotfile command).
1146
1147 DOTFILE_DIRS =
1148
1149 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1150 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1151 # this value, doxygen will try to truncate the graph, so that it fits within
1152 # the specified constraint. Beware that most browsers cannot cope with very
1153 # large images.
1154
1155 MAX_DOT_GRAPH_WIDTH = 1024
1156
1157 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1158 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1159 # this value, doxygen will try to truncate the graph, so that it fits within
1160 # the specified constraint. Beware that most browsers cannot cope with very
1161 # large images.
1162
1163 MAX_DOT_GRAPH_HEIGHT = 1024
1164
1165 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1166 # graphs generated by dot. A depth value of 3 means that only nodes reachable
1167 # from the root by following a path via at most 3 edges will be shown. Nodes
1168 # that lay further from the root node will be omitted. Note that setting this
1169 # option to 1 or 2 may greatly reduce the computation time needed for large
1170 # code bases. Also note that a graph may be further truncated if the graph's
1171 # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH
1172 # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
1173 # the graph is not depth-constrained.
1174
1175 MAX_DOT_GRAPH_DEPTH = 0
1176
1177 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1178 # background. This is disabled by default, which results in a white background.
1179 # Warning: Depending on the platform used, enabling this option may lead to
1180 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
1181 # read).
1182
1183 DOT_TRANSPARENT = NO
1184
1185 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1186 # files in one run (i.e. multiple -o and -T options on the command line). This
1187 # makes dot run faster, but since only newer versions of dot (>1.8.10)
1188 # support this, this feature is disabled by default.
1189
1190 DOT_MULTI_TARGETS = NO
1191
1192 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1193 # generate a legend page explaining the meaning of the various boxes and
1194 # arrows in the dot generated graphs.
1195
1196 GENERATE_LEGEND = YES
1197
1198 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1199 # remove the intermediate dot files that are used to generate
1200 # the various graphs.
1201
1202 DOT_CLEANUP = YES
1203
1204 #---------------------------------------------------------------------------
1205 # Configuration::additions related to the search engine
1206 #---------------------------------------------------------------------------
1207
1208 # The SEARCHENGINE tag specifies whether or not a search engine should be
1209 # used. If set to NO the values of all tags below this one will be ignored.
1210
1211 SEARCHENGINE = NO
+0
-182
1.3.0/INSTALL less more
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.
+0
-24
1.3.0/Makefile.am less more
0 ## Process this file with automake to produce Makefile.in
1 ## Created by Anjuta - will be overwritten
2 ## If you don't want it to overwrite it,
3 ## Please disable it in the Anjuta project configuration
4
5 SUBDIRS = intl po src examples bindings
6
7 pkgconfigdir = $(libdir)/pkgconfig
8 pkgconfig_DATA = libhdate.pc
9
10 libhdatedocdir = ${prefix}/share/doc/libhdate0
11 libhdatedoc_DATA = \
12 README\
13 hdate_README\
14 COPYING\
15 AUTHORS\
16 ChangeLog\
17 INSTALL\
18 NEWS\
19 TODO\
20 USE\
21 ABOUT-NLS
22
23 EXTRA_DIST = $(libhdatedoc_DATA) libhdate.pc.in libhdate.spec libhdate.spec.in
+0
-651
1.3.0/Makefile.in less more
0 # Makefile.in generated by automake 1.7.9 from Makefile.am.
1 # @configure_input@
2
3 # Copyright 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
4 # Free Software Foundation, Inc.
5 # This Makefile.in is free software; the Free Software Foundation
6 # gives unlimited permission to copy and/or distribute it,
7 # with or without modifications, as long as this notice is preserved.
8
9 # This program is distributed in the hope that it will be useful,
10 # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
11 # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
12 # PARTICULAR PURPOSE.
13
14 @SET_MAKE@
15
16 srcdir = @srcdir@
17 top_srcdir = @top_srcdir@
18 VPATH = @srcdir@
19 pkgdatadir = $(datadir)/@PACKAGE@
20 pkglibdir = $(libdir)/@PACKAGE@
21 pkgincludedir = $(includedir)/@PACKAGE@
22 top_builddir = .
23
24 am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
25 INSTALL = @INSTALL@
26 install_sh_DATA = $(install_sh) -c -m 644
27 install_sh_PROGRAM = $(install_sh) -c
28 install_sh_SCRIPT = $(install_sh) -c
29 INSTALL_HEADER = $(INSTALL_DATA)
30 transform = $(program_transform_name)
31 NORMAL_INSTALL = :
32 PRE_INSTALL = :
33 POST_INSTALL = :
34 NORMAL_UNINSTALL = :
35 PRE_UNINSTALL = :
36 POST_UNINSTALL = :
37 host_triplet = @host@
38 ACLOCAL = @ACLOCAL@
39 ALLOCA = @ALLOCA@
40 AMDEP_FALSE = @AMDEP_FALSE@
41 AMDEP_TRUE = @AMDEP_TRUE@
42 AMTAR = @AMTAR@
43 AR = @AR@
44 AUTOCONF = @AUTOCONF@
45 AUTOHEADER = @AUTOHEADER@
46 AUTOMAKE = @AUTOMAKE@
47 AWK = @AWK@
48 BUILD_INCLUDED_LIBINTL = @BUILD_INCLUDED_LIBINTL@
49 CATOBJEXT = @CATOBJEXT@
50 CC = @CC@
51 CCDEPMODE = @CCDEPMODE@
52 CFLAGS = @CFLAGS@
53 CPP = @CPP@
54 CPPFLAGS = @CPPFLAGS@
55 CXX = @CXX@
56 CXXCPP = @CXXCPP@
57 CXXDEPMODE = @CXXDEPMODE@
58 CXXFLAGS = @CXXFLAGS@
59 CYGPATH_W = @CYGPATH_W@
60 DATADIRNAME = @DATADIRNAME@
61 DEFS = @DEFS@
62 DEPDIR = @DEPDIR@
63 ECHO = @ECHO@
64 ECHO_C = @ECHO_C@
65 ECHO_N = @ECHO_N@
66 ECHO_T = @ECHO_T@
67 EGREP = @EGREP@
68 EXEEXT = @EXEEXT@
69 F77 = @F77@
70 FFLAGS = @FFLAGS@
71 GENCAT = @GENCAT@
72 GLIBC2 = @GLIBC2@
73 GLIBC21 = @GLIBC21@
74 GMSGFMT = @GMSGFMT@
75 HAVE_ASPRINTF = @HAVE_ASPRINTF@
76 HAVE_POSIX_PRINTF = @HAVE_POSIX_PRINTF@
77 HAVE_SNPRINTF = @HAVE_SNPRINTF@
78 HAVE_WPRINTF = @HAVE_WPRINTF@
79 INSTALL_DATA = @INSTALL_DATA@
80 INSTALL_PROGRAM = @INSTALL_PROGRAM@
81 INSTALL_SCRIPT = @INSTALL_SCRIPT@
82 INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
83 INSTOBJEXT = @INSTOBJEXT@
84 INTLBISON = @INTLBISON@
85 INTLLIBS = @INTLLIBS@
86 INTLOBJS = @INTLOBJS@
87 INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@
88 INTL_MACOSX_LIBS = @INTL_MACOSX_LIBS@
89 LDFLAGS = @LDFLAGS@
90 LIBICONV = @LIBICONV@
91 LIBINTL = @LIBINTL@
92 LIBOBJS = @LIBOBJS@
93 LIBS = @LIBS@
94 LIBTOOL = @LIBTOOL@
95 LN_S = @LN_S@
96 LTLIBICONV = @LTLIBICONV@
97 LTLIBINTL = @LTLIBINTL@
98 LTLIBOBJS = @LTLIBOBJS@
99 MAINT = @MAINT@
100 MAINTAINER_MODE_FALSE = @MAINTAINER_MODE_FALSE@
101 MAINTAINER_MODE_TRUE = @MAINTAINER_MODE_TRUE@
102 MAKEINFO = @MAKEINFO@
103 MKINSTALLDIRS = @MKINSTALLDIRS@
104 MSGFMT = @MSGFMT@
105 MSGMERGE = @MSGMERGE@
106 OBJEXT = @OBJEXT@
107 PACKAGE = @PACKAGE@
108 PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
109 PACKAGE_NAME = @PACKAGE_NAME@
110 PACKAGE_STRING = @PACKAGE_STRING@
111 PACKAGE_TARNAME = @PACKAGE_TARNAME@
112 PACKAGE_VERSION = @PACKAGE_VERSION@
113 PATH_SEPARATOR = @PATH_SEPARATOR@
114 PA_MODULES_PATH = @PA_MODULES_PATH@
115 PE_CFLAGS = @PE_CFLAGS@
116 PE_MODULES_PATH = @PE_MODULES_PATH@
117 PKG_CONFIG = @PKG_CONFIG@
118 POSUB = @POSUB@
119 PY_CFLAGS = @PY_CFLAGS@
120 PY_MODULES_PATH = @PY_MODULES_PATH@
121 RANLIB = @RANLIB@
122 SET_MAKE = @SET_MAKE@
123 SHELL = @SHELL@
124 STRIP = @STRIP@
125 USE_INCLUDED_LIBINTL = @USE_INCLUDED_LIBINTL@
126 USE_NLS = @USE_NLS@
127 VERSION = @VERSION@
128 VERSION_INFO = @VERSION_INFO@
129 WITH_EXAMPLES_FALSE = @WITH_EXAMPLES_FALSE@
130 WITH_EXAMPLES_TRUE = @WITH_EXAMPLES_TRUE@
131 WITH_HCAL_FALSE = @WITH_HCAL_FALSE@
132 WITH_HCAL_TRUE = @WITH_HCAL_TRUE@
133 WITH_PASCAL_FALSE = @WITH_PASCAL_FALSE@
134 WITH_PASCAL_TRUE = @WITH_PASCAL_TRUE@
135 WITH_PERL_FALSE = @WITH_PERL_FALSE@
136 WITH_PERL_TRUE = @WITH_PERL_TRUE@
137 WITH_PYTHON_FALSE = @WITH_PYTHON_FALSE@
138 WITH_PYTHON_TRUE = @WITH_PYTHON_TRUE@
139 XGETTEXT = @XGETTEXT@
140 ac_ct_AR = @ac_ct_AR@
141 ac_ct_CC = @ac_ct_CC@
142 ac_ct_CXX = @ac_ct_CXX@
143 ac_ct_F77 = @ac_ct_F77@
144 ac_ct_RANLIB = @ac_ct_RANLIB@
145 ac_ct_STRIP = @ac_ct_STRIP@
146 am__fastdepCC_FALSE = @am__fastdepCC_FALSE@
147 am__fastdepCC_TRUE = @am__fastdepCC_TRUE@
148 am__fastdepCXX_FALSE = @am__fastdepCXX_FALSE@
149 am__fastdepCXX_TRUE = @am__fastdepCXX_TRUE@
150 am__include = @am__include@
151 am__leading_dot = @am__leading_dot@
152 am__quote = @am__quote@
153 bindir = @bindir@
154 build = @build@
155 build_alias = @build_alias@
156 build_cpu = @build_cpu@
157 build_os = @build_os@
158 build_vendor = @build_vendor@
159 datadir = @datadir@
160 exec_prefix = @exec_prefix@
161 have_pascal = @have_pascal@
162 have_perl = @have_perl@
163 have_python = @have_python@
164 have_swig = @have_swig@
165 host = @host@
166 host_alias = @host_alias@
167 host_cpu = @host_cpu@
168 host_os = @host_os@
169 host_vendor = @host_vendor@
170 includedir = @includedir@
171 infodir = @infodir@
172 install_sh = @install_sh@
173 libdir = @libdir@
174 libexecdir = @libexecdir@
175 localstatedir = @localstatedir@
176 mandir = @mandir@
177 oldincludedir = @oldincludedir@
178 prefix = @prefix@
179 program_transform_name = @program_transform_name@
180 sbindir = @sbindir@
181 sharedstatedir = @sharedstatedir@
182 sysconfdir = @sysconfdir@
183 target_alias = @target_alias@
184
185 SUBDIRS = intl po src examples bindings debian
186
187 pkgconfigdir = $(libdir)/pkgconfig
188 pkgconfig_DATA = libhdate.pc
189
190 libhdatedocdir = ${prefix}/share/doc/libhdate0
191 libhdatedoc_DATA = \
192 README\
193 hdate_README\
194 COPYING\
195 AUTHORS\
196 ChangeLog\
197 INSTALL\
198 NEWS\
199 TODO\
200 USE\
201 ABOUT-NLS
202
203
204 EXTRA_DIST = $(libhdatedoc_DATA) libhdate.pc.in libhdate.spec libhdate.spec.in
205 subdir = .
206 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
207 mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
208 CONFIG_CLEAN_FILES = libhdate.spec libhdate.pc intl/Makefile
209 DIST_SOURCES =
210 DATA = $(libhdatedoc_DATA) $(pkgconfig_DATA)
211
212
213 RECURSIVE_TARGETS = info-recursive dvi-recursive pdf-recursive \
214 ps-recursive install-info-recursive uninstall-info-recursive \
215 all-recursive install-data-recursive install-exec-recursive \
216 installdirs-recursive install-recursive uninstall-recursive \
217 check-recursive installcheck-recursive
218 DIST_COMMON = README $(srcdir)/Makefile.in $(srcdir)/configure \
219 ABOUT-NLS AUTHORS COPYING ChangeLog INSTALL Makefile.am NEWS \
220 TODO aclocal.m4 compile config.guess config.sub configure.in \
221 depcomp install-sh libhdate.pc.in libhdate.spec.in ltmain.sh \
222 missing mkinstalldirs
223 DIST_SUBDIRS = $(SUBDIRS)
224 all: all-recursive
225
226 .SUFFIXES:
227
228 am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
229 configure.lineno
230 $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4)
231 cd $(top_srcdir) && \
232 $(AUTOMAKE) --gnu Makefile
233 Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
234 cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)
235
236 $(top_builddir)/config.status: $(srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
237 $(SHELL) ./config.status --recheck
238 $(srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(srcdir)/configure.in $(ACLOCAL_M4) $(CONFIGURE_DEPENDENCIES)
239 cd $(srcdir) && $(AUTOCONF)
240
241 $(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.in
242 cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
243 libhdate.spec: $(top_builddir)/config.status libhdate.spec.in
244 cd $(top_builddir) && $(SHELL) ./config.status $@
245 libhdate.pc: $(top_builddir)/config.status libhdate.pc.in
246 cd $(top_builddir) && $(SHELL) ./config.status $@
247 intl/Makefile: $(top_builddir)/config.status $(top_srcdir)/intl/Makefile.in
248 cd $(top_builddir) && $(SHELL) ./config.status $@
249
250 mostlyclean-libtool:
251 -rm -f *.lo
252
253 clean-libtool:
254 -rm -rf .libs _libs
255
256 distclean-libtool:
257 -rm -f libtool
258 uninstall-info-am:
259 libhdatedocDATA_INSTALL = $(INSTALL_DATA)
260 install-libhdatedocDATA: $(libhdatedoc_DATA)
261 @$(NORMAL_INSTALL)
262 $(mkinstalldirs) $(DESTDIR)$(libhdatedocdir)
263 @list='$(libhdatedoc_DATA)'; for p in $$list; do \
264 if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
265 f="`echo $$p | sed -e 's|^.*/||'`"; \
266 echo " $(libhdatedocDATA_INSTALL) $$d$$p $(DESTDIR)$(libhdatedocdir)/$$f"; \
267 $(libhdatedocDATA_INSTALL) $$d$$p $(DESTDIR)$(libhdatedocdir)/$$f; \
268 done
269
270 uninstall-libhdatedocDATA:
271 @$(NORMAL_UNINSTALL)
272 @list='$(libhdatedoc_DATA)'; for p in $$list; do \
273 f="`echo $$p | sed -e 's|^.*/||'`"; \
274 echo " rm -f $(DESTDIR)$(libhdatedocdir)/$$f"; \
275 rm -f $(DESTDIR)$(libhdatedocdir)/$$f; \
276 done
277 pkgconfigDATA_INSTALL = $(INSTALL_DATA)
278 install-pkgconfigDATA: $(pkgconfig_DATA)
279 @$(NORMAL_INSTALL)
280 $(mkinstalldirs) $(DESTDIR)$(pkgconfigdir)
281 @list='$(pkgconfig_DATA)'; for p in $$list; do \
282 if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
283 f="`echo $$p | sed -e 's|^.*/||'`"; \
284 echo " $(pkgconfigDATA_INSTALL) $$d$$p $(DESTDIR)$(pkgconfigdir)/$$f"; \
285 $(pkgconfigDATA_INSTALL) $$d$$p $(DESTDIR)$(pkgconfigdir)/$$f; \
286 done
287
288 uninstall-pkgconfigDATA:
289 @$(NORMAL_UNINSTALL)
290 @list='$(pkgconfig_DATA)'; for p in $$list; do \
291 f="`echo $$p | sed -e 's|^.*/||'`"; \
292 echo " rm -f $(DESTDIR)$(pkgconfigdir)/$$f"; \
293 rm -f $(DESTDIR)$(pkgconfigdir)/$$f; \
294 done
295
296 # This directory's subdirectories are mostly independent; you can cd
297 # into them and run `make' without going through this Makefile.
298 # To change the values of `make' variables: instead of editing Makefiles,
299 # (1) if the variable is set in `config.status', edit `config.status'
300 # (which will cause the Makefiles to be regenerated when you run `make');
301 # (2) otherwise, pass the desired values on the `make' command line.
302 $(RECURSIVE_TARGETS):
303 @set fnord $$MAKEFLAGS; amf=$$2; \
304 dot_seen=no; \
305 target=`echo $@ | sed s/-recursive//`; \
306 list='$(SUBDIRS)'; for subdir in $$list; do \
307 echo "Making $$target in $$subdir"; \
308 if test "$$subdir" = "."; then \
309 dot_seen=yes; \
310 local_target="$$target-am"; \
311 else \
312 local_target="$$target"; \
313 fi; \
314 (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
315 || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
316 done; \
317 if test "$$dot_seen" = "no"; then \
318 $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
319 fi; test -z "$$fail"
320
321 mostlyclean-recursive clean-recursive distclean-recursive \
322 maintainer-clean-recursive:
323 @set fnord $$MAKEFLAGS; amf=$$2; \
324 dot_seen=no; \
325 case "$@" in \
326 distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
327 *) list='$(SUBDIRS)' ;; \
328 esac; \
329 rev=''; for subdir in $$list; do \
330 if test "$$subdir" = "."; then :; else \
331 rev="$$subdir $$rev"; \
332 fi; \
333 done; \
334 rev="$$rev ."; \
335 target=`echo $@ | sed s/-recursive//`; \
336 for subdir in $$rev; do \
337 echo "Making $$target in $$subdir"; \
338 if test "$$subdir" = "."; then \
339 local_target="$$target-am"; \
340 else \
341 local_target="$$target"; \
342 fi; \
343 (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
344 || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
345 done && test -z "$$fail"
346 tags-recursive:
347 list='$(SUBDIRS)'; for subdir in $$list; do \
348 test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
349 done
350 ctags-recursive:
351 list='$(SUBDIRS)'; for subdir in $$list; do \
352 test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
353 done
354
355 ETAGS = etags
356 ETAGSFLAGS =
357
358 CTAGS = ctags
359 CTAGSFLAGS =
360
361 tags: TAGS
362
363 ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
364 list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
365 unique=`for i in $$list; do \
366 if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
367 done | \
368 $(AWK) ' { files[$$0] = 1; } \
369 END { for (i in files) print i; }'`; \
370 mkid -fID $$unique
371
372 TAGS: tags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
373 $(TAGS_FILES) $(LISP)
374 tags=; \
375 here=`pwd`; \
376 if (etags --etags-include --version) >/dev/null 2>&1; then \
377 include_option=--etags-include; \
378 else \
379 include_option=--include; \
380 fi; \
381 list='$(SUBDIRS)'; for subdir in $$list; do \
382 if test "$$subdir" = .; then :; else \
383 test -f $$subdir/TAGS && \
384 tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
385 fi; \
386 done; \
387 list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
388 unique=`for i in $$list; do \
389 if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
390 done | \
391 $(AWK) ' { files[$$0] = 1; } \
392 END { for (i in files) print i; }'`; \
393 test -z "$(ETAGS_ARGS)$$tags$$unique" \
394 || $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
395 $$tags $$unique
396
397 ctags: CTAGS
398 CTAGS: ctags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
399 $(TAGS_FILES) $(LISP)
400 tags=; \
401 here=`pwd`; \
402 list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
403 unique=`for i in $$list; do \
404 if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
405 done | \
406 $(AWK) ' { files[$$0] = 1; } \
407 END { for (i in files) print i; }'`; \
408 test -z "$(CTAGS_ARGS)$$tags$$unique" \
409 || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
410 $$tags $$unique
411
412 GTAGS:
413 here=`$(am__cd) $(top_builddir) && pwd` \
414 && cd $(top_srcdir) \
415 && gtags -i $(GTAGS_ARGS) $$here
416
417 distclean-tags:
418 -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
419 DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
420
421 top_distdir = .
422 distdir = $(PACKAGE)-$(VERSION)
423
424 am__remove_distdir = \
425 { test ! -d $(distdir) \
426 || { find $(distdir) -type d ! -perm -200 -exec chmod u+w {} ';' \
427 && rm -fr $(distdir); }; }
428
429 GZIP_ENV = --best
430 distuninstallcheck_listfiles = find . -type f -print
431 distcleancheck_listfiles = find . -type f -print
432
433 distdir: $(DISTFILES)
434 $(am__remove_distdir)
435 mkdir $(distdir)
436 $(mkinstalldirs) $(distdir)/. $(distdir)/intl $(distdir)/po
437 @srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; \
438 topsrcdirstrip=`echo "$(top_srcdir)" | sed 's|.|.|g'`; \
439 list='$(DISTFILES)'; for file in $$list; do \
440 case $$file in \
441 $(srcdir)/*) file=`echo "$$file" | sed "s|^$$srcdirstrip/||"`;; \
442 $(top_srcdir)/*) file=`echo "$$file" | sed "s|^$$topsrcdirstrip/|$(top_builddir)/|"`;; \
443 esac; \
444 if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
445 dir=`echo "$$file" | sed -e 's,/[^/]*$$,,'`; \
446 if test "$$dir" != "$$file" && test "$$dir" != "."; then \
447 dir="/$$dir"; \
448 $(mkinstalldirs) "$(distdir)$$dir"; \
449 else \
450 dir=''; \
451 fi; \
452 if test -d $$d/$$file; then \
453 if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
454 cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
455 fi; \
456 cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
457 else \
458 test -f $(distdir)/$$file \
459 || cp -p $$d/$$file $(distdir)/$$file \
460 || exit 1; \
461 fi; \
462 done
463 list='$(SUBDIRS)'; for subdir in $$list; do \
464 if test "$$subdir" = .; then :; else \
465 test -d $(distdir)/$$subdir \
466 || mkdir $(distdir)/$$subdir \
467 || exit 1; \
468 (cd $$subdir && \
469 $(MAKE) $(AM_MAKEFLAGS) \
470 top_distdir="$(top_distdir)" \
471 distdir=../$(distdir)/$$subdir \
472 distdir) \
473 || exit 1; \
474 fi; \
475 done
476 -find $(distdir) -type d ! -perm -777 -exec chmod a+rwx {} \; -o \
477 ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
478 ! -type d ! -perm -400 -exec chmod a+r {} \; -o \
479 ! -type d ! -perm -444 -exec $(SHELL) $(install_sh) -c -m a+r {} {} \; \
480 || chmod -R a+r $(distdir)
481 dist-gzip: distdir
482 $(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
483 $(am__remove_distdir)
484
485 dist dist-all: distdir
486 $(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
487 $(am__remove_distdir)
488
489 # This target untars the dist file and tries a VPATH configuration. Then
490 # it guarantees that the distribution is self-contained by making another
491 # tarfile.
492 distcheck: dist
493 $(am__remove_distdir)
494 GZIP=$(GZIP_ENV) gunzip -c $(distdir).tar.gz | $(AMTAR) xf -
495 chmod -R a-w $(distdir); chmod a+w $(distdir)
496 mkdir $(distdir)/_build
497 mkdir $(distdir)/_inst
498 chmod a-w $(distdir)
499 dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \
500 && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \
501 && cd $(distdir)/_build \
502 && ../configure --srcdir=.. --prefix="$$dc_install_base" \
503 --with-included-gettext \
504 $(DISTCHECK_CONFIGURE_FLAGS) \
505 && $(MAKE) $(AM_MAKEFLAGS) \
506 && $(MAKE) $(AM_MAKEFLAGS) dvi \
507 && $(MAKE) $(AM_MAKEFLAGS) check \
508 && $(MAKE) $(AM_MAKEFLAGS) install \
509 && $(MAKE) $(AM_MAKEFLAGS) installcheck \
510 && $(MAKE) $(AM_MAKEFLAGS) uninstall \
511 && $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \
512 distuninstallcheck \
513 && chmod -R a-w "$$dc_install_base" \
514 && ({ \
515 (cd ../.. && $(mkinstalldirs) "$$dc_destdir") \
516 && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \
517 && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \
518 && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \
519 distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \
520 } || { rm -rf "$$dc_destdir"; exit 1; }) \
521 && rm -rf "$$dc_destdir" \
522 && $(MAKE) $(AM_MAKEFLAGS) dist-gzip \
523 && rm -f $(distdir).tar.gz \
524 && $(MAKE) $(AM_MAKEFLAGS) distcleancheck
525 $(am__remove_distdir)
526 @echo "$(distdir).tar.gz is ready for distribution" | \
527 sed 'h;s/./=/g;p;x;p;x'
528 distuninstallcheck:
529 @cd $(distuninstallcheck_dir) \
530 && test `$(distuninstallcheck_listfiles) | wc -l` -le 1 \
531 || { echo "ERROR: files left after uninstall:" ; \
532 if test -n "$(DESTDIR)"; then \
533 echo " (check DESTDIR support)"; \
534 fi ; \
535 $(distuninstallcheck_listfiles) ; \
536 exit 1; } >&2
537 distcleancheck: distclean
538 @if test '$(srcdir)' = . ; then \
539 echo "ERROR: distcleancheck can only run from a VPATH build" ; \
540 exit 1 ; \
541 fi
542 @test `$(distcleancheck_listfiles) | wc -l` -eq 0 \
543 || { echo "ERROR: files left in build directory after distclean:" ; \
544 $(distcleancheck_listfiles) ; \
545 exit 1; } >&2
546 check-am: all-am
547 check: check-recursive
548 all-am: Makefile $(DATA)
549 installdirs: installdirs-recursive
550 installdirs-am:
551 $(mkinstalldirs) $(DESTDIR)$(libhdatedocdir) $(DESTDIR)$(pkgconfigdir)
552
553 install: install-recursive
554 install-exec: install-exec-recursive
555 install-data: install-data-recursive
556 uninstall: uninstall-recursive
557
558 install-am: all-am
559 @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
560
561 installcheck: installcheck-recursive
562 install-strip:
563 $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
564 install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
565 `test -z '$(STRIP)' || \
566 echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
567 mostlyclean-generic:
568
569 clean-generic:
570
571 distclean-generic:
572 -rm -f $(CONFIG_CLEAN_FILES)
573
574 maintainer-clean-generic:
575 @echo "This command is intended for maintainers to use"
576 @echo "it deletes files that may require special tools to rebuild."
577 clean: clean-recursive
578
579 clean-am: clean-generic clean-libtool mostlyclean-am
580
581 distclean: distclean-recursive
582 -rm -f $(am__CONFIG_DISTCLEAN_FILES)
583 -rm -f Makefile
584 distclean-am: clean-am distclean-generic distclean-libtool \
585 distclean-tags
586
587 dvi: dvi-recursive
588
589 dvi-am:
590
591 info: info-recursive
592
593 info-am:
594
595 install-data-am: install-libhdatedocDATA install-pkgconfigDATA
596
597 install-exec-am:
598
599 install-info: install-info-recursive
600
601 install-man:
602
603 installcheck-am:
604
605 maintainer-clean: maintainer-clean-recursive
606 -rm -f $(am__CONFIG_DISTCLEAN_FILES)
607 -rm -rf $(top_srcdir)/autom4te.cache
608 -rm -f Makefile
609 maintainer-clean-am: distclean-am maintainer-clean-generic
610
611 mostlyclean: mostlyclean-recursive
612
613 mostlyclean-am: mostlyclean-generic mostlyclean-libtool
614
615 pdf: pdf-recursive
616
617 pdf-am:
618
619 ps: ps-recursive
620
621 ps-am:
622
623 uninstall-am: uninstall-info-am uninstall-libhdatedocDATA \
624 uninstall-pkgconfigDATA
625
626 uninstall-info: uninstall-info-recursive
627
628 .PHONY: $(RECURSIVE_TARGETS) CTAGS GTAGS all all-am check check-am clean \
629 clean-generic clean-libtool clean-recursive ctags \
630 ctags-recursive dist dist-all dist-gzip distcheck distclean \
631 distclean-generic distclean-libtool distclean-recursive \
632 distclean-tags distcleancheck distdir distuninstallcheck dvi \
633 dvi-am dvi-recursive info info-am info-recursive install \
634 install-am install-data install-data-am install-data-recursive \
635 install-exec install-exec-am install-exec-recursive \
636 install-info install-info-am install-info-recursive \
637 install-libhdatedocDATA install-man install-pkgconfigDATA \
638 install-recursive install-strip installcheck installcheck-am \
639 installdirs installdirs-am installdirs-recursive \
640 maintainer-clean maintainer-clean-generic \
641 maintainer-clean-recursive mostlyclean mostlyclean-generic \
642 mostlyclean-libtool mostlyclean-recursive pdf pdf-am \
643 pdf-recursive ps ps-am ps-recursive tags tags-recursive \
644 uninstall uninstall-am uninstall-info-am \
645 uninstall-info-recursive uninstall-libhdatedocDATA \
646 uninstall-pkgconfigDATA uninstall-recursive
647
648 # Tell versions [3.59,3.63) of GNU make to not export all variables.
649 # Otherwise a system limit (for SysV at least) may be exceeded.
650 .NOEXPORT:
+0
-0
1.3.0/NEWS less more
(Empty file)
+0
-16
1.3.0/README less more
0 This library of functions are using the sorce code from
1 Amos Shapir's "hdate" package fixed and patched by Nadav Har'El.
2 See the original package's README (hdate_README)
3
4 LibHdate is a small C,C++ library for Hebrew dates,
5 holidays, and reading sequence (parasha). It is using
6 the sorce code from Amos Shapir's "hdate" package fixed and
7 patched by Nadav Har'El. The Torah reading sequence
8 is from tables by Zvi Har'El.
9
10 15 Adar II 5763 Shusan Purim
11 kobi zamir <kzamir@walla.co.il>
12 -------------------------------------
13
14 see USE file for usage.
15
+0
-17
1.3.0/TODO less more
0 libhdate (1.2.1)
1
2 * hcal example to print hebrew months and years
3 * configure.in - prefix for pascal, version for debian changlog
4 * mono binding usig swig
5 * ask eytan about the freanch
6 * clean the c code out of the pascal demo file ?
7
8 -- Yaacov Zamir <kzamir@wall.co.il> Tue, 15 Mar 2005 08:04:32
9
10 libhdate (0.16.3)
11
12 * Check date conversion, for more dates.
13 * More checks for Holyday function.
14 * More checks for Parasha function.
15
16 -- Yaacov Zamir <kzamir@wall.co.il> Mon, 21 Feb 2005 09:93:12
+0
-50
1.3.0/USE less more
0 use:
1 ----
2 gcc -c `pkg-config --cflags libhdate` <your code>.c
3 gcc `pkg-config --libs libhdate` <your code>.o -o <program name>
4
5
6 if you dont have pkg-config:
7 ----------------------------
8
9 gcc -c <your code>.c
10 gcc -lm -lhdate <your code>.o -o <program name>
11
12
13 kobi zamir <kzamir@walla.co.il>
14 -------------------------------------
15
16 -------------------------------
17 example code:
18 file: test.c
19 -------------------------------
20
21 #include <stdio.h>
22 #include <hdate.h>
23
24 #define TRUE 1
25 #define FALSE 0
26
27 int
28 main()
29 {
30 hdate_struct *h;
31
32 h = hdate_hdate( 0,0,0);
33
34 printf ("%s\n", hdate_get_format_date (h, FALSE) );
35
36 return 0;
37 }
38
39 --------------------------------
40 compile:
41 --------------------------------
42
43 gcc -lm -lhdate test.c -o test
44
45 --------------------------------
46 run:
47 --------------------------------
48
49 ./test
+0
-9476
1.3.0/aclocal.m4 less more
0 # generated automatically by aclocal 1.7.9 -*- Autoconf -*-
1
2 # Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002
3 # Free Software Foundation, Inc.
4 # This file is free software; the Free Software Foundation
5 # gives unlimited permission to copy and/or distribute it,
6 # with or without modifications, as long as this notice is preserved.
7
8 # This program is distributed in the hope that it will be useful,
9 # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
10 # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
11 # PARTICULAR PURPOSE.
12
13 # Do all the work for Automake. -*- Autoconf -*-
14
15 # This macro actually does too much some checks are only needed if
16 # your package does certain things. But this isn't really a big deal.
17
18 # Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
19 # Free Software Foundation, Inc.
20
21 # This program is free software; you can redistribute it and/or modify
22 # it under the terms of the GNU General Public License as published by
23 # the Free Software Foundation; either version 2, or (at your option)
24 # any later version.
25
26 # This program is distributed in the hope that it will be useful,
27 # but WITHOUT ANY WARRANTY; without even the implied warranty of
28 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
29 # GNU General Public License for more details.
30
31 # You should have received a copy of the GNU General Public License
32 # along with this program; if not, write to the Free Software
33 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
34 # 02111-1307, USA.
35
36 # serial 10
37
38 AC_PREREQ([2.54])
39
40 # Autoconf 2.50 wants to disallow AM_ names. We explicitly allow
41 # the ones we care about.
42 m4_pattern_allow([^AM_[A-Z]+FLAGS$])dnl
43
44 # AM_INIT_AUTOMAKE(PACKAGE, VERSION, [NO-DEFINE])
45 # AM_INIT_AUTOMAKE([OPTIONS])
46 # -----------------------------------------------
47 # The call with PACKAGE and VERSION arguments is the old style
48 # call (pre autoconf-2.50), which is being phased out. PACKAGE
49 # and VERSION should now be passed to AC_INIT and removed from
50 # the call to AM_INIT_AUTOMAKE.
51 # We support both call styles for the transition. After
52 # the next Automake release, Autoconf can make the AC_INIT
53 # arguments mandatory, and then we can depend on a new Autoconf
54 # release and drop the old call support.
55 AC_DEFUN([AM_INIT_AUTOMAKE],
56 [AC_REQUIRE([AM_SET_CURRENT_AUTOMAKE_VERSION])dnl
57 AC_REQUIRE([AC_PROG_INSTALL])dnl
58 # test to see if srcdir already configured
59 if test "`cd $srcdir && pwd`" != "`pwd`" &&
60 test -f $srcdir/config.status; then
61 AC_MSG_ERROR([source directory already configured; run "make distclean" there first])
62 fi
63
64 # test whether we have cygpath
65 if test -z "$CYGPATH_W"; then
66 if (cygpath --version) >/dev/null 2>/dev/null; then
67 CYGPATH_W='cygpath -w'
68 else
69 CYGPATH_W=echo
70 fi
71 fi
72 AC_SUBST([CYGPATH_W])
73
74 # Define the identity of the package.
75 dnl Distinguish between old-style and new-style calls.
76 m4_ifval([$2],
77 [m4_ifval([$3], [_AM_SET_OPTION([no-define])])dnl
78 AC_SUBST([PACKAGE], [$1])dnl
79 AC_SUBST([VERSION], [$2])],
80 [_AM_SET_OPTIONS([$1])dnl
81 AC_SUBST([PACKAGE], ['AC_PACKAGE_TARNAME'])dnl
82 AC_SUBST([VERSION], ['AC_PACKAGE_VERSION'])])dnl
83
84 _AM_IF_OPTION([no-define],,
85 [AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE", [Name of package])
86 AC_DEFINE_UNQUOTED(VERSION, "$VERSION", [Version number of package])])dnl
87
88 # Some tools Automake needs.
89 AC_REQUIRE([AM_SANITY_CHECK])dnl
90 AC_REQUIRE([AC_ARG_PROGRAM])dnl
91 AM_MISSING_PROG(ACLOCAL, aclocal-${am__api_version})
92 AM_MISSING_PROG(AUTOCONF, autoconf)
93 AM_MISSING_PROG(AUTOMAKE, automake-${am__api_version})
94 AM_MISSING_PROG(AUTOHEADER, autoheader)
95 AM_MISSING_PROG(MAKEINFO, makeinfo)
96 AM_MISSING_PROG(AMTAR, tar)
97 AM_PROG_INSTALL_SH
98 AM_PROG_INSTALL_STRIP
99 # We need awk for the "check" target. The system "awk" is bad on
100 # some platforms.
101 AC_REQUIRE([AC_PROG_AWK])dnl
102 AC_REQUIRE([AC_PROG_MAKE_SET])dnl
103 AC_REQUIRE([AM_SET_LEADING_DOT])dnl
104
105 _AM_IF_OPTION([no-dependencies],,
106 [AC_PROVIDE_IFELSE([AC_PROG_CC],
107 [_AM_DEPENDENCIES(CC)],
108 [define([AC_PROG_CC],
109 defn([AC_PROG_CC])[_AM_DEPENDENCIES(CC)])])dnl
110 AC_PROVIDE_IFELSE([AC_PROG_CXX],
111 [_AM_DEPENDENCIES(CXX)],
112 [define([AC_PROG_CXX],
113 defn([AC_PROG_CXX])[_AM_DEPENDENCIES(CXX)])])dnl
114 ])
115 ])
116
117
118 # When config.status generates a header, we must update the stamp-h file.
119 # This file resides in the same directory as the config header
120 # that is generated. The stamp files are numbered to have different names.
121
122 # Autoconf calls _AC_AM_CONFIG_HEADER_HOOK (when defined) in the
123 # loop where config.status creates the headers, so we can generate
124 # our stamp files there.
125 AC_DEFUN([_AC_AM_CONFIG_HEADER_HOOK],
126 [# Compute $1's index in $config_headers.
127 _am_stamp_count=1
128 for _am_header in $config_headers :; do
129 case $_am_header in
130 $1 | $1:* )
131 break ;;
132 * )
133 _am_stamp_count=`expr $_am_stamp_count + 1` ;;
134 esac
135 done
136 echo "timestamp for $1" >`AS_DIRNAME([$1])`/stamp-h[]$_am_stamp_count])
137
138 # Copyright 2002 Free Software Foundation, Inc.
139
140 # This program is free software; you can redistribute it and/or modify
141 # it under the terms of the GNU General Public License as published by
142 # the Free Software Foundation; either version 2, or (at your option)
143 # any later version.
144
145 # This program is distributed in the hope that it will be useful,
146 # but WITHOUT ANY WARRANTY; without even the implied warranty of
147 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
148 # GNU General Public License for more details.
149
150 # You should have received a copy of the GNU General Public License
151 # along with this program; if not, write to the Free Software
152 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
153
154 # AM_AUTOMAKE_VERSION(VERSION)
155 # ----------------------------
156 # Automake X.Y traces this macro to ensure aclocal.m4 has been
157 # generated from the m4 files accompanying Automake X.Y.
158 AC_DEFUN([AM_AUTOMAKE_VERSION],[am__api_version="1.7"])
159
160 # AM_SET_CURRENT_AUTOMAKE_VERSION
161 # -------------------------------
162 # Call AM_AUTOMAKE_VERSION so it can be traced.
163 # This function is AC_REQUIREd by AC_INIT_AUTOMAKE.
164 AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION],
165 [AM_AUTOMAKE_VERSION([1.7.9])])
166
167 # Helper functions for option handling. -*- Autoconf -*-
168
169 # Copyright 2001, 2002 Free Software Foundation, Inc.
170
171 # This program is free software; you can redistribute it and/or modify
172 # it under the terms of the GNU General Public License as published by
173 # the Free Software Foundation; either version 2, or (at your option)
174 # any later version.
175
176 # This program is distributed in the hope that it will be useful,
177 # but WITHOUT ANY WARRANTY; without even the implied warranty of
178 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
179 # GNU General Public License for more details.
180
181 # You should have received a copy of the GNU General Public License
182 # along with this program; if not, write to the Free Software
183 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
184 # 02111-1307, USA.
185
186 # serial 2
187
188 # _AM_MANGLE_OPTION(NAME)
189 # -----------------------
190 AC_DEFUN([_AM_MANGLE_OPTION],
191 [[_AM_OPTION_]m4_bpatsubst($1, [[^a-zA-Z0-9_]], [_])])
192
193 # _AM_SET_OPTION(NAME)
194 # ------------------------------
195 # Set option NAME. Presently that only means defining a flag for this option.
196 AC_DEFUN([_AM_SET_OPTION],
197 [m4_define(_AM_MANGLE_OPTION([$1]), 1)])
198
199 # _AM_SET_OPTIONS(OPTIONS)
200 # ----------------------------------
201 # OPTIONS is a space-separated list of Automake options.
202 AC_DEFUN([_AM_SET_OPTIONS],
203 [AC_FOREACH([_AM_Option], [$1], [_AM_SET_OPTION(_AM_Option)])])
204
205 # _AM_IF_OPTION(OPTION, IF-SET, [IF-NOT-SET])
206 # -------------------------------------------
207 # Execute IF-SET if OPTION is set, IF-NOT-SET otherwise.
208 AC_DEFUN([_AM_IF_OPTION],
209 [m4_ifset(_AM_MANGLE_OPTION([$1]), [$2], [$3])])
210
211 #
212 # Check to make sure that the build environment is sane.
213 #
214
215 # Copyright 1996, 1997, 2000, 2001 Free Software Foundation, Inc.
216
217 # This program is free software; you can redistribute it and/or modify
218 # it under the terms of the GNU General Public License as published by
219 # the Free Software Foundation; either version 2, or (at your option)
220 # any later version.
221
222 # This program is distributed in the hope that it will be useful,
223 # but WITHOUT ANY WARRANTY; without even the implied warranty of
224 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
225 # GNU General Public License for more details.
226
227 # You should have received a copy of the GNU General Public License
228 # along with this program; if not, write to the Free Software
229 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
230 # 02111-1307, USA.
231
232 # serial 3
233
234 # AM_SANITY_CHECK
235 # ---------------
236 AC_DEFUN([AM_SANITY_CHECK],
237 [AC_MSG_CHECKING([whether build environment is sane])
238 # Just in case
239 sleep 1
240 echo timestamp > conftest.file
241 # Do `set' in a subshell so we don't clobber the current shell's
242 # arguments. Must try -L first in case configure is actually a
243 # symlink; some systems play weird games with the mod time of symlinks
244 # (eg FreeBSD returns the mod time of the symlink's containing
245 # directory).
246 if (
247 set X `ls -Lt $srcdir/configure conftest.file 2> /dev/null`
248 if test "$[*]" = "X"; then
249 # -L didn't work.
250 set X `ls -t $srcdir/configure conftest.file`
251 fi
252 rm -f conftest.file
253 if test "$[*]" != "X $srcdir/configure conftest.file" \
254 && test "$[*]" != "X conftest.file $srcdir/configure"; then
255
256 # If neither matched, then we have a broken ls. This can happen
257 # if, for instance, CONFIG_SHELL is bash and it inherits a
258 # broken ls alias from the environment. This has actually
259 # happened. Such a system could not be considered "sane".
260 AC_MSG_ERROR([ls -t appears to fail. Make sure there is not a broken
261 alias in your environment])
262 fi
263
264 test "$[2]" = conftest.file
265 )
266 then
267 # Ok.
268 :
269 else
270 AC_MSG_ERROR([newly created file is older than distributed files!
271 Check your system clock])
272 fi
273 AC_MSG_RESULT(yes)])
274
275 # -*- Autoconf -*-
276
277
278 # Copyright 1997, 1999, 2000, 2001 Free Software Foundation, Inc.
279
280 # This program is free software; you can redistribute it and/or modify
281 # it under the terms of the GNU General Public License as published by
282 # the Free Software Foundation; either version 2, or (at your option)
283 # any later version.
284
285 # This program is distributed in the hope that it will be useful,
286 # but WITHOUT ANY WARRANTY; without even the implied warranty of
287 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
288 # GNU General Public License for more details.
289
290 # You should have received a copy of the GNU General Public License
291 # along with this program; if not, write to the Free Software
292 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
293 # 02111-1307, USA.
294
295 # serial 3
296
297 # AM_MISSING_PROG(NAME, PROGRAM)
298 # ------------------------------
299 AC_DEFUN([AM_MISSING_PROG],
300 [AC_REQUIRE([AM_MISSING_HAS_RUN])
301 $1=${$1-"${am_missing_run}$2"}
302 AC_SUBST($1)])
303
304
305 # AM_MISSING_HAS_RUN
306 # ------------------
307 # Define MISSING if not defined so far and test if it supports --run.
308 # If it does, set am_missing_run to use it, otherwise, to nothing.
309 AC_DEFUN([AM_MISSING_HAS_RUN],
310 [AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl
311 test x"${MISSING+set}" = xset || MISSING="\${SHELL} $am_aux_dir/missing"
312 # Use eval to expand $SHELL
313 if eval "$MISSING --run true"; then
314 am_missing_run="$MISSING --run "
315 else
316 am_missing_run=
317 AC_MSG_WARN([`missing' script is too old or missing])
318 fi
319 ])
320
321 # AM_AUX_DIR_EXPAND
322
323 # Copyright 2001 Free Software Foundation, Inc.
324
325 # This program is free software; you can redistribute it and/or modify
326 # it under the terms of the GNU General Public License as published by
327 # the Free Software Foundation; either version 2, or (at your option)
328 # any later version.
329
330 # This program is distributed in the hope that it will be useful,
331 # but WITHOUT ANY WARRANTY; without even the implied warranty of
332 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
333 # GNU General Public License for more details.
334
335 # You should have received a copy of the GNU General Public License
336 # along with this program; if not, write to the Free Software
337 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
338 # 02111-1307, USA.
339
340 # For projects using AC_CONFIG_AUX_DIR([foo]), Autoconf sets
341 # $ac_aux_dir to `$srcdir/foo'. In other projects, it is set to
342 # `$srcdir', `$srcdir/..', or `$srcdir/../..'.
343 #
344 # Of course, Automake must honor this variable whenever it calls a
345 # tool from the auxiliary directory. The problem is that $srcdir (and
346 # therefore $ac_aux_dir as well) can be either absolute or relative,
347 # depending on how configure is run. This is pretty annoying, since
348 # it makes $ac_aux_dir quite unusable in subdirectories: in the top
349 # source directory, any form will work fine, but in subdirectories a
350 # relative path needs to be adjusted first.
351 #
352 # $ac_aux_dir/missing
353 # fails when called from a subdirectory if $ac_aux_dir is relative
354 # $top_srcdir/$ac_aux_dir/missing
355 # fails if $ac_aux_dir is absolute,
356 # fails when called from a subdirectory in a VPATH build with
357 # a relative $ac_aux_dir
358 #
359 # The reason of the latter failure is that $top_srcdir and $ac_aux_dir
360 # are both prefixed by $srcdir. In an in-source build this is usually
361 # harmless because $srcdir is `.', but things will broke when you
362 # start a VPATH build or use an absolute $srcdir.
363 #
364 # So we could use something similar to $top_srcdir/$ac_aux_dir/missing,
365 # iff we strip the leading $srcdir from $ac_aux_dir. That would be:
366 # am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*\(.*\)"`
367 # and then we would define $MISSING as
368 # MISSING="\${SHELL} $am_aux_dir/missing"
369 # This will work as long as MISSING is not called from configure, because
370 # unfortunately $(top_srcdir) has no meaning in configure.
371 # However there are other variables, like CC, which are often used in
372 # configure, and could therefore not use this "fixed" $ac_aux_dir.
373 #
374 # Another solution, used here, is to always expand $ac_aux_dir to an
375 # absolute PATH. The drawback is that using absolute paths prevent a
376 # configured tree to be moved without reconfiguration.
377
378 # Rely on autoconf to set up CDPATH properly.
379 AC_PREREQ([2.50])
380
381 AC_DEFUN([AM_AUX_DIR_EXPAND], [
382 # expand $ac_aux_dir to an absolute path
383 am_aux_dir=`cd $ac_aux_dir && pwd`
384 ])
385
386 # AM_PROG_INSTALL_SH
387 # ------------------
388 # Define $install_sh.
389
390 # Copyright 2001 Free Software Foundation, Inc.
391
392 # This program is free software; you can redistribute it and/or modify
393 # it under the terms of the GNU General Public License as published by
394 # the Free Software Foundation; either version 2, or (at your option)
395 # any later version.
396
397 # This program is distributed in the hope that it will be useful,
398 # but WITHOUT ANY WARRANTY; without even the implied warranty of
399 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
400 # GNU General Public License for more details.
401
402 # You should have received a copy of the GNU General Public License
403 # along with this program; if not, write to the Free Software
404 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
405 # 02111-1307, USA.
406
407 AC_DEFUN([AM_PROG_INSTALL_SH],
408 [AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl
409 install_sh=${install_sh-"$am_aux_dir/install-sh"}
410 AC_SUBST(install_sh)])
411
412 # AM_PROG_INSTALL_STRIP
413
414 # Copyright 2001 Free Software Foundation, Inc.
415
416 # This program is free software; you can redistribute it and/or modify
417 # it under the terms of the GNU General Public License as published by
418 # the Free Software Foundation; either version 2, or (at your option)
419 # any later version.
420
421 # This program is distributed in the hope that it will be useful,
422 # but WITHOUT ANY WARRANTY; without even the implied warranty of
423 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
424 # GNU General Public License for more details.
425
426 # You should have received a copy of the GNU General Public License
427 # along with this program; if not, write to the Free Software
428 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
429 # 02111-1307, USA.
430
431 # One issue with vendor `install' (even GNU) is that you can't
432 # specify the program used to strip binaries. This is especially
433 # annoying in cross-compiling environments, where the build's strip
434 # is unlikely to handle the host's binaries.
435 # Fortunately install-sh will honor a STRIPPROG variable, so we
436 # always use install-sh in `make install-strip', and initialize
437 # STRIPPROG with the value of the STRIP variable (set by the user).
438 AC_DEFUN([AM_PROG_INSTALL_STRIP],
439 [AC_REQUIRE([AM_PROG_INSTALL_SH])dnl
440 # Installed binaries are usually stripped using `strip' when the user
441 # run `make install-strip'. However `strip' might not be the right
442 # tool to use in cross-compilation environments, therefore Automake
443 # will honor the `STRIP' environment variable to overrule this program.
444 dnl Don't test for $cross_compiling = yes, because it might be `maybe'.
445 if test "$cross_compiling" != no; then
446 AC_CHECK_TOOL([STRIP], [strip], :)
447 fi
448 INSTALL_STRIP_PROGRAM="\${SHELL} \$(install_sh) -c -s"
449 AC_SUBST([INSTALL_STRIP_PROGRAM])])
450
451 # -*- Autoconf -*-
452 # Copyright (C) 2003 Free Software Foundation, Inc.
453
454 # This program is free software; you can redistribute it and/or modify
455 # it under the terms of the GNU General Public License as published by
456 # the Free Software Foundation; either version 2, or (at your option)
457 # any later version.
458
459 # This program is distributed in the hope that it will be useful,
460 # but WITHOUT ANY WARRANTY; without even the implied warranty of
461 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
462 # GNU General Public License for more details.
463
464 # You should have received a copy of the GNU General Public License
465 # along with this program; if not, write to the Free Software
466 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
467 # 02111-1307, USA.
468
469 # serial 1
470
471 # Check whether the underlying file-system supports filenames
472 # with a leading dot. For instance MS-DOS doesn't.
473 AC_DEFUN([AM_SET_LEADING_DOT],
474 [rm -rf .tst 2>/dev/null
475 mkdir .tst 2>/dev/null
476 if test -d .tst; then
477 am__leading_dot=.
478 else
479 am__leading_dot=_
480 fi
481 rmdir .tst 2>/dev/null
482 AC_SUBST([am__leading_dot])])
483
484 # serial 5 -*- Autoconf -*-
485
486 # Copyright (C) 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
487
488 # This program is free software; you can redistribute it and/or modify
489 # it under the terms of the GNU General Public License as published by
490 # the Free Software Foundation; either version 2, or (at your option)
491 # any later version.
492
493 # This program is distributed in the hope that it will be useful,
494 # but WITHOUT ANY WARRANTY; without even the implied warranty of
495 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
496 # GNU General Public License for more details.
497
498 # You should have received a copy of the GNU General Public License
499 # along with this program; if not, write to the Free Software
500 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
501 # 02111-1307, USA.
502
503
504 # There are a few dirty hacks below to avoid letting `AC_PROG_CC' be
505 # written in clear, in which case automake, when reading aclocal.m4,
506 # will think it sees a *use*, and therefore will trigger all it's
507 # C support machinery. Also note that it means that autoscan, seeing
508 # CC etc. in the Makefile, will ask for an AC_PROG_CC use...
509
510
511
512 # _AM_DEPENDENCIES(NAME)
513 # ----------------------
514 # See how the compiler implements dependency checking.
515 # NAME is "CC", "CXX", "GCJ", or "OBJC".
516 # We try a few techniques and use that to set a single cache variable.
517 #
518 # We don't AC_REQUIRE the corresponding AC_PROG_CC since the latter was
519 # modified to invoke _AM_DEPENDENCIES(CC); we would have a circular
520 # dependency, and given that the user is not expected to run this macro,
521 # just rely on AC_PROG_CC.
522 AC_DEFUN([_AM_DEPENDENCIES],
523 [AC_REQUIRE([AM_SET_DEPDIR])dnl
524 AC_REQUIRE([AM_OUTPUT_DEPENDENCY_COMMANDS])dnl
525 AC_REQUIRE([AM_MAKE_INCLUDE])dnl
526 AC_REQUIRE([AM_DEP_TRACK])dnl
527
528 ifelse([$1], CC, [depcc="$CC" am_compiler_list=],
529 [$1], CXX, [depcc="$CXX" am_compiler_list=],
530 [$1], OBJC, [depcc="$OBJC" am_compiler_list='gcc3 gcc'],
531 [$1], GCJ, [depcc="$GCJ" am_compiler_list='gcc3 gcc'],
532 [depcc="$$1" am_compiler_list=])
533
534 AC_CACHE_CHECK([dependency style of $depcc],
535 [am_cv_$1_dependencies_compiler_type],
536 [if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then
537 # We make a subdir and do the tests there. Otherwise we can end up
538 # making bogus files that we don't know about and never remove. For
539 # instance it was reported that on HP-UX the gcc test will end up
540 # making a dummy file named `D' -- because `-MD' means `put the output
541 # in D'.
542 mkdir conftest.dir
543 # Copy depcomp to subdir because otherwise we won't find it if we're
544 # using a relative directory.
545 cp "$am_depcomp" conftest.dir
546 cd conftest.dir
547 # We will build objects and dependencies in a subdirectory because
548 # it helps to detect inapplicable dependency modes. For instance
549 # both Tru64's cc and ICC support -MD to output dependencies as a
550 # side effect of compilation, but ICC will put the dependencies in
551 # the current directory while Tru64 will put them in the object
552 # directory.
553 mkdir sub
554
555 am_cv_$1_dependencies_compiler_type=none
556 if test "$am_compiler_list" = ""; then
557 am_compiler_list=`sed -n ['s/^#*\([a-zA-Z0-9]*\))$/\1/p'] < ./depcomp`
558 fi
559 for depmode in $am_compiler_list; do
560 # Setup a source with many dependencies, because some compilers
561 # like to wrap large dependency lists on column 80 (with \), and
562 # we should not choose a depcomp mode which is confused by this.
563 #
564 # We need to recreate these files for each test, as the compiler may
565 # overwrite some of them when testing with obscure command lines.
566 # This happens at least with the AIX C compiler.
567 : > sub/conftest.c
568 for i in 1 2 3 4 5 6; do
569 echo '#include "conftst'$i'.h"' >> sub/conftest.c
570 : > sub/conftst$i.h
571 done
572 echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf
573
574 case $depmode in
575 nosideeffect)
576 # after this tag, mechanisms are not by side-effect, so they'll
577 # only be used when explicitly requested
578 if test "x$enable_dependency_tracking" = xyes; then
579 continue
580 else
581 break
582 fi
583 ;;
584 none) break ;;
585 esac
586 # We check with `-c' and `-o' for the sake of the "dashmstdout"
587 # mode. It turns out that the SunPro C++ compiler does not properly
588 # handle `-M -o', and we need to detect this.
589 if depmode=$depmode \
590 source=sub/conftest.c object=sub/conftest.${OBJEXT-o} \
591 depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \
592 $SHELL ./depcomp $depcc -c -o sub/conftest.${OBJEXT-o} sub/conftest.c \
593 >/dev/null 2>conftest.err &&
594 grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 &&
595 grep sub/conftest.${OBJEXT-o} sub/conftest.Po > /dev/null 2>&1 &&
596 ${MAKE-make} -s -f confmf > /dev/null 2>&1; then
597 # icc doesn't choke on unknown options, it will just issue warnings
598 # (even with -Werror). So we grep stderr for any message
599 # that says an option was ignored.
600 if grep 'ignoring option' conftest.err >/dev/null 2>&1; then :; else
601 am_cv_$1_dependencies_compiler_type=$depmode
602 break
603 fi
604 fi
605 done
606
607 cd ..
608 rm -rf conftest.dir
609 else
610 am_cv_$1_dependencies_compiler_type=none
611 fi
612 ])
613 AC_SUBST([$1DEPMODE], [depmode=$am_cv_$1_dependencies_compiler_type])
614 AM_CONDITIONAL([am__fastdep$1], [
615 test "x$enable_dependency_tracking" != xno \
616 && test "$am_cv_$1_dependencies_compiler_type" = gcc3])
617 ])
618
619
620 # AM_SET_DEPDIR
621 # -------------
622 # Choose a directory name for dependency files.
623 # This macro is AC_REQUIREd in _AM_DEPENDENCIES
624 AC_DEFUN([AM_SET_DEPDIR],
625 [AC_REQUIRE([AM_SET_LEADING_DOT])dnl
626 AC_SUBST([DEPDIR], ["${am__leading_dot}deps"])dnl
627 ])
628
629
630 # AM_DEP_TRACK
631 # ------------
632 AC_DEFUN([AM_DEP_TRACK],
633 [AC_ARG_ENABLE(dependency-tracking,
634 [ --disable-dependency-tracking Speeds up one-time builds
635 --enable-dependency-tracking Do not reject slow dependency extractors])
636 if test "x$enable_dependency_tracking" != xno; then
637 am_depcomp="$ac_aux_dir/depcomp"
638 AMDEPBACKSLASH='\'
639 fi
640 AM_CONDITIONAL([AMDEP], [test "x$enable_dependency_tracking" != xno])
641 AC_SUBST([AMDEPBACKSLASH])
642 ])
643
644 # Generate code to set up dependency tracking. -*- Autoconf -*-
645
646 # Copyright 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
647
648 # This program is free software; you can redistribute it and/or modify
649 # it under the terms of the GNU General Public License as published by
650 # the Free Software Foundation; either version 2, or (at your option)
651 # any later version.
652
653 # This program is distributed in the hope that it will be useful,
654 # but WITHOUT ANY WARRANTY; without even the implied warranty of
655 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
656 # GNU General Public License for more details.
657
658 # You should have received a copy of the GNU General Public License
659 # along with this program; if not, write to the Free Software
660 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
661 # 02111-1307, USA.
662
663 #serial 2
664
665 # _AM_OUTPUT_DEPENDENCY_COMMANDS
666 # ------------------------------
667 AC_DEFUN([_AM_OUTPUT_DEPENDENCY_COMMANDS],
668 [for mf in $CONFIG_FILES; do
669 # Strip MF so we end up with the name of the file.
670 mf=`echo "$mf" | sed -e 's/:.*$//'`
671 # Check whether this is an Automake generated Makefile or not.
672 # We used to match only the files named `Makefile.in', but
673 # some people rename them; so instead we look at the file content.
674 # Grep'ing the first line is not enough: some people post-process
675 # each Makefile.in and add a new line on top of each file to say so.
676 # So let's grep whole file.
677 if grep '^#.*generated by automake' $mf > /dev/null 2>&1; then
678 dirpart=`AS_DIRNAME("$mf")`
679 else
680 continue
681 fi
682 grep '^DEP_FILES *= *[[^ @%:@]]' < "$mf" > /dev/null || continue
683 # Extract the definition of DEP_FILES from the Makefile without
684 # running `make'.
685 DEPDIR=`sed -n -e '/^DEPDIR = / s///p' < "$mf"`
686 test -z "$DEPDIR" && continue
687 # When using ansi2knr, U may be empty or an underscore; expand it
688 U=`sed -n -e '/^U = / s///p' < "$mf"`
689 test -d "$dirpart/$DEPDIR" || mkdir "$dirpart/$DEPDIR"
690 # We invoke sed twice because it is the simplest approach to
691 # changing $(DEPDIR) to its actual value in the expansion.
692 for file in `sed -n -e '
693 /^DEP_FILES = .*\\\\$/ {
694 s/^DEP_FILES = //
695 :loop
696 s/\\\\$//
697 p
698 n
699 /\\\\$/ b loop
700 p
701 }
702 /^DEP_FILES = / s/^DEP_FILES = //p' < "$mf" | \
703 sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do
704 # Make sure the directory exists.
705 test -f "$dirpart/$file" && continue
706 fdir=`AS_DIRNAME(["$file"])`
707 AS_MKDIR_P([$dirpart/$fdir])
708 # echo "creating $dirpart/$file"
709 echo '# dummy' > "$dirpart/$file"
710 done
711 done
712 ])# _AM_OUTPUT_DEPENDENCY_COMMANDS
713
714
715 # AM_OUTPUT_DEPENDENCY_COMMANDS
716 # -----------------------------
717 # This macro should only be invoked once -- use via AC_REQUIRE.
718 #
719 # This code is only required when automatic dependency tracking
720