[xiph-commits] r8262 - in experimental/dholth/shoutpy: . gentoo
gentoo/dev-python gentoo/dev-python/shoutpy
dholth at motherfish-iii.xiph.org
dholth at motherfish-iii.xiph.org
Mon Nov 22 18:43:10 PST 2004
Author: dholth
Date: 2004-11-22 18:43:09 -0800 (Mon, 22 Nov 2004)
New Revision: 8262
Added:
experimental/dholth/shoutpy/CHANGELOG
experimental/dholth/shoutpy/COPYING
experimental/dholth/shoutpy/Doxyfile
experimental/dholth/shoutpy/Jamfile
experimental/dholth/shoutpy/Jamrules
experimental/dholth/shoutpy/LICENSE
experimental/dholth/shoutpy/MANIFEST.in
experimental/dholth/shoutpy/PKG-INFO
experimental/dholth/shoutpy/README
experimental/dholth/shoutpy/boost-build.jam
experimental/dholth/shoutpy/config.py
experimental/dholth/shoutpy/example.cc
experimental/dholth/shoutpy/example.py
experimental/dholth/shoutpy/gentoo/
experimental/dholth/shoutpy/gentoo/dev-python/
experimental/dholth/shoutpy/gentoo/dev-python/shoutpy/
experimental/dholth/shoutpy/gentoo/dev-python/shoutpy/shoutpy-0.5.2.ebuild
experimental/dholth/shoutpy/setup.py
experimental/dholth/shoutpy/shoutcc.cc
experimental/dholth/shoutpy/shoutcc.h
experimental/dholth/shoutpy/shoutpy.cc
Log:
libshout bindings for python
Added: experimental/dholth/shoutpy/CHANGELOG
===================================================================
--- experimental/dholth/shoutpy/CHANGELOG 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/CHANGELOG 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,3 @@
+0.5 : added doxygen documentation for C++ code, and docstrings for Python.
+0.4 : included example.py; Shout.send works.
+0.3 : initial release
Added: experimental/dholth/shoutpy/COPYING
===================================================================
--- experimental/dholth/shoutpy/COPYING 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/COPYING 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,510 @@
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations
+below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it
+becomes a de-facto standard. To achieve this, non-free programs must
+be allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control
+compilation and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ c) Accompany the work with a written offer, valid for at least
+ three years, to give the same user the materials specified in
+ Subsection 6a, above, for a charge no more than the cost of
+ performing this distribution.
+
+ d) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ e) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply, and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License
+may add an explicit geographical distribution limitation excluding those
+countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms
+of the ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library.
+It is safest to attach them to the start of each source file to most
+effectively convey the exclusion of warranty; and each file should
+have at least the "copyright" line and a pointer to where the full
+notice is found.
+
+
+ <one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or
+your school, if any, to sign a "copyright disclaimer" for the library,
+if necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James
+ Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
+
+
Added: experimental/dholth/shoutpy/Doxyfile
===================================================================
--- experimental/dholth/shoutpy/Doxyfile 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/Doxyfile 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,1101 @@
+# Doxyfile 1.3.2
+
+# This file describes the settings to be used by the documentation system
+# doxygen (www.doxygen.org) for a project
+#
+# All text after a hash (#) is considered a comment and will be ignored
+# The format is:
+# TAG = value [value, ...]
+# For lists items can also be appended using:
+# TAG += value [value, ...]
+# Values that contain spaces should be placed between quotes (" ")
+
+#---------------------------------------------------------------------------
+# General configuration options
+#---------------------------------------------------------------------------
+
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
+# by quotes) that should identify the project.
+
+PROJECT_NAME = shoutpy
+
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.
+# This could be handy for archiving the generated documentation or
+# if some version control system is used.
+
+PROJECT_NUMBER =
+
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
+# base path where the generated documentation will be put.
+# If a relative path is entered, it will be relative to the location
+# where doxygen was started. If left blank the current directory will be used.
+
+OUTPUT_DIRECTORY =
+
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all
+# documentation generated by doxygen is written. Doxygen will use this
+# information to generate all constant output in the proper language.
+# The default language is English, other supported languages are:
+# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
+# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
+# (Japanese with English messages), Korean, Norwegian, Polish, Portuguese,
+# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
+
+OUTPUT_LANGUAGE = English
+
+# This tag can be used to specify the encoding used in the generated output.
+# The encoding is not always determined by the language that is chosen,
+# but also whether or not the output is meant for Windows or non-Windows users.
+# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
+# forces the Windows encoding (this is the default for the Windows binary),
+# whereas setting the tag to NO uses a Unix-style encoding (the default for
+# all platforms other than Windows).
+
+USE_WINDOWS_ENCODING = NO
+
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
+# documentation are documented, even if no documentation was available.
+# Private class members and static file members will be hidden unless
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
+
+EXTRACT_ALL = NO
+
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
+# will be included in the documentation.
+
+EXTRACT_PRIVATE = NO
+
+# If the EXTRACT_STATIC tag is set to YES all static members of a file
+# will be included in the documentation.
+
+EXTRACT_STATIC = NO
+
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
+# defined locally in source files will be included in the documentation.
+# If set to NO only classes defined in header files are included.
+
+EXTRACT_LOCAL_CLASSES = YES
+
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
+# undocumented members of documented classes, files or namespaces.
+# If set to NO (the default) these members will be included in the
+# various overviews, but no documentation section is generated.
+# This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_MEMBERS = NO
+
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
+# undocumented classes that are normally visible in the class hierarchy.
+# If set to NO (the default) these classes will be included in the various
+# overviews. This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_CLASSES = NO
+
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
+# friend (class|struct|union) declarations.
+# If set to NO (the default) these declarations will be included in the
+# documentation.
+
+HIDE_FRIEND_COMPOUNDS = NO
+
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
+# documentation blocks found inside the body of a function.
+# If set to NO (the default) these blocks will be appended to the
+# function's detailed documentation block.
+
+HIDE_IN_BODY_DOCS = NO
+
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
+# include brief member descriptions after the members that are listed in
+# the file and class documentation (similar to JavaDoc).
+# Set to NO to disable this.
+
+BRIEF_MEMBER_DESC = YES
+
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
+# the brief description of a member or function before the detailed description.
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
+# brief descriptions will be completely suppressed.
+
+REPEAT_BRIEF = YES
+
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
+# Doxygen will generate a detailed section even if there is only a brief
+# description.
+
+ALWAYS_DETAILED_SEC = NO
+
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
+# members of a class in the documentation of that class as if those members were
+# ordinary class members. Constructors, destructors and assignment operators of
+# the base classes will not be shown.
+
+INLINE_INHERITED_MEMB = NO
+
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
+# path before files name in the file list and in the header files. If set
+# to NO the shortest path that makes the file name unique will be used.
+
+FULL_PATH_NAMES = NO
+
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
+# can be used to strip a user-defined part of the path. Stripping is
+# only done if one of the specified strings matches the left-hand part of
+# the path. It is allowed to use relative paths in the argument list.
+
+STRIP_FROM_PATH =
+
+# The INTERNAL_DOCS tag determines if documentation
+# that is typed after a \internal command is included. If the tag is set
+# to NO (the default) then the documentation will be excluded.
+# Set it to YES to include the internal documentation.
+
+INTERNAL_DOCS = NO
+
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
+# file names in lower-case letters. If set to YES upper-case letters are also
+# allowed. This is useful if you have classes or files whose names only differ
+# in case and if your file system supports case sensitive file names. Windows
+# users are advised to set this option to NO.
+
+CASE_SENSE_NAMES = YES
+
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
+# (but less readable) file names. This can be useful is your file systems
+# doesn't support long names like on DOS, Mac, or CD-ROM.
+
+SHORT_NAMES = NO
+
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
+# will show members with their full class and namespace scopes in the
+# documentation. If set to YES the scope will be hidden.
+
+HIDE_SCOPE_NAMES = NO
+
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
+# will put a list of the files that are included by a file in the documentation
+# of that file.
+
+SHOW_INCLUDE_FILES = YES
+
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
+# will interpret the first line (until the first dot) of a JavaDoc-style
+# comment as the brief description. If set to NO, the JavaDoc
+# comments will behave just like the Qt-style comments (thus requiring an
+# explict @brief command for a brief description.
+
+JAVADOC_AUTOBRIEF = NO
+
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///
+# comments) as a brief description. This used to be the default behaviour.
+# The new default is to treat a multi-line C++ comment block as a detailed
+# description. Set this tag to YES if you prefer the old behaviour instead.
+
+MULTILINE_CPP_IS_BRIEF = NO
+
+# If the DETAILS_AT_TOP tag is set to YES then Doxygen
+# will output the detailed description near the top, like JavaDoc.
+# If set to NO, the detailed description appears after the member
+# documentation.
+
+DETAILS_AT_TOP = NO
+
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
+# member inherits the documentation from any documented member that it
+# reimplements.
+
+INHERIT_DOCS = YES
+
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
+# is inserted in the documentation for inline members.
+
+INLINE_INFO = YES
+
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
+# will sort the (detailed) documentation of file and class members
+# alphabetically by member name. If set to NO the members will appear in
+# declaration order.
+
+SORT_MEMBER_DOCS = YES
+
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
+# tag is set to YES, then doxygen will reuse the documentation of the first
+# member in the group (if any) for the other members of the group. By default
+# all members of a group must be documented explicitly.
+
+DISTRIBUTE_GROUP_DOC = NO
+
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.
+# Doxygen uses this value to replace tabs by spaces in code fragments.
+
+TAB_SIZE = 8
+
+# The GENERATE_TODOLIST tag can be used to enable (YES) or
+# disable (NO) the todo list. This list is created by putting \todo
+# commands in the documentation.
+
+GENERATE_TODOLIST = YES
+
+# The GENERATE_TESTLIST tag can be used to enable (YES) or
+# disable (NO) the test list. This list is created by putting \test
+# commands in the documentation.
+
+GENERATE_TESTLIST = YES
+
+# The GENERATE_BUGLIST tag can be used to enable (YES) or
+# disable (NO) the bug list. This list is created by putting \bug
+# commands in the documentation.
+
+GENERATE_BUGLIST = YES
+
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
+# disable (NO) the deprecated list. This list is created by putting
+# \deprecated commands in the documentation.
+
+GENERATE_DEPRECATEDLIST= YES
+
+# This tag can be used to specify a number of aliases that acts
+# as commands in the documentation. An alias has the form "name=value".
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to
+# put the command \sideeffect (or @sideeffect) in the documentation, which
+# will result in a user-defined paragraph with heading "Side Effects:".
+# You can put \n's in the value part of an alias to insert newlines.
+
+ALIASES =
+
+# The ENABLED_SECTIONS tag can be used to enable conditional
+# documentation sections, marked by \if sectionname ... \endif.
+
+ENABLED_SECTIONS =
+
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
+# the initial value of a variable or define consists of for it to appear in
+# the documentation. If the initializer consists of more lines than specified
+# here it will be hidden. Use a value of 0 to hide initializers completely.
+# The appearance of the initializer of individual variables and defines in the
+# documentation can be controlled using \showinitializer or \hideinitializer
+# command in the documentation regardless of this setting.
+
+MAX_INITIALIZER_LINES = 30
+
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
+# only. Doxygen will then generate output that is more tailored for C.
+# For instance, some of the names that are used will be different. The list
+# of all members will be omitted, etc.
+
+OPTIMIZE_OUTPUT_FOR_C = NO
+
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
+# only. Doxygen will then generate output that is more tailored for Java.
+# For instance, namespaces will be presented as packages, qualified scopes
+# will look different, etc.
+
+OPTIMIZE_OUTPUT_JAVA = NO
+
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
+# at the bottom of the documentation of classes and structs. If set to YES the
+# list will mention the files that were used to generate the documentation.
+
+SHOW_USED_FILES = YES
+
+#---------------------------------------------------------------------------
+# configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+
+# The QUIET tag can be used to turn on/off the messages that are generated
+# by doxygen. Possible values are YES and NO. If left blank NO is used.
+
+QUIET = NO
+
+# The WARNINGS tag can be used to turn on/off the warning messages that are
+# generated by doxygen. Possible values are YES and NO. If left blank
+# NO is used.
+
+WARNINGS = YES
+
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
+# automatically be disabled.
+
+WARN_IF_UNDOCUMENTED = YES
+
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
+# potential errors in the documentation, such as not documenting some
+# parameters in a documented function, or documenting parameters that
+# don't exist or using markup commands wrongly.
+
+WARN_IF_DOC_ERROR = YES
+
+# The WARN_FORMAT tag determines the format of the warning messages that
+# doxygen can produce. The string should contain the $file, $line, and $text
+# tags, which will be replaced by the file and line number from which the
+# warning originated and the warning text.
+
+WARN_FORMAT = "$file:$line: $text"
+
+# The WARN_LOGFILE tag can be used to specify a file to which warning
+# and error messages should be written. If left blank the output is written
+# to stderr.
+
+WARN_LOGFILE =
+
+#---------------------------------------------------------------------------
+# configuration options related to the input files
+#---------------------------------------------------------------------------
+
+# The INPUT tag can be used to specify the files and/or directories that contain
+# documented source files. You may enter file names like "myfile.cpp" or
+# directories like "/usr/src/myproject". Separate the files or directories
+# with spaces.
+
+INPUT = shoutcc.cc shoutcc.h
+
+# If the value of the INPUT tag contains directories, you can use the
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
+# and *.h) to filter out the source-files in the directories. If left
+# blank the following patterns are tested:
+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
+# *.h++ *.idl *.odl *.cs
+
+FILE_PATTERNS =
+
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories
+# should be searched for input files as well. Possible values are YES and NO.
+# If left blank NO is used.
+
+RECURSIVE = NO
+
+# The EXCLUDE tag can be used to specify files and/or directories that should
+# excluded from the INPUT source files. This way you can easily exclude a
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
+
+EXCLUDE =
+
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
+# that are symbolic links (a Unix filesystem feature) are excluded from the input.
+
+EXCLUDE_SYMLINKS = NO
+
+# If the value of the INPUT tag contains directories, you can use the
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
+# certain files from those directories.
+
+EXCLUDE_PATTERNS =
+
+# The EXAMPLE_PATH tag can be used to specify one or more files or
+# directories that contain example code fragments that are included (see
+# the \include command).
+
+EXAMPLE_PATH =
+
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
+# and *.h) to filter out the source-files in the directories. If left
+# blank all files are included.
+
+EXAMPLE_PATTERNS =
+
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
+# searched for input files to be used with the \include or \dontinclude
+# commands irrespective of the value of the RECURSIVE tag.
+# Possible values are YES and NO. If left blank NO is used.
+
+EXAMPLE_RECURSIVE = NO
+
+# The IMAGE_PATH tag can be used to specify one or more files or
+# directories that contain image that are included in the documentation (see
+# the \image command).
+
+IMAGE_PATH =
+
+# The INPUT_FILTER tag can be used to specify a program that doxygen should
+# invoke to filter for each input file. Doxygen will invoke the filter program
+# by executing (via popen()) the command <filter> <input-file>, where <filter>
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
+# input file. Doxygen will then use the output that the filter program writes
+# to standard output.
+
+INPUT_FILTER =
+
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
+# INPUT_FILTER) will be used to filter the input files when producing source
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).
+
+FILTER_SOURCE_FILES = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to source browsing
+#---------------------------------------------------------------------------
+
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will
+# be generated. Documented entities will be cross-referenced with these sources.
+
+SOURCE_BROWSER = NO
+
+# Setting the INLINE_SOURCES tag to YES will include the body
+# of functions and classes directly in the documentation.
+
+INLINE_SOURCES = NO
+
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
+# doxygen to hide any special comment blocks from generated source code
+# fragments. Normal C and C++ comments will always remain visible.
+
+STRIP_CODE_COMMENTS = YES
+
+# If the REFERENCED_BY_RELATION tag is set to YES (the default)
+# then for each documented function all documented
+# functions referencing it will be listed.
+
+REFERENCED_BY_RELATION = YES
+
+# If the REFERENCES_RELATION tag is set to YES (the default)
+# then for each documented function all documented entities
+# called/used by that function will be listed.
+
+REFERENCES_RELATION = YES
+
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
+# will generate a verbatim copy of the header file for each class for
+# which an include is specified. Set to NO to disable this.
+
+VERBATIM_HEADERS = YES
+
+#---------------------------------------------------------------------------
+# configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
+# of all compounds will be generated. Enable this if the project
+# contains a lot of classes, structs, unions or interfaces.
+
+ALPHABETICAL_INDEX = NO
+
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
+# in which this list will be split (can be a number in the range [1..20])
+
+COLS_IN_ALPHA_INDEX = 5
+
+# In case all classes in a project start with a common prefix, all
+# classes will be put under the same header in the alphabetical index.
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
+# should be ignored while generating the index headers.
+
+IGNORE_PREFIX =
+
+#---------------------------------------------------------------------------
+# configuration options related to the HTML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
+# generate HTML output.
+
+GENERATE_HTML = YES
+
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `html' will be used as the default path.
+
+HTML_OUTPUT = web/html
+
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
+# doxygen will generate files with .html extension.
+
+HTML_FILE_EXTENSION = .html
+
+# The HTML_HEADER tag can be used to specify a personal HTML header for
+# each generated HTML page. If it is left blank doxygen will generate a
+# standard header.
+
+HTML_HEADER =
+
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for
+# each generated HTML page. If it is left blank doxygen will generate a
+# standard footer.
+
+HTML_FOOTER =
+
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
+# style sheet that is used by each HTML page. It can be used to
+# fine-tune the look of the HTML output. If the tag is left blank doxygen
+# will generate a default style sheet
+
+HTML_STYLESHEET =
+
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
+# files or namespaces will be aligned in HTML using tables. If set to
+# NO a bullet list will be used.
+
+HTML_ALIGN_MEMBERS = YES
+
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files
+# will be generated that can be used as input for tools like the
+# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
+# of the generated HTML documentation.
+
+GENERATE_HTMLHELP = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
+# be used to specify the file name of the resulting .chm file. You
+# can add a path in front of the file if the result should not be
+# written to the html output dir.
+
+CHM_FILE =
+
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
+# be used to specify the location (absolute path including file name) of
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
+# the HTML help compiler on the generated index.hhp.
+
+HHC_LOCATION =
+
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
+# controls if a separate .chi index file is generated (YES) or that
+# it should be included in the master .chm file (NO).
+
+GENERATE_CHI = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
+# controls whether a binary table of contents is generated (YES) or a
+# normal table of contents (NO) in the .chm file.
+
+BINARY_TOC = NO
+
+# The TOC_EXPAND flag can be set to YES to add extra items for group members
+# to the contents of the HTML help documentation and to the tree view.
+
+TOC_EXPAND = NO
+
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
+# top of each HTML page. The value NO (the default) enables the index and
+# the value YES disables it.
+
+DISABLE_INDEX = NO
+
+# This tag can be used to set the number of enum values (range [1..20])
+# that doxygen will group on one line in the generated HTML documentation.
+
+ENUM_VALUES_PER_LINE = 4
+
+# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
+# generated containing a tree-like index structure (just like the one that
+# is generated for HTML Help). For this to work a browser that supports
+# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
+# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
+# probably better off using the HTML help feature.
+
+GENERATE_TREEVIEW = NO
+
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
+# used to set the initial width (in pixels) of the frame in which the tree
+# is shown.
+
+TREEVIEW_WIDTH = 250
+
+#---------------------------------------------------------------------------
+# configuration options related to the LaTeX output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
+# generate Latex output.
+
+GENERATE_LATEX = YES
+
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `latex' will be used as the default path.
+
+LATEX_OUTPUT = latex
+
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
+# invoked. If left blank `latex' will be used as the default command name.
+
+LATEX_CMD_NAME = latex
+
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
+# generate index for LaTeX. If left blank `makeindex' will be used as the
+# default command name.
+
+MAKEINDEX_CMD_NAME = makeindex
+
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
+# LaTeX documents. This may be useful for small projects and may help to
+# save some trees in general.
+
+COMPACT_LATEX = NO
+
+# The PAPER_TYPE tag can be used to set the paper type that is used
+# by the printer. Possible values are: a4, a4wide, letter, legal and
+# executive. If left blank a4wide will be used.
+
+PAPER_TYPE = a4wide
+
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
+# packages that should be included in the LaTeX output.
+
+EXTRA_PACKAGES =
+
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
+# the generated latex document. The header should contain everything until
+# the first chapter. If it is left blank doxygen will generate a
+# standard header. Notice: only use this tag if you know what you are doing!
+
+LATEX_HEADER =
+
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will
+# contain links (just like the HTML output) instead of page references
+# This makes the output suitable for online browsing using a pdf viewer.
+
+PDF_HYPERLINKS = NO
+
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
+# plain latex in the generated Makefile. Set this option to YES to get a
+# higher quality PDF documentation.
+
+USE_PDFLATEX = NO
+
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
+# command to the generated LaTeX files. This will instruct LaTeX to keep
+# running if errors occur, instead of asking the user for help.
+# This option is also used when generating formulas in HTML.
+
+LATEX_BATCHMODE = NO
+
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not
+# include the index chapters (such as File Index, Compound Index, etc.)
+# in the output.
+
+LATEX_HIDE_INDICES = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the RTF output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
+# The RTF output is optimised for Word 97 and may not look very pretty with
+# other RTF readers or editors.
+
+GENERATE_RTF = NO
+
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `rtf' will be used as the default path.
+
+RTF_OUTPUT = rtf
+
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
+# RTF documents. This may be useful for small projects and may help to
+# save some trees in general.
+
+COMPACT_RTF = NO
+
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
+# will contain hyperlink fields. The RTF file will
+# contain links (just like the HTML output) instead of page references.
+# This makes the output suitable for online browsing using WORD or other
+# programs which support those fields.
+# Note: wordpad (write) and others do not support links.
+
+RTF_HYPERLINKS = NO
+
+# Load stylesheet definitions from file. Syntax is similar to doxygen's
+# config file, i.e. a series of assigments. You only have to provide
+# replacements, missing definitions are set to their default value.
+
+RTF_STYLESHEET_FILE =
+
+# Set optional variables used in the generation of an rtf document.
+# Syntax is similar to doxygen's config file.
+
+RTF_EXTENSIONS_FILE =
+
+#---------------------------------------------------------------------------
+# configuration options related to the man page output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
+# generate man pages
+
+GENERATE_MAN = NO
+
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `man' will be used as the default path.
+
+MAN_OUTPUT = man
+
+# The MAN_EXTENSION tag determines the extension that is added to
+# the generated man pages (default is the subroutine's section .3)
+
+MAN_EXTENSION = .3
+
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
+# then it will generate one additional man file for each entity
+# documented in the real man page(s). These additional files
+# only source the real man page, but without them the man command
+# would be unable to find the correct page. The default is NO.
+
+MAN_LINKS = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the XML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_XML tag is set to YES Doxygen will
+# generate an XML file that captures the structure of
+# the code including all documentation. Note that this
+# feature is still experimental and incomplete at the
+# moment.
+
+GENERATE_XML = YES
+
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `xml' will be used as the default path.
+
+XML_OUTPUT = xml
+
+# The XML_SCHEMA tag can be used to specify an XML schema,
+# which can be used by a validating XML parser to check the
+# syntax of the XML files.
+
+XML_SCHEMA =
+
+# The XML_DTD tag can be used to specify an XML DTD,
+# which can be used by a validating XML parser to check the
+# syntax of the XML files.
+
+XML_DTD =
+
+#---------------------------------------------------------------------------
+# configuration options for the AutoGen Definitions output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
+# generate an AutoGen Definitions (see autogen.sf.net) file
+# that captures the structure of the code including all
+# documentation. Note that this feature is still experimental
+# and incomplete at the moment.
+
+GENERATE_AUTOGEN_DEF = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the Perl module output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will
+# generate a Perl module file that captures the structure of
+# the code including all documentation. Note that this
+# feature is still experimental and incomplete at the
+# moment.
+
+GENERATE_PERLMOD = NO
+
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able
+# to generate PDF and DVI output from the Perl module output.
+
+PERLMOD_LATEX = NO
+
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
+# nicely formatted so it can be parsed by a human reader. This is useful
+# if you want to understand what is going on. On the other hand, if this
+# tag is set to NO the size of the Perl module output will be much smaller
+# and Perl will parse it just the same.
+
+PERLMOD_PRETTY = YES
+
+# The names of the make variables in the generated doxyrules.make file
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
+# This is useful so different doxyrules.make files included by the same
+# Makefile don't overwrite each other's variables.
+
+PERLMOD_MAKEVAR_PREFIX =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the preprocessor
+#---------------------------------------------------------------------------
+
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
+# evaluate all C-preprocessor directives found in the sources and include
+# files.
+
+ENABLE_PREPROCESSING = YES
+
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
+# names in the source code. If set to NO (the default) only conditional
+# compilation will be performed. Macro expansion can be done in a controlled
+# way by setting EXPAND_ONLY_PREDEF to YES.
+
+MACRO_EXPANSION = NO
+
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
+# then the macro expansion is limited to the macros specified with the
+# PREDEFINED and EXPAND_AS_PREDEFINED tags.
+
+EXPAND_ONLY_PREDEF = NO
+
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
+# in the INCLUDE_PATH (see below) will be search if a #include is found.
+
+SEARCH_INCLUDES = YES
+
+# The INCLUDE_PATH tag can be used to specify one or more directories that
+# contain include files that are not input files but should be processed by
+# the preprocessor.
+
+INCLUDE_PATH =
+
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
+# patterns (like *.h and *.hpp) to filter out the header-files in the
+# directories. If left blank, the patterns specified with FILE_PATTERNS will
+# be used.
+
+INCLUDE_FILE_PATTERNS =
+
+# The PREDEFINED tag can be used to specify one or more macro names that
+# are defined before the preprocessor is started (similar to the -D option of
+# gcc). The argument of the tag is a list of macros of the form: name
+# or name=definition (no spaces). If the definition and the = are
+# omitted =1 is assumed.
+
+PREDEFINED =
+
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
+# this tag can be used to specify a list of macro names that should be expanded.
+# The macro definition that is found in the sources will be used.
+# Use the PREDEFINED tag if you want to use a different macro definition.
+
+EXPAND_AS_DEFINED =
+
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
+# doxygen's preprocessor will remove all function-like macros that are alone
+# on a line, have an all uppercase name, and do not end with a semicolon. Such
+# function macros are typically used for boiler-plate code, and will confuse the
+# parser if not removed.
+
+SKIP_FUNCTION_MACROS = YES
+
+#---------------------------------------------------------------------------
+# Configuration::addtions related to external references
+#---------------------------------------------------------------------------
+
+# The TAGFILES option can be used to specify one or more tagfiles.
+# Optionally an initial location of the external documentation
+# can be added for each tagfile. The format of a tag file without
+# this location is as follows:
+# TAGFILES = file1 file2 ...
+# Adding location for the tag files is done as follows:
+# TAGFILES = file1=loc1 "file2 = loc2" ...
+# where "loc1" and "loc2" can be relative or absolute paths or
+# URLs. If a location is present for each tag, the installdox tool
+# does not have to be run to correct the links.
+# Note that each tag file must have a unique name
+# (where the name does NOT include the path)
+# If a tag file is not located in the directory in which doxygen
+# is run, you must also specify the path to the tagfile here.
+
+TAGFILES =
+
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create
+# a tag file that is based on the input files it reads.
+
+GENERATE_TAGFILE =
+
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed
+# in the class index. If set to NO only the inherited external classes
+# will be listed.
+
+ALLEXTERNALS = NO
+
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
+# in the modules index. If set to NO, only the current project's groups will
+# be listed.
+
+EXTERNAL_GROUPS = YES
+
+# The PERL_PATH should be the absolute path and name of the perl script
+# interpreter (i.e. the result of `which perl').
+
+PERL_PATH = /usr/bin/perl
+
+#---------------------------------------------------------------------------
+# Configuration options related to the dot tool
+#---------------------------------------------------------------------------
+
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
+# super classes. Setting the tag to NO turns the diagrams off. Note that this
+# option is superceded by the HAVE_DOT option below. This is only a fallback. It is
+# recommended to install and use dot, since it yields more powerful graphs.
+
+CLASS_DIAGRAMS = YES
+
+# If set to YES, the inheritance and collaboration graphs will hide
+# inheritance and usage relations if the target is undocumented
+# or is not a class.
+
+HIDE_UNDOC_RELATIONS = YES
+
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
+# available from the path. This tool is part of Graphviz, a graph visualization
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section
+# have no effect if this option is set to NO (the default)
+
+HAVE_DOT = NO
+
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for each documented class showing the direct and
+# indirect inheritance relations. Setting this tag to YES will force the
+# the CLASS_DIAGRAMS tag to NO.
+
+CLASS_GRAPH = YES
+
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for each documented class showing the direct and
+# indirect implementation dependencies (inheritance, containment, and
+# class references variables) of the class with other documented classes.
+
+COLLABORATION_GRAPH = YES
+
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
+# colloborations diagrams in a style similiar to the OMG's Unified Modeling
+# Language.
+
+UML_LOOK = NO
+
+# If set to YES, the inheritance and collaboration graphs will show the
+# relations between templates and their instances.
+
+TEMPLATE_RELATIONS = NO
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
+# tags are set to YES then doxygen will generate a graph for each documented
+# file showing the direct and indirect include dependencies of the file with
+# other documented files.
+
+INCLUDE_GRAPH = YES
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
+# documented header file showing the documented files that directly or
+# indirectly include this file.
+
+INCLUDED_BY_GRAPH = YES
+
+# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
+# generate a call dependency graph for every global function or class method.
+# Note that enabling this option will significantly increase the time of a run.
+# So in most cases it will be better to enable call graphs for selected
+# functions only using the \callgraph command.
+
+CALL_GRAPH = NO
+
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
+# will graphical hierarchy of all classes instead of a textual one.
+
+GRAPHICAL_HIERARCHY = YES
+
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
+# generated by dot. Possible values are png, jpg, or gif
+# If left blank png will be used.
+
+DOT_IMAGE_FORMAT = png
+
+# The tag DOT_PATH can be used to specify the path where the dot tool can be
+# found. If left blank, it is assumed the dot tool can be found on the path.
+
+DOT_PATH =
+
+# The DOTFILE_DIRS tag can be used to specify one or more directories that
+# contain dot files that are included in the documentation (see the
+# \dotfile command).
+
+DOTFILE_DIRS =
+
+# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than
+# this value, doxygen will try to truncate the graph, so that it fits within
+# the specified constraint. Beware that most browsers cannot cope with very
+# large images.
+
+MAX_DOT_GRAPH_WIDTH = 1024
+
+# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than
+# this value, doxygen will try to truncate the graph, so that it fits within
+# the specified constraint. Beware that most browsers cannot cope with very
+# large images.
+
+MAX_DOT_GRAPH_HEIGHT = 1024
+
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
+# graphs generated by dot. A depth value of 3 means that only nodes reachable
+# from the root by following a path via at most 3 edges will be shown. Nodes that
+# lay further from the root node will be omitted. Note that setting this option to
+# 1 or 2 may greatly reduce the computation time needed for large code bases. Also
+# note that a graph may be further truncated if the graph's image dimensions are
+# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
+# If 0 is used for the depth value (the default), the graph is not depth-constrained.
+
+MAX_DOT_GRAPH_DEPTH = 0
+
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
+# generate a legend page explaining the meaning of the various boxes and
+# arrows in the dot generated graphs.
+
+GENERATE_LEGEND = YES
+
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
+# remove the intermediate dot files that are used to generate
+# the various graphs.
+
+DOT_CLEANUP = YES
+
+#---------------------------------------------------------------------------
+# Configuration::addtions related to the search engine
+#---------------------------------------------------------------------------
+
+# The SEARCHENGINE tag specifies whether or not a search engine should be
+# used. If set to NO the values of all tags below this one will be ignored.
+
+SEARCHENGINE = NO
+
+# The CGI_NAME tag should be the name of the CGI script that
+# starts the search engine (doxysearch) with the correct parameters.
+# A script with this name will be generated by doxygen.
+
+CGI_NAME = search.cgi
+
+# The CGI_URL tag should be the absolute URL to the directory where the
+# cgi binaries are located. See the documentation of your http daemon for
+# details.
+
+CGI_URL =
+
+# The DOC_URL tag should be the absolute URL to the directory where the
+# documentation is located. If left blank the absolute path to the
+# documentation, with file:// prepended to it, will be used.
+
+DOC_URL =
+
+# The DOC_ABSPATH tag should be the absolute path to the directory where the
+# documentation is located. If left blank the directory on the local machine
+# will be used.
+
+DOC_ABSPATH =
+
+# The BIN_ABSPATH tag must point to the directory where the doxysearch binary
+# is installed.
+
+BIN_ABSPATH = /usr/local/bin/
+
+# The EXT_DOC_PATHS tag can be used to specify one or more paths to
+# documentation generated for other projects. This allows doxysearch to search
+# the documentation for these projects as well.
+
+EXT_DOC_PATHS =
Added: experimental/dholth/shoutpy/Jamfile
===================================================================
--- experimental/dholth/shoutpy/Jamfile 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/Jamfile 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,30 @@
+# Daniel Holth <dholth at fastmail.fm>, 2004
+# based on David Abraham's example from Boost.Python
+
+# This file is not important unless you want to use boost-jam;
+# bjam -sBUILD=release builds a smaller binary than setup.py
+
+# This is the top of our own project tree
+project-root ;
+
+import python ;
+
+# The Python extension
+extension shoutpy
+: # sources
+ shoutpy.cc
+ shoutcc.cc
+: # requirements
+ <find-library>shout
+ <find-library>boost_python
+ ;
+
+# The C++ example
+exe cplus_streaming_example
+: # sources
+ example.cc
+ shoutcc.cc
+: # requirements
+ <find-library>shout
+ ;
+
Added: experimental/dholth/shoutpy/Jamrules
===================================================================
--- experimental/dholth/shoutpy/Jamrules 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/Jamrules 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,30 @@
+# Copyright David Abrahams 2003. See accompanying LICENSE for terms
+# and conditions of use.
+
+# If you move this example from its place in the Boost tree, edit this
+# path to point at the root directory of your Boost installation (the
+# one containing a subdirectory called "boost/" and a sub-subdirectory
+# "boost/python/" that contains .hpp files. Absolute paths work, too.
+
+path-global BOOST_ROOT : $(HOME)/src/boost ;
+
+# Boost.Python configuration variables, as described in
+# http://www.boost.org/libs/python/doc/building.html. Usually you
+# don't need to set these; the defaults will work. If you do set
+# them, try to change as few of them as possible, starting with the
+# first ones.
+
+ # PYTHON_VERSION = <the two-part Major.Minor version number, e.g. 2.2> ;
+ # PYTHON_ROOT = <path to root directory of your Python installation> ;
+ # PYTHON_INCLUDES = <path to Python #include directories> ;
+ # PYTHON_LIB_PATH = <path to Python library object> ;
+
+# You may need to configure your compiler toolset, especially if you
+# want to build with a compiler that is not the "system default" or if
+# it is installed in a nonstandard place; see
+# http://www.boost.org/more/getting_started.html#Configuring for
+# details.
+
+# Makes a project id for boost so that other Boost.Build projects can
+# refer to it by name.
+project boost : $(BOOST_ROOT) ;
Property changes on: experimental/dholth/shoutpy/Jamrules
___________________________________________________________________
Name: svn:executable
+ *
Added: experimental/dholth/shoutpy/LICENSE
===================================================================
--- experimental/dholth/shoutpy/LICENSE 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/LICENSE 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,25 @@
+This document applies to Jamrules, Jamfile and boost-build.jam
+
+Boost Software License - Version 1.0 - August 17th, 2003
+
+Permission is hereby granted, free of charge, to any person or organization
+obtaining a copy of the software and accompanying documentation covered by
+this license (the "Software") to use, reproduce, display, distribute,
+execute, and transmit the Software, and to prepare derivative works of the
+Software, and to permit third-parties to whom the Software is furnished to
+do so, all subject to the following:
+
+The copyright notices in the Software and this entire statement, including
+the above license grant, this restriction and the following disclaimer,
+must be included in all copies of the Software, in whole or in part, and
+all derivative works of the Software, unless such copies or derivative
+works are solely in the form of machine-executable object code generated by
+a source language processor.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
+SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
+FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.
Added: experimental/dholth/shoutpy/MANIFEST.in
===================================================================
--- experimental/dholth/shoutpy/MANIFEST.in 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/MANIFEST.in 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,4 @@
+include Doxyfile MANIFEST.in CHANGELOG COPYING
+include *.h example.py example.cc config.py
+include Jamfile Jamrules boost-build.jam LICENSE
+recursive-include gentoo *.ebuild
Added: experimental/dholth/shoutpy/PKG-INFO
===================================================================
--- experimental/dholth/shoutpy/PKG-INFO 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/PKG-INFO 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,18 @@
+Metadata-Version: 1.0
+Name: shoutpy
+Version: 0.5.2
+Summary: Boost.Python bindings for libshout 2
+Home-page: http://dingoskidneys.com/shoutpy/
+Author: Daniel Holth
+Author-email: dholth at fastmail.fm
+License: GNU LGPL
+Download-URL: http://dingoskidneys.com/shoutpy/shoutpy-0.5.2.tar.gz
+Description: shoutpy provides Pythonic bindings for libshout 2.
+Platform: linux
+Classifier: Development Status :: 3 - Alpha
+Classifier: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL)
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: C++
+Classifier: Programming Language :: Python
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Multimedia :: Sound/Audio
Added: experimental/dholth/shoutpy/README
===================================================================
--- experimental/dholth/shoutpy/README 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/README 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,31 @@
+shoutpy
+-------
+http://dingoskidneys.com/shoutpy/
+
+A Python (Boost.Python) and C++ wrapper for libshout 2.
+
+Installing
+----------
+You must have Boost.Python >= version 1.31.
+
+Edit config.py if boost.python or libshout is installed outside your
+compiler's normal search path or you are not using gcc and boost.python
+1.31.
+
+To compile and install:
+ python setup.py install
+
+In gentoo, you may install the notable dependencies thus:
+ ACCEPT_KEYWORDS=~x86 emerge libshout && emerge boost
+
+A gentoo ebuild is provided.
+
+A boost-jam setup (edit Jamrules and boost-build.jam to point to your
+boost installation) is also provided; you will need to install the boost
+sources and the latest boost-jam before you can use this. Then type
+
+ bjam
+
+and look for the module and C++ source client under ./bin/
+
+(c) 2004 Daniel Holth <dholth at fastmail.fm>
Added: experimental/dholth/shoutpy/boost-build.jam
===================================================================
--- experimental/dholth/shoutpy/boost-build.jam 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/boost-build.jam 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,6 @@
+# Copyright David Abrahams 2003. See accompanying LICENSE for terms
+# and conditions of use.
+
+# Edit this path to point at the tools/build/v1 subdirectory of your
+# Boost installation. Absolute paths work, too.
+boost-build /usr/share/boost/v1 ;
Property changes on: experimental/dholth/shoutpy/boost-build.jam
___________________________________________________________________
Name: svn:executable
+ *
Added: experimental/dholth/shoutpy/config.py
===================================================================
--- experimental/dholth/shoutpy/config.py 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/config.py 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,11 @@
+# Local configuration for shoutpy
+# Daniel Holth <dholth at fastmail.fm>, 2004
+# This one is for gentoo.
+
+libraries = ["shout"]
+libraries.extend(("boost_python",))
+# libraries.extend(("boost_python-gcc-mt-1_31",)) # this name may also work for you
+
+library_dirs = []
+
+include_dirs = []
Added: experimental/dholth/shoutpy/example.cc
===================================================================
--- experimental/dholth/shoutpy/example.cc 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/example.cc 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,69 @@
+/* Simple multi-file streaming to a server.
+ *
+ * Daniel Holth <dholth at fastmail.fm>, 2004
+ */
+
+#include "shoutcc.h"
+#include <stdio.h>
+
+#define BUFSIZE 4096
+
+void usage(char *name)
+{
+ printf("Usage:\n"
+ "\t%s file1.ogg [file2.ogg]...\n", name);
+}
+
+
+int main(int argc, char **argv)
+{
+ static unsigned char buffer[BUFSIZE];
+ Shout s;
+
+ try {
+ try {
+ s.set_user("source");
+ s.set_password("hackme");
+ s.set_mount("/");
+ s.set_port(8001);
+ s.set_format(SHOUT_FORMAT_VORBIS);
+
+ s.open();
+ }
+ catch(ShoutErr error) {
+ printf("Error connecting to server %s:%d with username %s, password %s.\n",
+ s.get_host(), s.get_port(), s.get_user(), s.get_password());
+ throw error;
+ }
+
+ if(argc > 1) {
+ int delay;
+ for(int i=1; i<argc; i++) {
+ size_t bytes = 0;
+ FILE *f = fopen(*(argv+i), "rb");
+
+ while(!feof(f)) {
+ bytes = fread(buffer, sizeof(char), BUFSIZE, f);
+ s.send(buffer, bytes);
+
+ delay = s.delay();
+ if(delay > 1000) {
+ printf("delay: %d\n", s.delay());
+ }
+
+ s.sync();
+ }
+ }
+ s.close();
+ }
+ else {
+ usage(*argv);
+ }
+ }
+ catch(ShoutErr error) {
+ printf("Shout Error: %s (code %d)\n", error.err.c_str(), error.ern);
+ exit(1);
+ }
+
+ return 0;
+}
Property changes on: experimental/dholth/shoutpy/example.cc
___________________________________________________________________
Name: svn:executable
+ *
Added: experimental/dholth/shoutpy/example.py
===================================================================
--- experimental/dholth/shoutpy/example.py 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/example.py 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,31 @@
+#!/usr/bin/python
+#
+# Simple streaming to icecast.
+#
+# Daniel Holth, 2004
+
+import sys
+import shoutpy
+
+s = shoutpy.Shout()
+s.user = "source"
+s.password = "hackme"
+s.mount = "/shoutpy.ogg"
+s.port = 8001
+s.format = shoutpy.FORMAT_VORBIS
+
+s.open()
+
+for arg in sys.argv[1:]:
+ f = open(arg, "rb")
+
+ buf = f.read(4096)
+
+ while buf:
+ s.send(buf)
+ buf = f.read(512)
+ s.sync()
+
+ f.close()
+
+s.close()
Property changes on: experimental/dholth/shoutpy/example.py
___________________________________________________________________
Name: svn:executable
+ *
Added: experimental/dholth/shoutpy/gentoo/dev-python/shoutpy/shoutpy-0.5.2.ebuild
===================================================================
--- experimental/dholth/shoutpy/gentoo/dev-python/shoutpy/shoutpy-0.5.2.ebuild 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/gentoo/dev-python/shoutpy/shoutpy-0.5.2.ebuild 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,25 @@
+# Copyright 1999-2004 Gentoo Technologies, Inc.
+# Distributed under the terms of the GNU General Public License v2
+# $Header: $
+
+inherit distutils
+
+DESCRIPTION="Python bindings for libshout2."
+HOMEPAGE="http://dingoskidneys.com/shoutpy/"
+SRC_URI="http://dingoskidneys.com/shoutpy/${P}.tar.gz"
+
+LICENSE="LGPL-2.1"
+SLOT="0"
+KEYWORDS="~x86"
+
+DEPEND="dev-lang/python
+ >=media-libs/libshout-2.0
+ >=dev-libs/boost-1.31.0"
+
+# Install the example
+src_install () {
+ distutils_src_install
+
+ insinto /usr/share/doc/${PF}
+ doins ${S}/example.py
+}
Added: experimental/dholth/shoutpy/setup.py
===================================================================
--- experimental/dholth/shoutpy/setup.py 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/setup.py 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,43 @@
+#!/usr/bin/env python
+#
+# shoutpy's distutils setup script.
+#
+# Daniel Holth <dholth at fastmail.fm>
+# 15 Jan. 2004
+
+from distutils.core import setup
+from distutils.extension import Extension
+
+# local configuration
+import config
+
+description = """shoutpy provides Pythonic bindings for libshout 2."""
+
+classifiers="""\
+Development Status :: 3 - Alpha
+License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL)
+Operating System :: POSIX :: Linux
+Programming Language :: C++
+Programming Language :: Python
+Topic :: Software Development :: Libraries :: Python Modules
+Topic :: Multimedia :: Sound/Audio
+"""
+
+version="0.5.2"
+url = "http://dingoskidneys.com/shoutpy/"
+
+setup(name="shoutpy",
+ version=version,
+ description="Boost.Python bindings for libshout 2",
+ long_description=description,
+ author="Daniel Holth",
+ author_email="dholth at fastmail.fm",
+ url=url,
+ download_url=url+"shoutpy-"+version+".tar.gz",
+ platforms="linux",
+ license="GNU LGPL",
+ classifiers=filter(None, classifiers.splitlines()),
+ ext_modules=[Extension("shoutpy", ["shoutpy.cc", "shoutcc.cc"],
+ libraries=config.libraries,
+ include_dirs=config.include_dirs,
+ library_dirs=config.library_dirs)])
Property changes on: experimental/dholth/shoutpy/setup.py
___________________________________________________________________
Name: svn:executable
+ *
Added: experimental/dholth/shoutpy/shoutcc.cc
===================================================================
--- experimental/dholth/shoutpy/shoutcc.cc 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/shoutcc.cc 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,408 @@
+/* C++ wrapper for libshout2
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2.1 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Lesser General Public License for more details.
+ *
+ * You should have received a copy of the GNU Lesser General Public
+ * License along with this library; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ *
+ * For questions regarding this program contact
+ * Daniel Holth <dholth at fastmail.fm>
+ */
+
+/** \mainpage shoutpy's C++ API
+ * \section Intro
+ *
+ * These pages document the C++ API for libshout2, which is simply
+ * libshout2's object-oriented C functions like shout_get_foo(shout_t * object, ...)
+ * collected into one Shout:: class. This library doesn't attempt to wrap everything in C++;
+ * it doesn't pay off to wrap the non-object-oriented functions like shout_get_version().
+ *
+ * As they are all very similar, this set of documents
+ * might also help you understand how to use libshout2 or shoutpy, or even pyshout.
+ * In fact, most of the member documentation was copied from libshout2's documentation.
+ *
+ * This package was developed for shoutpy, an alternative
+ * Python wrapper for libshout2 that is implemented with
+ * Boost.Python. (http://boost.org/libs/python/doc/index.html)
+ *
+ * Shoutpy's home is http://dingoskidneys.com/shoutpy/.
+ *
+ * libshout and icecast live at http://www.icecast.org/.
+ *
+ * \section License
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2.1 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Lesser General Public License for more details.
+ *
+ * You should have received a copy of the GNU Lesser General Public
+ * License along with this library; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ *
+ * \author Daniel Holth < dholth at fastmail dot fm >
+ */
+
+
+#include "shoutcc.h"
+
+
+/// Provide default descriptions for libshout2 errors when a library-provided text description is not available.
+ShoutErr::ShoutErr(int n) {
+ char *d;
+ switch(n) {
+ case SHOUTERR_SUCCESS:
+ d = "SUCCESS";
+ break;
+ case SHOUTERR_INSANE:
+ d = "INSANE";
+ break;
+ case SHOUTERR_NOCONNECT:
+ d = "NOCONNECT";
+ break;
+ case SHOUTERR_NOLOGIN:
+ d = "NOLOGIN";
+ break;
+ case SHOUTERR_SOCKET:
+ d = "SOCKET";
+ break;
+ case SHOUTERR_MALLOC:
+ d = "MALLOC";
+ break;
+ case SHOUTERR_METADATA:
+ d = "METADATA";
+ break;
+ case SHOUTERR_CONNECTED:
+ d = "CONNECTED";
+ break;
+ case SHOUTERR_UNCONNECTED:
+ d = "UNCONNECTED";
+ break;
+ case SHOUTERR_UNSUPPORTED:
+ d = "UNSUPPORTED";
+ break;
+ default:
+ d = "";
+ }
+
+ this->err = d;
+}
+
+
+
+/// Constructor.
+Shout::Shout() {
+ this->self = shout_new();
+}
+
+/// Destructor.
+Shout::~Shout() {
+ shout_free(this->self);
+}
+
+/// Internal wrapper for libshout2 return codes. If it was an error, throw the appropriate ShoutErr object.
+void Shout::check(int code) {
+ if(code!=0) {
+ throw ShoutErr(code, this->get_error());
+ }
+}
+
+/// \brief Return a statically allocated string describing
+/// the last shout error that occured in this connection.
+/// Only valid until the next call affecting this connection.
+const char* Shout::get_error() {
+ return shout_get_error(this->self);
+}
+
+/// Return the shout error code of the last error that occured in this connection.
+int Shout::get_errno() {
+ return shout_get_errno(this->self);
+}
+
+/// Are we connected to a server?
+bool Shout::get_connected() {
+ return (shout_get_connected(this->self) == SHOUTERR_CONNECTED);
+}
+
+/// Set IP address or hostname of our server.
+/**
+ * The default is localhost.
+ * \param host IP address in dotted decimal format, or hostname, of server.
+ */
+void Shout::set_host(const char *host) {
+ this->check(shout_set_host(this->self, host));
+}
+
+/// Return IP address/hostname of our server.
+const char *Shout::get_host() {
+ return shout_get_host(this->self);
+}
+
+/// Set server port.
+/**
+ * The default is 8000.
+ */
+void Shout::set_port(unsigned short port) {
+ this->check(shout_set_port(this->self, port));
+}
+
+/// Return server port.
+unsigned short Shout::get_port() {
+ return shout_get_port(this->self);
+}
+
+/// Set password to authenticate to the server with.
+/**
+ * This parameter @b must be set. There is no default.
+ */
+void Shout::set_password(const char *password) {
+ this->check(shout_set_password(this->self, password));
+}
+
+/// Return the password.
+const char *Shout::get_password() {
+ return shout_get_password(this->self);
+}
+
+/// Set the mount point for this stream.
+/**
+ * A mountpoint is a resource on the icecast server that represents
+ * a single broadcast stream. Mountpoints are named similar to
+ * files (/mystream.ogg, /mymp3stream). When listeners connect
+ * to icecast2, they must specify the mountpoint in the request
+ * (i.e. http://192.168.1.10:8000/mystream.ogg). Additionally, source
+ * clients must specify a mountpoint when they connect as well. Statistics
+ * are kept track of by mountpoint. Mountpoints are a fundamental aspect
+ * of icecast2 and how it is organized.
+ *
+ * Only for protocols that support this option. ( \c SHOUT_PROTOCOL_ICY doesn't).
+ */
+void Shout::set_mount(const char *mount) {
+ this->check(shout_set_mount(this->self, mount));
+}
+
+/// Return this stream's mount point.
+const char *Shout::get_mount() {
+ return shout_get_mount(this->self);
+}
+
+/// Set the name of this stream.
+/**
+ * This must be for the benefit of listing the stream,
+ * e.g. "The Emo Hamster Rock Channel"
+ */
+void Shout::set_name(const char *name) {
+ this->check(shout_set_name(this->self, name));
+}
+
+/// Return the name of this stream.
+const char *Shout::get_name() {
+ return shout_get_name(this->self);
+}
+
+/// Set the URL of a site about this stream.
+void Shout::set_url(const char *url) {
+ this->check(shout_set_url(this->self, url));
+}
+
+/// Return URL of the site about this stream.
+const char *Shout::get_url() {
+ return shout_get_url(this->self);
+}
+
+/// Set the genre of this stream.
+/**
+ * This is usually a keyword list, eg "techno electronica world hippity-hop".
+ */
+void Shout::set_genre(const char *genre) {
+ this->check(shout_set_genre(this->self, genre));
+}
+
+/// Return the genre of this stream.
+const char *Shout::get_genre() {
+ return shout_get_genre(this->self);
+}
+
+/// Set username for authenticating with the server.
+void Shout::set_user(const char *username) {
+ this->check(shout_set_user(this->self, username));
+}
+
+/// Return the user name.
+const char *Shout::get_user() {
+ return shout_get_user(this->self);
+}
+
+/// Set the user agent header.
+/**
+ * This is \c libshout/VERSION by default. If you don't
+ * know what this function is for, don't use it.
+ */
+void Shout::set_agent(const char *username) {
+ this->check(shout_set_agent(this->self, username));
+}
+
+/// Return the user agent header.
+const char *Shout::get_agent() {
+ return shout_get_agent(this->self);
+}
+
+/// Set the description of this stream.
+void Shout::set_description(const char *description) {
+ this->check(shout_set_description(this->self, description));
+}
+
+/// Return the description of this stream.
+const char *Shout::get_description() {
+ return shout_get_description(this->self);
+}
+
+/// Set server-side archive filename.
+/**
+ * If the server supports it, you can request that your stream be archived
+ * on the server under the name \c dumpfile. This can quickly eat a lot of
+ * disk space, so think twice before setting it.
+ */
+void Shout::set_dumpfile(const char *dumpfile) {
+ this->check(shout_set_dumpfile(this->self, dumpfile));
+}
+
+/// Return server-side archive filename.
+const char *Shout::get_dumpfile() {
+ return shout_get_dumpfile(this->self);
+}
+
+/// Set a stream audio parameter.
+/**
+ * The currently defined parameters are listed in shout.h
+ * ("bitrate", "samplerate", "channels", "quality") but you
+ * are free to add additional fields if your directory server
+ * understands them.
+ */
+void Shout::set_audio_info(const char *name, const char *value) {
+ this->check(shout_set_audio_info(this->self, name, value));
+}
+
+/// Return a stream audio parameter.
+const char *Shout::get_audio_info(const char *name) {
+ return shout_get_audio_info(this->self, name);
+}
+
+/// Instruct the server to advertise (or not) this stream.
+/**
+ * Setting this to \c 1 asks the server to list the stream in
+ * any directories it knows about. To suppress listing, set this to
+ * \c 0. The default is \c 0.
+ */
+void Shout::set_public(unsigned int make_public) {
+ this->check(shout_set_public(this->self, make_public));
+}
+
+/// Return whether this stream will be public.
+unsigned int Shout::get_public() {
+ return shout_get_public(this->self);
+}
+
+/// Set the audio format of this stream.
+/**
+ * The default is \c SHOUT_FORMAT_VORBIS
+ */
+void Shout::set_format(unsigned int format) {
+ this->check(shout_set_format(this->self, format));
+}
+
+/// Return the audio format of the stream.
+unsigned int Shout::get_format() {
+ return shout_get_format(this->self);
+}
+
+/// Set the protocol with which to connect to the server.
+/**
+ * The default is \c SHOUT_PROTOCOL_HTTP (compatible with Icecast 2).
+ */
+void Shout::set_protocol(unsigned int protocol) {
+ this->check(shout_set_protocol(this->self, protocol));
+}
+
+/// Return the protocol this stream will use.
+unsigned int Shout::get_protocol() {
+ return shout_get_protocol(this->self);
+}
+
+/// Open a connection to a server. All connection parameters must have been set prior to this call.
+void Shout::open() {
+ this->check(shout_open(this->self));
+}
+
+/// Close this connection to the server.
+void Shout::close() {
+ this->check(shout_close(this->self));
+}
+
+/// Send audio data to the server.
+/**
+ * Send \c len bytes of audio data from the buffer pointed to by
+ * \c data to the server. The connection must already have been
+ * established by a successful call to Shout::shout_open.
+ */
+void Shout::send(const unsigned char *data, size_t len) {
+ this->check(shout_send(this->self, data, len));
+}
+
+/// Send data to the server, in an unfriendly, unsafe manner.
+/**
+ * Send \c len bytes of audio data from the buffer pointed to by
+ * \c data to the server. The data is not parsed for timing
+ * or validity, but sent raw over the connection. The connection
+ * must already have been established by a successful call to
+ * Shout::shout_open.
+ *
+ * \warning This function should not be used unless you know exactly what you
+ * are doing. Its use is deprecated and it may be removed in a future version of
+ * the library.
+ */
+ssize_t Shout::send_raw(const unsigned char *data, size_t len) {
+ return shout_send_raw(this->self, data, len);
+}
+
+
+/// Sleep until the server will be ready for more data.
+/**
+ * Causes the caller to sleep for the amount of time necessary to play back
+ * audio sent since the last call to Shout::shout_sync. Should be called
+ * before every call to Shout::shout_send to ensure that audio data is
+ * sent to the server at the correct speed. Alternatively, the caller may
+ * use Shout::shout_delay to determine the number of milliseconds to wait
+ * and delay itself.
+ */
+void Shout::sync() {
+ shout_sync(this->self);
+}
+
+/// Return delay, in milliseconds, after which server will be ready for more data.
+int Shout::delay() {
+ return shout_delay(this->self);
+}
+
+/// Valid only for Mp3, define the metadata (title, artist, etc.) for the current stream.
+/**
+ * Currently the only metadata supported is song title and only for MP3 streams.
+ *
+ * Ogg/Vorbis metadata should be embedded in the Ogg stream.
+ */
+void Shout::set_metadata(ShoutMetadata *metadata) {
+ this->check(shout_set_metadata(this->self, metadata->self));
+}
Added: experimental/dholth/shoutpy/shoutcc.h
===================================================================
--- experimental/dholth/shoutpy/shoutcc.h 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/shoutcc.h 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,141 @@
+/* C++ wrapper for libshout2
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2.1 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Lesser General Public License for more details.
+ *
+ * You should have received a copy of the GNU Lesser General Public
+ * License along with this library; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ *
+ * For questions regarding this program contact
+ * Daniel Holth <dholth at fastmail.fm>
+ */
+
+/** shoutcc.h
+ *
+ * Interface for the C++ wrapper to libshout2.
+ *
+ * @author Daniel Holth <dholth at fastmail.fm>
+ */
+
+
+#ifndef __SHOUTCC_H__
+#define __SHOUTCC_H__
+
+#include <shout/shout.h>
+#include <string>
+
+
+class ShoutMetadata;
+
+/// The exception.
+/**
+ * Wherever libshout2 returns error codes, shoutpy throws exceptions.
+ */
+class ShoutErr {
+ public:
+ /// libshout2 error code. See shout.h
+ int ern;
+ /// libshout2 error description.
+ std::string err;
+
+ ShoutErr(int n);
+ ShoutErr(int n, std::string e) {
+ this->ern = n;
+ this->err = e; }
+};
+
+/// The main event. Wraps the shout_t object in a C++ object.
+class Shout {
+ private:
+ /// libshout2 data structure that we wrap.
+ shout_t *self;
+
+ public:
+ shout_t *get_self() { return this->self; }
+
+ Shout();
+ ~Shout();
+
+ void check(int code);
+
+ const char *get_error();
+
+ int get_errno();
+
+ bool get_connected();
+
+ void set_host(const char *host);
+ const char *get_host();
+
+ void set_port(unsigned short port);
+ unsigned short get_port();
+
+ void set_password(const char *password);
+ const char *get_password();
+
+ void set_mount(const char *mount);
+ const char *get_mount();
+
+ void set_name(const char *name);
+ const char *get_name();
+
+ void set_url(const char *url);
+ const char *get_url();
+
+ void set_genre(const char *genre);
+ const char *get_genre();
+
+ void set_user(const char *username);
+ const char *get_user();
+
+ void set_agent(const char *username);
+ const char *get_agent();
+
+ void set_description(const char *description);
+ const char *get_description();
+
+ void set_dumpfile(const char *dumpfile);
+ const char *get_dumpfile();
+
+ void set_audio_info(const char *name, const char *value);
+ const char *get_audio_info(const char *name);
+
+ void set_public(unsigned int make_public);
+ unsigned int get_public();
+
+ void set_format(unsigned int format);
+ unsigned int get_format();
+
+ void set_protocol(unsigned int protocol);
+ unsigned int get_protocol();
+
+ void open();
+ void close();
+ void send(const unsigned char *data, size_t len);
+ ssize_t send_raw(const unsigned char *data, size_t len);
+ void sync();
+ int delay();
+
+ void set_metadata(ShoutMetadata *metadata);
+};
+
+/// Wrapper for shout_metadata_t, a dictionary-like metadata object.
+class ShoutMetadata {
+ public:
+ shout_metadata_t *self;
+
+ ShoutMetadata() { this->self = shout_metadata_new(); }
+ ~ShoutMetadata() { shout_metadata_free(this->self); }
+
+ void add(const char *name, const char *value) { shout_metadata_add(this->self, name, value); }
+};
+
+#endif
Added: experimental/dholth/shoutpy/shoutpy.cc
===================================================================
--- experimental/dholth/shoutpy/shoutpy.cc 2004-11-23 02:33:04 UTC (rev 8261)
+++ experimental/dholth/shoutpy/shoutpy.cc 2004-11-23 02:43:09 UTC (rev 8262)
@@ -0,0 +1,141 @@
+/* Boost.Python wrapper for libshout 2 */
+/* */
+/* This library is free software; you can redistribute it and/or */
+/* modify it under the terms of the GNU Lesser General Public */
+/* License as published by the Free Software Foundation; either */
+/* version 2.1 of the License, or (at your option) any later version. */
+/* */
+/* This library is distributed in the hope that it will be useful, */
+/* but WITHOUT ANY WARRANTY; without even the implied warranty of */
+/* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU */
+/* Lesser General Public License for more details. */
+/* */
+/* You should have received a copy of the GNU Lesser General Public */
+/* License along with this library; if not, write to the Free Software */
+/* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */
+/* */
+/* For questions regarding this program contact */
+/* Daniel Holth <dholth at fastmail.fm> */
+
+/**
+ * Control libshout through a Boost.Python wrapper.
+ *
+ * @author Daniel Holth
+ */
+
+#include <boost/python.hpp>
+#include <boost/python/def.hpp>
+#include <boost/python/module.hpp>
+#include <boost/python/tuple.hpp>
+#include <boost/python/exception_translator.hpp>
+
+#include "shoutcc.h"
+
+using namespace boost::python;
+
+void translate(ShoutErr const& x) {
+ PyErr_SetObject(PyExc_RuntimeError, make_tuple(x.ern, x.err).ptr());
+}
+
+void shoutpy_send(Shout& s, str data) {
+ int len;
+ char const* c_str;
+
+ len = extract<int>(data.attr("__len__")());
+ c_str = extract<char const*>(data);
+
+ s.send((const unsigned char*)c_str, len);
+}
+
+tuple shoutpy_shout_version() {
+ int major, minor, patch;
+ const char *name;
+
+ name = shout_version(&major, &minor, &patch);
+
+ return make_tuple(name, make_tuple(major, minor, patch));
+}
+
+BOOST_PYTHON_MODULE_INIT(shoutpy)
+{
+ register_exception_translator<ShoutErr>(&translate);
+
+ // init is automatic in libshout-2.0.0, and shutdown (might) crash python, which is against the rules.
+ // def("init", &shout_init);
+ // def("shutdown", &shout_shutdown);
+
+ scope().attr("version") = shoutpy_shout_version();
+
+#ifdef SHOUT_FORMAT_VORBIS
+ scope().attr("FORMAT_VORBIS") = SHOUT_FORMAT_VORBIS;
+#endif
+#ifdef SHOUT_FORMAT_MP3
+ scope().attr("FORMAT_MP3") = SHOUT_FORMAT_MP3;
+#endif
+#ifdef SHOUT_FORMAT_OGG
+ scope().attr("FORMAT_OGG") = SHOUT_FORMAT_OGG;
+#endif
+
+ scope().attr("PROTOCOL_HTTP") = SHOUT_PROTOCOL_HTTP;
+ scope().attr("PROTOCOL_XAUDIOCAST") = SHOUT_PROTOCOL_XAUDIOCAST;
+ scope().attr("PROTOCOL_ICY") = SHOUT_PROTOCOL_ICY;
+
+ scope().attr("AI_BITRATE") = SHOUT_AI_BITRATE;
+ scope().attr("AI_SAMPLERATE") = SHOUT_AI_SAMPLERATE;
+ scope().attr("AI_CHANNELS") = SHOUT_AI_CHANNELS;
+ scope().attr("AI_QUALITY") = SHOUT_AI_QUALITY;
+
+ class_<Shout>("Shout", "Shout() -> new libshout2 connection object.")
+ .add_property("version", &shoutpy_shout_version)
+// "libshout2 version as a (string, values) tuple, eg. ('2.0', (2, 0, 0)).")
+ .add_property("error", &Shout::get_error)
+// "description of this connection's last error.")
+ .add_property("errno", &Shout::get_errno)
+// "error code of this connection's last error.")
+ .add_property("connected", &Shout::get_connected)
+// "boolean connection status.")
+ .add_property("agent", &Shout::get_agent, &Shout::set_agent)
+// "user agent header.")
+ .add_property("description", &Shout::get_description, &Shout::set_description)
+// "description of the stream.")
+ .add_property("dumpfile", &Shout::get_dumpfile, &Shout::set_dumpfile)
+// "filename for a server-side archive of the stream")
+ .add_property("format", &Shout::get_format, &Shout::set_format)
+// "audio format. shoutpy.FORMAT_VORBIS or shoutpy.FORMAT_MP3.")
+ .add_property("genre", &Shout::get_genre, &Shout::set_genre)
+// "genre. usually a list (whitespace-delimited string) of keywords.")
+ .add_property("host", &Shout::get_host, &Shout::set_host)
+// "IP address or dns hostname of server.")
+ .add_property("mount", &Shout::get_mount, &Shout::set_mount)
+// "mountpoint for this stream.")
+ .add_property("name", &Shout::get_name, &Shout::set_name)
+ .add_property("password", &Shout::get_password, &Shout::set_password)
+ .add_property("port", &Shout::get_port, &Shout::set_port)
+// "server port. default is 8000.")
+ .add_property("protocol", &Shout::get_protocol, &Shout::set_protocol)
+// "PROTOCOL_HTTP, PROTOCOL_XAUDIOCAST or PROTOCOL_ICY")
+ .add_property("public", &Shout::get_public, &Shout::set_public)
+// "should the server advertize this stream?")
+ .add_property("url", &Shout::get_url, &Shout::set_url)
+// "URL of a page describing this stream.")
+ .add_property("user", &Shout::get_user, &Shout::set_user)
+// "Username for authenticating with the server.")
+ .def("get_audio_info", &Shout::get_audio_info,
+ "x.get_audio_info(\"keyword\") -> value")
+ .def("set_audio_info", &Shout::set_audio_info,
+ "x.set_audio_info(\"keyword\", \"value\") -> None. Set information about the audio itself (channels, bitrate, ...).")
+ .def("open", &Shout::open,
+ "x.open() -> None. Connect to the server.")
+ .def("close", &Shout::close,
+ "x.close() -> None. Disconnect from the server.")
+ .def("send", &shoutpy_send,
+ "x.send(data) -> None. Send audio to the server.")
+ // .def("send_raw", &Shout::send_raw) -- intentionally unexposed
+ .def("sync", &Shout::sync,
+ "x.sync() -> None. Block until the server is ready for more data.")
+ .def("delay", &Shout::delay,
+ "x.delay() -> milliseconds until server will need more audio data.");
+
+ class_<ShoutMetadata>("ShoutMetadata")
+ .def("add", &ShoutMetadata::add);
+}
More information about the commits
mailing list