1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/gmyth/m4/AUTHORS Thu Sep 28 15:57:27 2006 +0100
1.3 @@ -0,0 +1,4 @@
1.4 +Alexsandro Jose Virginio dos Santos <alexsandro.santos@indt.org.br>
1.5 +Hallyson Luiz de Morais Melo <hallyson.melo@indt.org.br>
1.6 +Leonardo Sobral Cunha <leonardo.cunha@indt.org.br>
1.7 +Rosfran Lins Borges <rosfran.borges@indt.org.br>
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
2.2 +++ b/gmyth/m4/COPYING Thu Sep 28 15:57:27 2006 +0100
2.3 @@ -0,0 +1,504 @@
2.4 + GNU LESSER GENERAL PUBLIC LICENSE
2.5 + Version 2.1, February 1999
2.6 +
2.7 + Copyright (C) 1991, 1999 Free Software Foundation, Inc.
2.8 + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
2.9 + Everyone is permitted to copy and distribute verbatim copies
2.10 + of this license document, but changing it is not allowed.
2.11 +
2.12 +[This is the first released version of the Lesser GPL. It also counts
2.13 + as the successor of the GNU Library Public License, version 2, hence
2.14 + the version number 2.1.]
2.15 +
2.16 + Preamble
2.17 +
2.18 + The licenses for most software are designed to take away your
2.19 +freedom to share and change it. By contrast, the GNU General Public
2.20 +Licenses are intended to guarantee your freedom to share and change
2.21 +free software--to make sure the software is free for all its users.
2.22 +
2.23 + This license, the Lesser General Public License, applies to some
2.24 +specially designated software packages--typically libraries--of the
2.25 +Free Software Foundation and other authors who decide to use it. You
2.26 +can use it too, but we suggest you first think carefully about whether
2.27 +this license or the ordinary General Public License is the better
2.28 +strategy to use in any particular case, based on the explanations below.
2.29 +
2.30 + When we speak of free software, we are referring to freedom of use,
2.31 +not price. Our General Public Licenses are designed to make sure that
2.32 +you have the freedom to distribute copies of free software (and charge
2.33 +for this service if you wish); that you receive source code or can get
2.34 +it if you want it; that you can change the software and use pieces of
2.35 +it in new free programs; and that you are informed that you can do
2.36 +these things.
2.37 +
2.38 + To protect your rights, we need to make restrictions that forbid
2.39 +distributors to deny you these rights or to ask you to surrender these
2.40 +rights. These restrictions translate to certain responsibilities for
2.41 +you if you distribute copies of the library or if you modify it.
2.42 +
2.43 + For example, if you distribute copies of the library, whether gratis
2.44 +or for a fee, you must give the recipients all the rights that we gave
2.45 +you. You must make sure that they, too, receive or can get the source
2.46 +code. If you link other code with the library, you must provide
2.47 +complete object files to the recipients, so that they can relink them
2.48 +with the library after making changes to the library and recompiling
2.49 +it. And you must show them these terms so they know their rights.
2.50 +
2.51 + We protect your rights with a two-step method: (1) we copyright the
2.52 +library, and (2) we offer you this license, which gives you legal
2.53 +permission to copy, distribute and/or modify the library.
2.54 +
2.55 + To protect each distributor, we want to make it very clear that
2.56 +there is no warranty for the free library. Also, if the library is
2.57 +modified by someone else and passed on, the recipients should know
2.58 +that what they have is not the original version, so that the original
2.59 +author's reputation will not be affected by problems that might be
2.60 +introduced by others.
2.61 +
2.62 + Finally, software patents pose a constant threat to the existence of
2.63 +any free program. We wish to make sure that a company cannot
2.64 +effectively restrict the users of a free program by obtaining a
2.65 +restrictive license from a patent holder. Therefore, we insist that
2.66 +any patent license obtained for a version of the library must be
2.67 +consistent with the full freedom of use specified in this license.
2.68 +
2.69 + Most GNU software, including some libraries, is covered by the
2.70 +ordinary GNU General Public License. This license, the GNU Lesser
2.71 +General Public License, applies to certain designated libraries, and
2.72 +is quite different from the ordinary General Public License. We use
2.73 +this license for certain libraries in order to permit linking those
2.74 +libraries into non-free programs.
2.75 +
2.76 + When a program is linked with a library, whether statically or using
2.77 +a shared library, the combination of the two is legally speaking a
2.78 +combined work, a derivative of the original library. The ordinary
2.79 +General Public License therefore permits such linking only if the
2.80 +entire combination fits its criteria of freedom. The Lesser General
2.81 +Public License permits more lax criteria for linking other code with
2.82 +the library.
2.83 +
2.84 + We call this license the "Lesser" General Public License because it
2.85 +does Less to protect the user's freedom than the ordinary General
2.86 +Public License. It also provides other free software developers Less
2.87 +of an advantage over competing non-free programs. These disadvantages
2.88 +are the reason we use the ordinary General Public License for many
2.89 +libraries. However, the Lesser license provides advantages in certain
2.90 +special circumstances.
2.91 +
2.92 + For example, on rare occasions, there may be a special need to
2.93 +encourage the widest possible use of a certain library, so that it becomes
2.94 +a de-facto standard. To achieve this, non-free programs must be
2.95 +allowed to use the library. A more frequent case is that a free
2.96 +library does the same job as widely used non-free libraries. In this
2.97 +case, there is little to gain by limiting the free library to free
2.98 +software only, so we use the Lesser General Public License.
2.99 +
2.100 + In other cases, permission to use a particular library in non-free
2.101 +programs enables a greater number of people to use a large body of
2.102 +free software. For example, permission to use the GNU C Library in
2.103 +non-free programs enables many more people to use the whole GNU
2.104 +operating system, as well as its variant, the GNU/Linux operating
2.105 +system.
2.106 +
2.107 + Although the Lesser General Public License is Less protective of the
2.108 +users' freedom, it does ensure that the user of a program that is
2.109 +linked with the Library has the freedom and the wherewithal to run
2.110 +that program using a modified version of the Library.
2.111 +
2.112 + The precise terms and conditions for copying, distribution and
2.113 +modification follow. Pay close attention to the difference between a
2.114 +"work based on the library" and a "work that uses the library". The
2.115 +former contains code derived from the library, whereas the latter must
2.116 +be combined with the library in order to run.
2.117 +
2.118 + GNU LESSER GENERAL PUBLIC LICENSE
2.119 + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
2.120 +
2.121 + 0. This License Agreement applies to any software library or other
2.122 +program which contains a notice placed by the copyright holder or
2.123 +other authorized party saying it may be distributed under the terms of
2.124 +this Lesser General Public License (also called "this License").
2.125 +Each licensee is addressed as "you".
2.126 +
2.127 + A "library" means a collection of software functions and/or data
2.128 +prepared so as to be conveniently linked with application programs
2.129 +(which use some of those functions and data) to form executables.
2.130 +
2.131 + The "Library", below, refers to any such software library or work
2.132 +which has been distributed under these terms. A "work based on the
2.133 +Library" means either the Library or any derivative work under
2.134 +copyright law: that is to say, a work containing the Library or a
2.135 +portion of it, either verbatim or with modifications and/or translated
2.136 +straightforwardly into another language. (Hereinafter, translation is
2.137 +included without limitation in the term "modification".)
2.138 +
2.139 + "Source code" for a work means the preferred form of the work for
2.140 +making modifications to it. For a library, complete source code means
2.141 +all the source code for all modules it contains, plus any associated
2.142 +interface definition files, plus the scripts used to control compilation
2.143 +and installation of the library.
2.144 +
2.145 + Activities other than copying, distribution and modification are not
2.146 +covered by this License; they are outside its scope. The act of
2.147 +running a program using the Library is not restricted, and output from
2.148 +such a program is covered only if its contents constitute a work based
2.149 +on the Library (independent of the use of the Library in a tool for
2.150 +writing it). Whether that is true depends on what the Library does
2.151 +and what the program that uses the Library does.
2.152 +
2.153 + 1. You may copy and distribute verbatim copies of the Library's
2.154 +complete source code as you receive it, in any medium, provided that
2.155 +you conspicuously and appropriately publish on each copy an
2.156 +appropriate copyright notice and disclaimer of warranty; keep intact
2.157 +all the notices that refer to this License and to the absence of any
2.158 +warranty; and distribute a copy of this License along with the
2.159 +Library.
2.160 +
2.161 + You may charge a fee for the physical act of transferring a copy,
2.162 +and you may at your option offer warranty protection in exchange for a
2.163 +fee.
2.164 +
2.165 + 2. You may modify your copy or copies of the Library or any portion
2.166 +of it, thus forming a work based on the Library, and copy and
2.167 +distribute such modifications or work under the terms of Section 1
2.168 +above, provided that you also meet all of these conditions:
2.169 +
2.170 + a) The modified work must itself be a software library.
2.171 +
2.172 + b) You must cause the files modified to carry prominent notices
2.173 + stating that you changed the files and the date of any change.
2.174 +
2.175 + c) You must cause the whole of the work to be licensed at no
2.176 + charge to all third parties under the terms of this License.
2.177 +
2.178 + d) If a facility in the modified Library refers to a function or a
2.179 + table of data to be supplied by an application program that uses
2.180 + the facility, other than as an argument passed when the facility
2.181 + is invoked, then you must make a good faith effort to ensure that,
2.182 + in the event an application does not supply such function or
2.183 + table, the facility still operates, and performs whatever part of
2.184 + its purpose remains meaningful.
2.185 +
2.186 + (For example, a function in a library to compute square roots has
2.187 + a purpose that is entirely well-defined independent of the
2.188 + application. Therefore, Subsection 2d requires that any
2.189 + application-supplied function or table used by this function must
2.190 + be optional: if the application does not supply it, the square
2.191 + root function must still compute square roots.)
2.192 +
2.193 +These requirements apply to the modified work as a whole. If
2.194 +identifiable sections of that work are not derived from the Library,
2.195 +and can be reasonably considered independent and separate works in
2.196 +themselves, then this License, and its terms, do not apply to those
2.197 +sections when you distribute them as separate works. But when you
2.198 +distribute the same sections as part of a whole which is a work based
2.199 +on the Library, the distribution of the whole must be on the terms of
2.200 +this License, whose permissions for other licensees extend to the
2.201 +entire whole, and thus to each and every part regardless of who wrote
2.202 +it.
2.203 +
2.204 +Thus, it is not the intent of this section to claim rights or contest
2.205 +your rights to work written entirely by you; rather, the intent is to
2.206 +exercise the right to control the distribution of derivative or
2.207 +collective works based on the Library.
2.208 +
2.209 +In addition, mere aggregation of another work not based on the Library
2.210 +with the Library (or with a work based on the Library) on a volume of
2.211 +a storage or distribution medium does not bring the other work under
2.212 +the scope of this License.
2.213 +
2.214 + 3. You may opt to apply the terms of the ordinary GNU General Public
2.215 +License instead of this License to a given copy of the Library. To do
2.216 +this, you must alter all the notices that refer to this License, so
2.217 +that they refer to the ordinary GNU General Public License, version 2,
2.218 +instead of to this License. (If a newer version than version 2 of the
2.219 +ordinary GNU General Public License has appeared, then you can specify
2.220 +that version instead if you wish.) Do not make any other change in
2.221 +these notices.
2.222 +
2.223 + Once this change is made in a given copy, it is irreversible for
2.224 +that copy, so the ordinary GNU General Public License applies to all
2.225 +subsequent copies and derivative works made from that copy.
2.226 +
2.227 + This option is useful when you wish to copy part of the code of
2.228 +the Library into a program that is not a library.
2.229 +
2.230 + 4. You may copy and distribute the Library (or a portion or
2.231 +derivative of it, under Section 2) in object code or executable form
2.232 +under the terms of Sections 1 and 2 above provided that you accompany
2.233 +it with the complete corresponding machine-readable source code, which
2.234 +must be distributed under the terms of Sections 1 and 2 above on a
2.235 +medium customarily used for software interchange.
2.236 +
2.237 + If distribution of object code is made by offering access to copy
2.238 +from a designated place, then offering equivalent access to copy the
2.239 +source code from the same place satisfies the requirement to
2.240 +distribute the source code, even though third parties are not
2.241 +compelled to copy the source along with the object code.
2.242 +
2.243 + 5. A program that contains no derivative of any portion of the
2.244 +Library, but is designed to work with the Library by being compiled or
2.245 +linked with it, is called a "work that uses the Library". Such a
2.246 +work, in isolation, is not a derivative work of the Library, and
2.247 +therefore falls outside the scope of this License.
2.248 +
2.249 + However, linking a "work that uses the Library" with the Library
2.250 +creates an executable that is a derivative of the Library (because it
2.251 +contains portions of the Library), rather than a "work that uses the
2.252 +library". The executable is therefore covered by this License.
2.253 +Section 6 states terms for distribution of such executables.
2.254 +
2.255 + When a "work that uses the Library" uses material from a header file
2.256 +that is part of the Library, the object code for the work may be a
2.257 +derivative work of the Library even though the source code is not.
2.258 +Whether this is true is especially significant if the work can be
2.259 +linked without the Library, or if the work is itself a library. The
2.260 +threshold for this to be true is not precisely defined by law.
2.261 +
2.262 + If such an object file uses only numerical parameters, data
2.263 +structure layouts and accessors, and small macros and small inline
2.264 +functions (ten lines or less in length), then the use of the object
2.265 +file is unrestricted, regardless of whether it is legally a derivative
2.266 +work. (Executables containing this object code plus portions of the
2.267 +Library will still fall under Section 6.)
2.268 +
2.269 + Otherwise, if the work is a derivative of the Library, you may
2.270 +distribute the object code for the work under the terms of Section 6.
2.271 +Any executables containing that work also fall under Section 6,
2.272 +whether or not they are linked directly with the Library itself.
2.273 +
2.274 + 6. As an exception to the Sections above, you may also combine or
2.275 +link a "work that uses the Library" with the Library to produce a
2.276 +work containing portions of the Library, and distribute that work
2.277 +under terms of your choice, provided that the terms permit
2.278 +modification of the work for the customer's own use and reverse
2.279 +engineering for debugging such modifications.
2.280 +
2.281 + You must give prominent notice with each copy of the work that the
2.282 +Library is used in it and that the Library and its use are covered by
2.283 +this License. You must supply a copy of this License. If the work
2.284 +during execution displays copyright notices, you must include the
2.285 +copyright notice for the Library among them, as well as a reference
2.286 +directing the user to the copy of this License. Also, you must do one
2.287 +of these things:
2.288 +
2.289 + a) Accompany the work with the complete corresponding
2.290 + machine-readable source code for the Library including whatever
2.291 + changes were used in the work (which must be distributed under
2.292 + Sections 1 and 2 above); and, if the work is an executable linked
2.293 + with the Library, with the complete machine-readable "work that
2.294 + uses the Library", as object code and/or source code, so that the
2.295 + user can modify the Library and then relink to produce a modified
2.296 + executable containing the modified Library. (It is understood
2.297 + that the user who changes the contents of definitions files in the
2.298 + Library will not necessarily be able to recompile the application
2.299 + to use the modified definitions.)
2.300 +
2.301 + b) Use a suitable shared library mechanism for linking with the
2.302 + Library. A suitable mechanism is one that (1) uses at run time a
2.303 + copy of the library already present on the user's computer system,
2.304 + rather than copying library functions into the executable, and (2)
2.305 + will operate properly with a modified version of the library, if
2.306 + the user installs one, as long as the modified version is
2.307 + interface-compatible with the version that the work was made with.
2.308 +
2.309 + c) Accompany the work with a written offer, valid for at
2.310 + least three years, to give the same user the materials
2.311 + specified in Subsection 6a, above, for a charge no more
2.312 + than the cost of performing this distribution.
2.313 +
2.314 + d) If distribution of the work is made by offering access to copy
2.315 + from a designated place, offer equivalent access to copy the above
2.316 + specified materials from the same place.
2.317 +
2.318 + e) Verify that the user has already received a copy of these
2.319 + materials or that you have already sent this user a copy.
2.320 +
2.321 + For an executable, the required form of the "work that uses the
2.322 +Library" must include any data and utility programs needed for
2.323 +reproducing the executable from it. However, as a special exception,
2.324 +the materials to be distributed need not include anything that is
2.325 +normally distributed (in either source or binary form) with the major
2.326 +components (compiler, kernel, and so on) of the operating system on
2.327 +which the executable runs, unless that component itself accompanies
2.328 +the executable.
2.329 +
2.330 + It may happen that this requirement contradicts the license
2.331 +restrictions of other proprietary libraries that do not normally
2.332 +accompany the operating system. Such a contradiction means you cannot
2.333 +use both them and the Library together in an executable that you
2.334 +distribute.
2.335 +
2.336 + 7. You may place library facilities that are a work based on the
2.337 +Library side-by-side in a single library together with other library
2.338 +facilities not covered by this License, and distribute such a combined
2.339 +library, provided that the separate distribution of the work based on
2.340 +the Library and of the other library facilities is otherwise
2.341 +permitted, and provided that you do these two things:
2.342 +
2.343 + a) Accompany the combined library with a copy of the same work
2.344 + based on the Library, uncombined with any other library
2.345 + facilities. This must be distributed under the terms of the
2.346 + Sections above.
2.347 +
2.348 + b) Give prominent notice with the combined library of the fact
2.349 + that part of it is a work based on the Library, and explaining
2.350 + where to find the accompanying uncombined form of the same work.
2.351 +
2.352 + 8. You may not copy, modify, sublicense, link with, or distribute
2.353 +the Library except as expressly provided under this License. Any
2.354 +attempt otherwise to copy, modify, sublicense, link with, or
2.355 +distribute the Library is void, and will automatically terminate your
2.356 +rights under this License. However, parties who have received copies,
2.357 +or rights, from you under this License will not have their licenses
2.358 +terminated so long as such parties remain in full compliance.
2.359 +
2.360 + 9. You are not required to accept this License, since you have not
2.361 +signed it. However, nothing else grants you permission to modify or
2.362 +distribute the Library or its derivative works. These actions are
2.363 +prohibited by law if you do not accept this License. Therefore, by
2.364 +modifying or distributing the Library (or any work based on the
2.365 +Library), you indicate your acceptance of this License to do so, and
2.366 +all its terms and conditions for copying, distributing or modifying
2.367 +the Library or works based on it.
2.368 +
2.369 + 10. Each time you redistribute the Library (or any work based on the
2.370 +Library), the recipient automatically receives a license from the
2.371 +original licensor to copy, distribute, link with or modify the Library
2.372 +subject to these terms and conditions. You may not impose any further
2.373 +restrictions on the recipients' exercise of the rights granted herein.
2.374 +You are not responsible for enforcing compliance by third parties with
2.375 +this License.
2.376 +
2.377 + 11. If, as a consequence of a court judgment or allegation of patent
2.378 +infringement or for any other reason (not limited to patent issues),
2.379 +conditions are imposed on you (whether by court order, agreement or
2.380 +otherwise) that contradict the conditions of this License, they do not
2.381 +excuse you from the conditions of this License. If you cannot
2.382 +distribute so as to satisfy simultaneously your obligations under this
2.383 +License and any other pertinent obligations, then as a consequence you
2.384 +may not distribute the Library at all. For example, if a patent
2.385 +license would not permit royalty-free redistribution of the Library by
2.386 +all those who receive copies directly or indirectly through you, then
2.387 +the only way you could satisfy both it and this License would be to
2.388 +refrain entirely from distribution of the Library.
2.389 +
2.390 +If any portion of this section is held invalid or unenforceable under any
2.391 +particular circumstance, the balance of the section is intended to apply,
2.392 +and the section as a whole is intended to apply in other circumstances.
2.393 +
2.394 +It is not the purpose of this section to induce you to infringe any
2.395 +patents or other property right claims or to contest validity of any
2.396 +such claims; this section has the sole purpose of protecting the
2.397 +integrity of the free software distribution system which is
2.398 +implemented by public license practices. Many people have made
2.399 +generous contributions to the wide range of software distributed
2.400 +through that system in reliance on consistent application of that
2.401 +system; it is up to the author/donor to decide if he or she is willing
2.402 +to distribute software through any other system and a licensee cannot
2.403 +impose that choice.
2.404 +
2.405 +This section is intended to make thoroughly clear what is believed to
2.406 +be a consequence of the rest of this License.
2.407 +
2.408 + 12. If the distribution and/or use of the Library is restricted in
2.409 +certain countries either by patents or by copyrighted interfaces, the
2.410 +original copyright holder who places the Library under this License may add
2.411 +an explicit geographical distribution limitation excluding those countries,
2.412 +so that distribution is permitted only in or among countries not thus
2.413 +excluded. In such case, this License incorporates the limitation as if
2.414 +written in the body of this License.
2.415 +
2.416 + 13. The Free Software Foundation may publish revised and/or new
2.417 +versions of the Lesser General Public License from time to time.
2.418 +Such new versions will be similar in spirit to the present version,
2.419 +but may differ in detail to address new problems or concerns.
2.420 +
2.421 +Each version is given a distinguishing version number. If the Library
2.422 +specifies a version number of this License which applies to it and
2.423 +"any later version", you have the option of following the terms and
2.424 +conditions either of that version or of any later version published by
2.425 +the Free Software Foundation. If the Library does not specify a
2.426 +license version number, you may choose any version ever published by
2.427 +the Free Software Foundation.
2.428 +
2.429 + 14. If you wish to incorporate parts of the Library into other free
2.430 +programs whose distribution conditions are incompatible with these,
2.431 +write to the author to ask for permission. For software which is
2.432 +copyrighted by the Free Software Foundation, write to the Free
2.433 +Software Foundation; we sometimes make exceptions for this. Our
2.434 +decision will be guided by the two goals of preserving the free status
2.435 +of all derivatives of our free software and of promoting the sharing
2.436 +and reuse of software generally.
2.437 +
2.438 + NO WARRANTY
2.439 +
2.440 + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
2.441 +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
2.442 +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
2.443 +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
2.444 +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
2.445 +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
2.446 +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
2.447 +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
2.448 +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
2.449 +
2.450 + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
2.451 +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
2.452 +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
2.453 +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
2.454 +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
2.455 +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
2.456 +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
2.457 +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
2.458 +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
2.459 +DAMAGES.
2.460 +
2.461 + END OF TERMS AND CONDITIONS
2.462 +
2.463 + How to Apply These Terms to Your New Libraries
2.464 +
2.465 + If you develop a new library, and you want it to be of the greatest
2.466 +possible use to the public, we recommend making it free software that
2.467 +everyone can redistribute and change. You can do so by permitting
2.468 +redistribution under these terms (or, alternatively, under the terms of the
2.469 +ordinary General Public License).
2.470 +
2.471 + To apply these terms, attach the following notices to the library. It is
2.472 +safest to attach them to the start of each source file to most effectively
2.473 +convey the exclusion of warranty; and each file should have at least the
2.474 +"copyright" line and a pointer to where the full notice is found.
2.475 +
2.476 + <one line to give the library's name and a brief idea of what it does.>
2.477 + Copyright (C) <year> <name of author>
2.478 +
2.479 + This library is free software; you can redistribute it and/or
2.480 + modify it under the terms of the GNU Lesser General Public
2.481 + License as published by the Free Software Foundation; either
2.482 + version 2.1 of the License, or (at your option) any later version.
2.483 +
2.484 + This library is distributed in the hope that it will be useful,
2.485 + but WITHOUT ANY WARRANTY; without even the implied warranty of
2.486 + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
2.487 + Lesser General Public License for more details.
2.488 +
2.489 + You should have received a copy of the GNU Lesser General Public
2.490 + License along with this library; if not, write to the Free Software
2.491 + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
2.492 +
2.493 +Also add information on how to contact you by electronic and paper mail.
2.494 +
2.495 +You should also get your employer (if you work as a programmer) or your
2.496 +school, if any, to sign a "copyright disclaimer" for the library, if
2.497 +necessary. Here is a sample; alter the names:
2.498 +
2.499 + Yoyodyne, Inc., hereby disclaims all copyright interest in the
2.500 + library `Frob' (a library for tweaking knobs) written by James Random Hacker.
2.501 +
2.502 + <signature of Ty Coon>, 1 April 1990
2.503 + Ty Coon, President of Vice
2.504 +
2.505 +That's all there is to it!
2.506 +
2.507 +
3.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
3.2 +++ b/gmyth/m4/ChangeLog Thu Sep 28 15:57:27 2006 +0100
3.3 @@ -0,0 +1,24 @@
3.4 +2006-08-17 Rosfran Borges <rosfran.borges@indt.org.br>
3.5 + * Added the correct gstreamer-base package (GSTBASE) at the configure.ac;
3.6 + GSTBASE_CFLAGS and GSTBASE_LIBS variables had the same values from
3.7 + the GST_CFLAGS/GST_LIBS.
3.8 +
3.9 +2006-08-16 Rosfran Borges <rosfran.borges@indt.org.br>
3.10 + * Fixed some installation issues, regarding lib-installing to the
3.11 + correct directory, and copying the header files to the destination
3.12 + dir (make install).
3.13 + * Put 'pkg-config' resource to the Maemo Myth library. The name of the
3.14 + PKG-CONFIG resource is 'maemo-myth', plus the minor and major version.
3.15 + Actually, the version is '0.1', so the library config file is:
3.16 + 'maemo-myth-0.1.pc'. You can type: 'pkg-config --cflags --libs
3.17 + maemo-myth-0.1'.
3.18 + * Many adjustments in the automake/autoconf configuration files
3.19 + (configure.ac, Makefile.am) - some autotools misusage fixed.
3.20 + * Added the MythURI structure, and the URI parsing utility functions
3.21 + (missing in the GLib).
3.22 + * Some functions were exported (myth_socket, mmyth_context), that's
3.23 + why many ther modules need to use them.
3.24 + * Fixed some library dependencies.
3.25 + * Prepared to be used inside the GStreamer (linking with the MythTV
3.26 + plug-in).
3.27 +
4.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
4.2 +++ b/gmyth/m4/INSTALL Thu Sep 28 15:57:27 2006 +0100
4.3 @@ -0,0 +1,236 @@
4.4 +Installation Instructions
4.5 +*************************
4.6 +
4.7 +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
4.8 +Software Foundation, Inc.
4.9 +
4.10 +This file is free documentation; the Free Software Foundation gives
4.11 +unlimited permission to copy, distribute and modify it.
4.12 +
4.13 +Basic Installation
4.14 +==================
4.15 +
4.16 +These are generic installation instructions.
4.17 +
4.18 + The `configure' shell script attempts to guess correct values for
4.19 +various system-dependent variables used during compilation. It uses
4.20 +those values to create a `Makefile' in each directory of the package.
4.21 +It may also create one or more `.h' files containing system-dependent
4.22 +definitions. Finally, it creates a shell script `config.status' that
4.23 +you can run in the future to recreate the current configuration, and a
4.24 +file `config.log' containing compiler output (useful mainly for
4.25 +debugging `configure').
4.26 +
4.27 + It can also use an optional file (typically called `config.cache'
4.28 +and enabled with `--cache-file=config.cache' or simply `-C') that saves
4.29 +the results of its tests to speed up reconfiguring. (Caching is
4.30 +disabled by default to prevent problems with accidental use of stale
4.31 +cache files.)
4.32 +
4.33 + If you need to do unusual things to compile the package, please try
4.34 +to figure out how `configure' could check whether to do them, and mail
4.35 +diffs or instructions to the address given in the `README' so they can
4.36 +be considered for the next release. If you are using the cache, and at
4.37 +some point `config.cache' contains results you don't want to keep, you
4.38 +may remove or edit it.
4.39 +
4.40 + The file `configure.ac' (or `configure.in') is used to create
4.41 +`configure' by a program called `autoconf'. You only need
4.42 +`configure.ac' if you want to change it or regenerate `configure' using
4.43 +a newer version of `autoconf'.
4.44 +
4.45 +The simplest way to compile this package is:
4.46 +
4.47 + 1. `cd' to the directory containing the package's source code and type
4.48 + `./configure' to configure the package for your system. If you're
4.49 + using `csh' on an old version of System V, you might need to type
4.50 + `sh ./configure' instead to prevent `csh' from trying to execute
4.51 + `configure' itself.
4.52 +
4.53 + Running `configure' takes awhile. While running, it prints some
4.54 + messages telling which features it is checking for.
4.55 +
4.56 + 2. Type `make' to compile the package.
4.57 +
4.58 + 3. Optionally, type `make check' to run any self-tests that come with
4.59 + the package.
4.60 +
4.61 + 4. Type `make install' to install the programs and any data files and
4.62 + documentation.
4.63 +
4.64 + 5. You can remove the program binaries and object files from the
4.65 + source code directory by typing `make clean'. To also remove the
4.66 + files that `configure' created (so you can compile the package for
4.67 + a different kind of computer), type `make distclean'. There is
4.68 + also a `make maintainer-clean' target, but that is intended mainly
4.69 + for the package's developers. If you use it, you may have to get
4.70 + all sorts of other programs in order to regenerate files that came
4.71 + with the distribution.
4.72 +
4.73 +Compilers and Options
4.74 +=====================
4.75 +
4.76 +Some systems require unusual options for compilation or linking that the
4.77 +`configure' script does not know about. Run `./configure --help' for
4.78 +details on some of the pertinent environment variables.
4.79 +
4.80 + You can give `configure' initial values for configuration parameters
4.81 +by setting variables in the command line or in the environment. Here
4.82 +is an example:
4.83 +
4.84 + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
4.85 +
4.86 + *Note Defining Variables::, for more details.
4.87 +
4.88 +Compiling For Multiple Architectures
4.89 +====================================
4.90 +
4.91 +You can compile the package for more than one kind of computer at the
4.92 +same time, by placing the object files for each architecture in their
4.93 +own directory. To do this, you must use a version of `make' that
4.94 +supports the `VPATH' variable, such as GNU `make'. `cd' to the
4.95 +directory where you want the object files and executables to go and run
4.96 +the `configure' script. `configure' automatically checks for the
4.97 +source code in the directory that `configure' is in and in `..'.
4.98 +
4.99 + If you have to use a `make' that does not support the `VPATH'
4.100 +variable, you have to compile the package for one architecture at a
4.101 +time in the source code directory. After you have installed the
4.102 +package for one architecture, use `make distclean' before reconfiguring
4.103 +for another architecture.
4.104 +
4.105 +Installation Names
4.106 +==================
4.107 +
4.108 +By default, `make install' installs the package's commands under
4.109 +`/usr/local/bin', include files under `/usr/local/include', etc. You
4.110 +can specify an installation prefix other than `/usr/local' by giving
4.111 +`configure' the option `--prefix=PREFIX'.
4.112 +
4.113 + You can specify separate installation prefixes for
4.114 +architecture-specific files and architecture-independent files. If you
4.115 +pass the option `--exec-prefix=PREFIX' to `configure', the package uses
4.116 +PREFIX as the prefix for installing programs and libraries.
4.117 +Documentation and other data files still use the regular prefix.
4.118 +
4.119 + In addition, if you use an unusual directory layout you can give
4.120 +options like `--bindir=DIR' to specify different values for particular
4.121 +kinds of files. Run `configure --help' for a list of the directories
4.122 +you can set and what kinds of files go in them.
4.123 +
4.124 + If the package supports it, you can cause programs to be installed
4.125 +with an extra prefix or suffix on their names by giving `configure' the
4.126 +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
4.127 +
4.128 +Optional Features
4.129 +=================
4.130 +
4.131 +Some packages pay attention to `--enable-FEATURE' options to
4.132 +`configure', where FEATURE indicates an optional part of the package.
4.133 +They may also pay attention to `--with-PACKAGE' options, where PACKAGE
4.134 +is something like `gnu-as' or `x' (for the X Window System). The
4.135 +`README' should mention any `--enable-' and `--with-' options that the
4.136 +package recognizes.
4.137 +
4.138 + For packages that use the X Window System, `configure' can usually
4.139 +find the X include and library files automatically, but if it doesn't,
4.140 +you can use the `configure' options `--x-includes=DIR' and
4.141 +`--x-libraries=DIR' to specify their locations.
4.142 +
4.143 +Specifying the System Type
4.144 +==========================
4.145 +
4.146 +There may be some features `configure' cannot figure out automatically,
4.147 +but needs to determine by the type of machine the package will run on.
4.148 +Usually, assuming the package is built to be run on the _same_
4.149 +architectures, `configure' can figure that out, but if it prints a
4.150 +message saying it cannot guess the machine type, give it the
4.151 +`--build=TYPE' option. TYPE can either be a short name for the system
4.152 +type, such as `sun4', or a canonical name which has the form:
4.153 +
4.154 + CPU-COMPANY-SYSTEM
4.155 +
4.156 +where SYSTEM can have one of these forms:
4.157 +
4.158 + OS KERNEL-OS
4.159 +
4.160 + See the file `config.sub' for the possible values of each field. If
4.161 +`config.sub' isn't included in this package, then this package doesn't
4.162 +need to know the machine type.
4.163 +
4.164 + If you are _building_ compiler tools for cross-compiling, you should
4.165 +use the option `--target=TYPE' to select the type of system they will
4.166 +produce code for.
4.167 +
4.168 + If you want to _use_ a cross compiler, that generates code for a
4.169 +platform different from the build platform, you should specify the
4.170 +"host" platform (i.e., that on which the generated programs will
4.171 +eventually be run) with `--host=TYPE'.
4.172 +
4.173 +Sharing Defaults
4.174 +================
4.175 +
4.176 +If you want to set default values for `configure' scripts to share, you
4.177 +can create a site shell script called `config.site' that gives default
4.178 +values for variables like `CC', `cache_file', and `prefix'.
4.179 +`configure' looks for `PREFIX/share/config.site' if it exists, then
4.180 +`PREFIX/etc/config.site' if it exists. Or, you can set the
4.181 +`CONFIG_SITE' environment variable to the location of the site script.
4.182 +A warning: not all `configure' scripts look for a site script.
4.183 +
4.184 +Defining Variables
4.185 +==================
4.186 +
4.187 +Variables not defined in a site shell script can be set in the
4.188 +environment passed to `configure'. However, some packages may run
4.189 +configure again during the build, and the customized values of these
4.190 +variables may be lost. In order to avoid this problem, you should set
4.191 +them in the `configure' command line, using `VAR=value'. For example:
4.192 +
4.193 + ./configure CC=/usr/local2/bin/gcc
4.194 +
4.195 +causes the specified `gcc' to be used as the C compiler (unless it is
4.196 +overridden in the site shell script). Here is a another example:
4.197 +
4.198 + /bin/bash ./configure CONFIG_SHELL=/bin/bash
4.199 +
4.200 +Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
4.201 +configuration-related scripts to be executed by `/bin/bash'.
4.202 +
4.203 +`configure' Invocation
4.204 +======================
4.205 +
4.206 +`configure' recognizes the following options to control how it operates.
4.207 +
4.208 +`--help'
4.209 +`-h'
4.210 + Print a summary of the options to `configure', and exit.
4.211 +
4.212 +`--version'
4.213 +`-V'
4.214 + Print the version of Autoconf used to generate the `configure'
4.215 + script, and exit.
4.216 +
4.217 +`--cache-file=FILE'
4.218 + Enable the cache: use and save the results of the tests in FILE,
4.219 + traditionally `config.cache'. FILE defaults to `/dev/null' to
4.220 + disable caching.
4.221 +
4.222 +`--config-cache'
4.223 +`-C'
4.224 + Alias for `--cache-file=config.cache'.
4.225 +
4.226 +`--quiet'
4.227 +`--silent'
4.228 +`-q'
4.229 + Do not print messages saying which checks are being made. To
4.230 + suppress all normal output, redirect it to `/dev/null' (any error
4.231 + messages will still be shown).
4.232 +
4.233 +`--srcdir=DIR'
4.234 + Look for the package's source code in directory DIR. Usually
4.235 + `configure' can determine that directory automatically.
4.236 +
4.237 +`configure' also accepts some other, not widely useful, options. Run
4.238 +`configure --help' for more details.
4.239 +
5.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
5.2 +++ b/gmyth/m4/configure.ac Thu Sep 28 15:57:27 2006 +0100
5.3 @@ -0,0 +1,234 @@
5.4 +# -*- Autoconf -*-
5.5 +# Process this file with autoconf to produce a configure script.
5.6 +
5.7 +AC_PREREQ(2.50)
5.8 +
5.9 +AC_INIT([gmyth],[0.1])
5.10 +
5.11 +dnl AC_CONFIG_SRCDIR([src/mmyth_main.c])
5.12 +AC_CONFIG_HEADER(config.h)
5.13 +
5.14 +dnl when going to/from release please set the nano (fourth number) right !
5.15 +dnl releases only do Wall, SVN and prerelease does Werror too
5.16 +AS_VERSION(gmyth, GMYTH, 0, 1, 0, 3, GMYTH_SVN="no", GMYTH_SVN="yes")
5.17 +
5.18 +GMYTH_MAJORMINOR=$GMYTH_MAJOR_VERSION.$GMYTH_MINOR_VERSION
5.19 +
5.20 +AC_SUBST(GMYTH_MAJORMINOR)
5.21 +
5.22 +dnl AM_MAINTAINER_MODE provides the option to enable maintainer mode
5.23 +AM_MAINTAINER_MODE
5.24 +dnl make aclocal work in maintainer mode
5.25 +AC_SUBST(ACLOCAL_AMFLAGS, "-I m4")
5.26 +
5.27 +# Checks for programs.
5.28 +# check for tools
5.29 +# Make sure CFLAGS is defined to stop AC_PROC_CC adding -g
5.30 +CFLAGS="$CFLAGS -Wall"
5.31 +AC_PROG_CC
5.32 +AC_PROG_LIBTOOL
5.33 +
5.34 +dnl Generate doxygen documentation
5.35 +DX_HTML_FEATURE(ON)
5.36 +DX_CHM_FEATURE(OFF)
5.37 +DX_CHI_FEATURE(OFF)
5.38 +DX_MAN_FEATURE(OFF)
5.39 +DX_RTF_FEATURE(OFF)
5.40 +DX_XML_FEATURE(OFF)
5.41 +DX_PDF_FEATURE(OFF)
5.42 +DX_PS_FEATURE(OFF)
5.43 +DX_INIT_DOXYGEN(gmyth, doxygen.cfg, docs)
5.44 +
5.45 +
5.46 +# Checks for libraries.
5.47 +
5.48 +# Checks for header files.
5.49 +AC_HEADER_STDC
5.50 +AC_CHECK_HEADERS([fcntl.h stdint.h stdlib.h string.h sys/ioctl.h sys/socket.h unistd.h])
5.51 +
5.52 +# Checks for typedefs, structures, and compiler characteristics.
5.53 +AC_C_CONST
5.54 +AC_TYPE_PID_T
5.55 +AC_STRUCT_TM
5.56 +
5.57 +# Checks for library functions.
5.58 +AC_FUNC_FORK
5.59 +AC_PROG_GCC_TRADITIONAL
5.60 +AC_FUNC_MALLOC
5.61 +AC_FUNC_MKTIME
5.62 +AC_FUNC_VPRINTF
5.63 +AC_CHECK_FUNCS([memset socket stime strstr strtoul])
5.64 +
5.65 +AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
5.66 +
5.67 +# Checks required packages
5.68 +
5.69 +dnl Test if --disable-debug given
5.70 +AC_ARG_ENABLE(debug,
5.71 + [AC_HELP_STRING([--disable-debug], [disable debugging mode])],
5.72 + enable_debug="$enableval",
5.73 + enable_debug=yes)
5.74 +
5.75 +if test "x$enable_debug" = "xyes" ; then
5.76 + CFLAGS="$CFLAGS -g"
5.77 +else
5.78 + AC_DEFINE( NDEBUG, 1, [disable debug messages] )
5.79 + CFLAGS="$CFLAGS -O2 -DG_DISABLE_CHECKS -DNDEBUG"
5.80 +fi
5.81 +
5.82 +AM_CONDITIONAL( NDEBUG, test "x$enable_debug" = "xyes" )
5.83 +
5.84 +# Check for pkgconfig
5.85 +AC_CHECK_PROG(HAVE_PKGCONFIG, pkg-config, yes, no)
5.86 +# Give error and exit if we don't have pkgconfig
5.87 +if test "x$HAVE_PKGCONFIG" = "xno"; then
5.88 + AC_MSG_ERROR(you need to have pkgconfig installed !)
5.89 +fi
5.90 +
5.91 +# Check for Glib2.0
5.92 +PKG_CHECK_MODULES(GLIB, glib-2.0, HAVE_GLIB=yes,HAVE_GLIB=no)
5.93 +
5.94 +# Give error and exit if we don't have glib
5.95 +if test "x$HAVE_GLIB" = "xno"; then
5.96 + AC_MSG_ERROR(you need glib-2.0 installed)
5.97 +fi
5.98 +
5.99 +# make GLIB_CFLAGS and GLIB_LIBS available
5.100 +AC_SUBST(GLIB_CFLAGS)
5.101 +AC_SUBST(GLIB_LIBS)
5.102 +
5.103 +# Check for GObject2.0
5.104 +PKG_CHECK_MODULES(GOBJECT,
5.105 + gobject-2.0,
5.106 + HAVE_GOBJECT=yes, HAVE_GOBJECT=no)
5.107 +
5.108 +# Give error and exit if we don't have gobject
5.109 +if test "x$HAVE_GOBJECT" = "xno"; then
5.110 + AC_MSG_ERROR(you need gobject-2.0 installed)
5.111 +fi
5.112 +
5.113 +# make GOBJECT_CFLAGS and GOBJECT_LIBS available
5.114 +AC_SUBST(GOBJECT_CFLAGS)
5.115 +AC_SUBST(GOBJECT_LIBS)
5.116 +
5.117 +# Check for GTK+-2.0
5.118 +PKG_CHECK_MODULES(GTK, gtk+-2.0, HAVE_GTK=yes,HAVE_GTK=no)
5.119 +
5.120 +# Give error and exit if we don't have gtk
5.121 +if test "x$HAVE_GTK" = "xyes"; then
5.122 + AC_DEFINE(WITH_GTK, 1, [build with GTK+ related stuff])
5.123 + dnl AC_MSG_ERROR(you need gtk+-2.0 installed)
5.124 +else
5.125 + AC_MSG_RESULT(no)
5.126 +fi
5.127 +
5.128 +AM_CONDITIONAL(WITH_GTK, test "x$HAVE_GTK" = "xyes" )
5.129 +
5.130 +# make GTK_CFLAGS and GTK_LIBS available
5.131 +AC_SUBST(GTK_CFLAGS)
5.132 +AC_SUBST(GTK_LIBS)
5.133 +
5.134 +dnl ========== Check for Hildon Libraries
5.135 +PKG_CHECK_MODULES(HILDON,
5.136 + hildon-lgpl libosso hildon-status-bar-lib libhildonmenu hildon-base-lib hildon-control-panel hildon-libs,
5.137 + HAVE_HILDON=yes, HAVE_HILDON=no)
5.138 +
5.139 +if test "x$HAVE_HILDON" = "xyes"; then
5.140 + AC_DEFINE(MAEMO_PLATFORM, 1, [build with hildon libs])
5.141 + HILDON_CFLAGS="$HILDON_CFLAGS -DMAEMO_PLATFORM=1"
5.142 +else
5.143 + AC_MSG_RESULT(no)
5.144 +fi
5.145 +
5.146 +AM_CONDITIONAL(MAEMO_PLATFORM, test "x$HAVE_HILDON" = "xyes")
5.147 +
5.148 +dnl make HILDON_CFLAGS and HILDON_LIBS available
5.149 +AC_SUBST(HILDON_CFLAGS)
5.150 +AC_SUBST(HILDON_LIBS)
5.151 +
5.152 +# Check for libxml-2.0
5.153 +PKG_CHECK_MODULES(LIBXML, libxml-2.0, HAVE_LIBXML=yes,HAVE_LIBXML=no)
5.154 +
5.155 +# Give error and exit if we don't have libxml
5.156 +if test "x$HAVE_LIBXML" = "xno"; then
5.157 + AC_MSG_ERROR(you need libxml-2.0 installed)
5.158 +fi
5.159 +
5.160 +# make LIBXML_CFLAGS and LIBXML_LIBS available
5.161 +AC_SUBST(LIBXML_CFLAGS)
5.162 +AC_SUBST(LIBXML_LIBS)
5.163 +
5.164 +
5.165 +# check for gstreamer development files
5.166 +GST_REQUIRED=0.10
5.167 +GST_MAJORMINOR=0.10
5.168 +PKG_CHECK_MODULES(GST, \
5.169 + gstreamer-$GST_MAJORMINOR >= $GST_REQUIRED,
5.170 + HAVE_GST=yes, HAVE_GST=no)
5.171 +
5.172 +# Give error and exit if we don't have gstreamer
5.173 +if test "x$HAVE_GST" = "xno"; then
5.174 + AC_MSG_ERROR(you need gstreamer development packages installed !)
5.175 +fi
5.176 +
5.177 +# make GST_CFLAGS and GST_LIBS available
5.178 +AC_SUBST(GST_CFLAGS)
5.179 +AC_SUBST(GST_LIBS)
5.180 +
5.181 +# check for gstreamer-base plugins (xoverlay interface)
5.182 +GSTBASE_REQUIRED=0.10
5.183 +GSTBASE_MAJORMINOR=0.10
5.184 +PKG_CHECK_MODULES(GSTBASE, \
5.185 + gstreamer-base-$GSTBASE_MAJORMINOR >= $GSTBASE_REQUIRED,
5.186 + HAVE_GSTBASE=yes, HAVE_GSTBASE=no)
5.187 +
5.188 +# Give error and exit if we don't have gstreamer base libraries
5.189 +if test "x$HAVE_GSTBASE" = "xno"; then
5.190 + AC_MSG_ERROR(you need gstreamer base development packages installed !)
5.191 +fi
5.192 +
5.193 +# make GSTBASE_CFLAGS and GSTBASE_LIBS available
5.194 +AC_SUBST(GSTBASE_CFLAGS)
5.195 +AC_SUBST(GSTBASE_LIBS)
5.196 +
5.197 +
5.198 +# make GST_MAJORMINOR available in Makefile.am
5.199 +AC_SUBST(GST_MAJORMINOR)
5.200 +
5.201 +#
5.202 +# mysql libraries
5.203 +#
5.204 +AC_CHECK_PROG(MYSQL_CFLAGS,mysql_config,`mysql_config --cflags`)
5.205 +if test -z "$MYSQL_CFLAGS"; then
5.206 + AC_MSG_ERROR([Could not find mysql_config script. Make sure the mysql client libraries are installed])
5.207 +fi
5.208 +AC_SUBST(MYSQL_CFLAGS)
5.209 +
5.210 +
5.211 +AC_CHECK_PROG(MYSQL_LIBS,mysql_config,`mysql_config --libs`)
5.212 +if test -z "$MYSQL_LIBS"; then
5.213 + AC_MSG_ERROR([Could not find mysql_config script. Make sure the mysql client libraries are installed])
5.214 +fi
5.215 +AC_SUBST(MYSQL_LIBS)
5.216 +
5.217 +## Check for gmyth-0.1
5.218 +
5.219 +PKG_CHECK_MODULES(LIBGMYTH, gmyth-0.1, HAVE_LIBGMYTH=yes,HAVE_LIBGMYTH=no)
5.220 +
5.221 +# Give error and exit if we don't have gmyth-0.1
5.222 +if test "x$HAVE_LIBGMYTH" = "xno"; then
5.223 + AC_MSG_ERROR(you need gmyth-0.1 installed)
5.224 +fi
5.225 +
5.226 +# make LIBXML_CFLAGS and LIBXML_LIBS available
5.227 +AC_SUBST(LIBGMYTH_CFLAGS)
5.228 +AC_SUBST(LIBGMYTH_LIBS)
5.229 +
5.230 +#dnl Enable gtk-doc
5.231 +#GTK_DOC_CHECK(1.4)
5.232 +
5.233 +
5.234 +AC_CONFIG_FILES([Makefile
5.235 + src/Makefile
5.236 + pixmaps/Makefile])
5.237 +AC_OUTPUT