[Galago-commits] r2795 - in trunk: . notify-sharp
notify-sharp/notify notify-sharp/notify/generated
notify-sharp/sources notify-sharp/tests
galago-commits at freedesktop.org
galago-commits at freedesktop.org
Thu May 4 01:31:40 PDT 2006
Author: chipx86
Date: 2006-05-04 01:31:34 -0700 (Thu, 04 May 2006)
New Revision: 2795
Added:
trunk/notify-sharp/
trunk/notify-sharp/AUTHORS
trunk/notify-sharp/COPYING
trunk/notify-sharp/ChangeLog
trunk/notify-sharp/INSTALL
trunk/notify-sharp/Makefile.am
trunk/notify-sharp/NEWS
trunk/notify-sharp/README
trunk/notify-sharp/autogen.sh
trunk/notify-sharp/configure.ac
trunk/notify-sharp/notify-sharp.pc.in
trunk/notify-sharp/notify/
trunk/notify-sharp/notify/AssemblyInfo.cs.in
trunk/notify-sharp/notify/Makefile.am
trunk/notify-sharp/notify/generated/
trunk/notify-sharp/notify/notify-sharp.metadata
trunk/notify-sharp/notify/notify-sharp.snk
trunk/notify-sharp/sources/
trunk/notify-sharp/sources/Makefile.am
trunk/notify-sharp/sources/notify-sharp-sources.xml.in
trunk/notify-sharp/tests/
trunk/notify-sharp/tests/Makefile.am
Log:
Add the beginnings of notify-sharp.
Property changes on: trunk/notify-sharp
___________________________________________________________________
Name: svn:ignore
+ ABOUT-NLS
Doxyfile
Makefile.in
Makefile
aclocal.m4
autom4te*.cache
confdefs.h
config.cache
config.guess
config.h
config.h.in
config.log
config.status
config.sub
configure
depcomp
install-sh
intl
stamp-h
stamp-h1
stamp-h.in
*.pc
*.spec
libtool
ltconfig
ltmain.sh
missing
mkinstalldirs
.todo.*
.*.swp
.*.swo
*.diff
*.gz
*.package
*.patch
Added: trunk/notify-sharp/AUTHORS
===================================================================
--- trunk/notify-sharp/AUTHORS 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/AUTHORS 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1 @@
+Christian Hammond <chipx86 at chipx86.com>
Added: trunk/notify-sharp/COPYING
===================================================================
--- trunk/notify-sharp/COPYING 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/COPYING 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,504 @@
+ 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: trunk/notify-sharp/ChangeLog
===================================================================
Added: trunk/notify-sharp/INSTALL
===================================================================
--- trunk/notify-sharp/INSTALL 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/INSTALL 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,229 @@
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
+Foundation, Inc.
+
+ This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+ These are generic installation instructions.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system. If you're
+ using `csh' on an old version of System V, you might need to type
+ `sh ./configure' instead to prevent `csh' from trying to execute
+ `configure' itself.
+
+ Running `configure' takes awhile. While running, it prints some
+ messages telling which features it is checking for.
+
+ 2. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+Compilers and Options
+=====================
+
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+ If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+ By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+ Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+ There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on. Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+ If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+ Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+`configure' Invocation
+======================
+
+ `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+ Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+
+`--srcdir=DIR'
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
Added: trunk/notify-sharp/Makefile.am
===================================================================
--- trunk/notify-sharp/Makefile.am 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/Makefile.am 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,11 @@
+SUBDIRS = sources notify tests
+
+pcdata_DATA= notify-sharp.pc
+pcdatadir = $(libdir)/pkgconfig
+
+EXTRA_DIST = \
+ AUTHORS NEWS INSTALL COPYING README \
+ ChangeLog \
+ autogen.sh \
+ configure.ac \
+ notify-sharp.pc.in
Added: trunk/notify-sharp/NEWS
===================================================================
Added: trunk/notify-sharp/README
===================================================================
--- trunk/notify-sharp/README 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/README 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1 @@
+Galago-Gtk# for Mono
Added: trunk/notify-sharp/autogen.sh
===================================================================
--- trunk/notify-sharp/autogen.sh 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/autogen.sh 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,58 @@
+#!/bin/sh
+# Run this to generate all the initial makefiles, etc.
+
+DIE=0
+
+PROJECT=notify-sharp
+
+echo "Generating configuration files for $PROJECT, please wait..."
+
+(autoconf --version) < /dev/null > /dev/null 2>&1 || {
+ echo
+ echo "You must have autoconf installed to compile $PROJECT."
+ echo "Download the appropriate package for your distribution,"
+ echo "or get the source tarball at ftp://ftp.gnu.org/pub/gnu/"
+ DIE=1
+}
+
+(libtool --version) < /dev/null > /dev/null 2>&1 || {
+ echo
+ echo "You must have libtool installed to compile $PROJECT."
+ echo "Download the appropriate package for your distribution,"
+ echo "or get the source tarball at ftp://ftp.gnu.org/pub/gnu/"
+ DIE=1
+}
+
+(automake --version) < /dev/null > /dev/null 2>&1 || {
+ echo
+ echo "You must have automake installed to compile $PROJECT."
+ echo "Download the appropriate package for your distribution,"
+ echo "or get the source tarball at ftp://ftp.gnu.org/pub/gnu/"
+ DIE=1
+}
+
+[ $DIE -eq 1 ] && exit 1;
+
+echo " libtoolize --copy --force"
+libtoolize --copy --force
+echo " aclocal $ACLOCAL_FLAGS"
+aclocal $ACLOCAL_FLAGS
+echo " autoheader"
+autoheader
+echo " automake --add-missing"
+automake --add-missing
+echo " autoconf"
+autoconf
+
+if [ -x config.status -a -z "$*" ]; then
+ ./config.status --recheck
+else
+ if test -z "$*"; then
+ echo "I am going to run ./configure with no arguments - if you wish"
+ echo "to pass any to it, please specify them on the $0 command line."
+ echo "If you do not wish to run ./configure, press Ctrl-C now."
+ trap 'echo "configure aborted" ; exit 0' 1 2 15
+ sleep 1
+ fi
+ ./configure "$@";
+fi
Property changes on: trunk/notify-sharp/autogen.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: trunk/notify-sharp/configure.ac
===================================================================
--- trunk/notify-sharp/configure.ac 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/configure.ac 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,182 @@
+dnl Process this file with autoconf to create configure.
+
+dnl ################################################################
+dnl # Initialize autoconf
+dnl ################################################################
+AC_INIT(notify-sharp, 0.1.0, chipx86 at chipx86.com)
+AC_PREREQ(2.50)
+AC_CONFIG_SRCDIR(config.h.in)
+AC_COPYRIGHT([Copyright 2006 Christian Hammond])
+
+
+dnl ################################################################
+dnl # Version information
+dnl ################################################################
+NOTIFY_SHARP_MAJOR_VERSION=0
+NOTIFY_SHARP_MINOR_VERSION=1
+NOTIFY_SHARP_MICRO_VERSION=0
+NOTIFY_SHARP_DEVEL_VERSION=0
+
+NOTIFY_SHARP_VERSION=$NOTIFY_SHARP_MAJOR_VERSION.$NOTIFY_SHARP_MINOR_VERSION.$NOTIFY_SHARP_MICRO_VERSION
+
+if test "x$NOTIFY_SHARP_DEVEL_VERSION" != "x0"; then
+ NOTIFY_SHARP_VERSION=$NOTIFY_SHARP_VERSION.$NOTIFY_SHARP_DEVEL_VERSION
+fi
+
+AC_DEFINE_UNQUOTED(NOTIFY_SHARP_MAJOR_VERSION, $NOTIFY_SHARP_MAJOR_VERSION,
+ [notify-sharp major version.])
+AC_DEFINE_UNQUOTED(NOTIFY_SHARP_MINOR_VERSION, $NOTIFY_SHARP_MINOR_VERSION,
+ [notify-sharp minor version.])
+AC_DEFINE_UNQUOTED(NOTIFY_SHARP_MICRO_VERSION, $NOTIFY_SHARP_MICRO_VERSION,
+ [notify-sharp micro version.])
+AC_DEFINE_UNQUOTED(NOTIFY_SHARP_VERSION, "$NOTIFY_SHARP_VERSION",
+ [notify-sharp version.])
+
+
+API_VERSION=1.0.0.0
+AC_SUBST(API_VERSION)
+
+dnl ################################################################
+dnl # Initialize automake
+dnl ################################################################
+VERSION=$NOTIFY_SHARP_VERSION
+PACKAGE=notify-sharp
+
+AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
+
+dnl ################################################################
+dnl # Specify a header configuration file
+dnl ################################################################
+AM_CONFIG_HEADER(config.h)
+
+dnl ################################################################
+dnl # Check for some standard stuff.
+dnl ################################################################
+AC_PROG_CC
+#AC_ARG_PROGRAM
+AC_PROG_CPP
+AC_PROG_MAKE_SET
+AC_PROG_LN_S
+AC_PROG_INSTALL
+
+AC_C_CONST
+AC_TYPE_SIZE_T
+AC_EXEEXT
+
+AM_PROG_LIBTOOL
+
+
+dnl ################################################################
+dnl # Look for Mono
+dnl ################################################################
+MONO_REQUIRED_VERSION=1.0
+PKG_CHECK_MODULES(MONO, mono >= $MONO_REQUIRED_VERSION, has_mono=true, has_mono=false)
+
+if test "x$has_mono" = "xtrue"; then
+ AC_PATH_PROG(RUNTIME, mono, no)
+ AC_PATH_PROG(CSC, mcs, no)
+
+ GACUTIL_FLAGS='/package $(PACKAGE) /gacdir $(libdir) /root $(DESTDIR)$(libdir)'
+
+ GENERATED_SOURCES=generated/*.cs
+
+ if test `uname -s` = "Darwin"; then
+ LIB_PREFIX=
+ LIB_SUFFIX=.dylib
+ else
+ LIB_PREFIX=.so
+ LIB_SUFFIX=
+ fi
+
+ AC_PATH_PROG(GAPI_FIXUP, gapi2-fixup, no)
+ AC_PATH_PROG(GAPI_CODEGEN, gapi2-codegen, no)
+else
+ AC_PATH_PROG(CSC, csc.exe, no)
+
+ GENERATED_SOURCES=generated\\\\*.cs
+
+ GACUTIL_FLAGS=
+
+ if test "x$CSC" = "xno"; then
+ AC_MSG_ERROR([You need to install either Mono or .NET])
+ else
+ RUNTIME=
+ LIB_PREFIX=
+ LIB_SUFFIX=.dylib
+ fi
+fi
+
+GTK_SHARP_PREFIX=`pkg-config --variable=prefix gtk-sharp-2.0`
+AC_SUBST(GTK_SHARP_PREFIX)
+
+CS="C#"
+if test "x$CSC" = "xno"; then
+ AC_MSG_ERROR([No $CS compiler found])
+fi
+
+AC_PATH_PROG(GACUTIL, gacutil, no)
+if test "x$GACUTIL" = "xno"; then
+ AC_MSG_ERROR([No gacutil tool found])
+fi
+
+AC_SUBST(RUNTIME)
+AC_SUBST(CSC)
+AC_SUBST(LIB_PREFIX)
+AC_SUBST(LIB_SUFFIX)
+AC_SUBST(GACUTIL)
+AC_SUBST(GACUTIL_FLAGS)
+AC_SUBST(GENERATED_SOURCES)
+
+GTK_SHARP_MIN_VERSION="1.0"
+AC_SUBST(GTK_SHARP_MIN_VERSION)
+
+PKG_CHECK_MODULES(GTK_SHARP, gtk-sharp-2.0 >= $GTK_SHARP_MIN_VERSION)
+AC_SUBST(GTK_SHARP_CFLAGS)
+AC_SUBST(GTK_SHARP_LIBS)
+
+PKG_CHECK_MODULES(NOTIFY, libnotify >= 0.4.0)
+AC_SUBST(NOTIFY_CFLAGS)
+AC_SUBST(NOTIFY_LIBS)
+
+
+dnl ################################################################
+dnl # Check if we want to use a tarball or svn for updates
+dnl ################################################################
+AC_ARG_WITH([libnotify-svn], AC_HELP_STRING([--with-libnotify-svn],
+ [Build against libnotify SVN]),
+[
+ use_libnotify_svn=yes
+],[
+ if test "x$NOTIFY_SHARP_DEVEL_VERSION" != "x0"; then
+ use_libnotify_svn=yes;
+ else
+ use_libnotify_svn=no;
+ fi
+])
+
+AM_CONDITIONAL(USE_NOTIFY_SVN, test "x$use_libnotify_svn" = "xyes",
+ [Define if using libnotify SVN.])
+
+
+dnl ################################################################
+dnl # Output the Makefiles
+dnl ################################################################
+AC_CONFIG_FILES([
+notify-sharp.pc
+Makefile
+notify/Makefile
+notify/AssemblyInfo.cs
+sources/Makefile
+sources/notify-sharp-sources.xml
+tests/Makefile
+])
+
+AC_OUTPUT
+
+echo
+echo $PACKAGE v$VERSION
+
+echo
+echo "Now type make to compile"
+echo "Then su to root and type: make install"
+echo
Property changes on: trunk/notify-sharp/notify
___________________________________________________________________
Name: svn:ignore
+ AssemblyInfo.cs
Makefile
Makefile.in
generated-stamp
*.dll
*.raw
notify-api.xml
.*.swp
Added: trunk/notify-sharp/notify/AssemblyInfo.cs.in
===================================================================
--- trunk/notify-sharp/notify/AssemblyInfo.cs.in 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/notify/AssemblyInfo.cs.in 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,6 @@
+using System.Reflection;
+using System.Runtime.CompilerServices;
+
+[assembly:AssemblyVersion("@API_VERSION@")]
+[assembly:AssemblyDelaySign(false)]
+[assembly:AssemblyKeyFile("@srcdir@/notify-sharp.snk")]
Added: trunk/notify-sharp/notify/Makefile.am
===================================================================
--- trunk/notify-sharp/notify/Makefile.am 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/notify/Makefile.am 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,71 @@
+API = notify-api.xml
+RAW_API = notify-api.raw
+ADDITIONAL_API =
+
+INCLUDE_API = \
+ $(GTK_SHARP_PREFIX)/share/gapi-2.0/art-api.xml \
+ $(GTK_SHARP_PREFIX)/share/gapi-2.0/pango-api.xml \
+ $(GTK_SHARP_PREFIX)/share/gapi-2.0/atk-api.xml \
+ $(GTK_SHARP_PREFIX)/share/gapi-2.0/gtk-api.xml \
+ $(GTK_SHARP_PREFIX)/share/gapi-2.0/gdk-api.xml
+
+METADATA = notify-sharp.metadata
+ASSEMBLY_NAME = notify-sharp
+references = -pkg:gtk-sharp-2.0
+
+TARGET = $(ASSEMBLY)
+ASSEMBLY = $(ASSEMBLY_NAME).dll
+gapidir = $(datadir)/gapi-2.0
+noinst_DATA = $(ASSEMBLY)
+gapi_DATA = $(API) $(ADDITIONAL_API)
+
+CLEANFILES = \
+ $(ASSEMBLY) \
+ generated-stamp generated/*.cs \
+ $(API) \
+ $(RAW_API) \
+ glue/generated.c
+
+DISTCLEANFILES = AssemblyInfo.cs
+
+sources =
+build_sources = $(addprefix $(srcdir)/, $(sources)) AssemblyInfo.cs
+
+customs =
+
+build_customs = $(addprefix $(srcdir)/, $(customs))
+
+EXTRA_DIST = \
+ AssemblyInfo.cs.in \
+ notify-sharp.snk \
+ $(RAW_API) \
+ $(METADATA) \
+ $(customs) \
+ $(sources)
+
+$(API): $(srcdir)/$(RAW_API) $(srcdir)/$(METADATA)
+ sed -e 's/ name="GalagoGtk/ name="/g' $(srcdir)/$(RAW_API) > $(API)
+ chmod u+w $(API)
+ $(GAPI_FIXUP) --api=$(API) --metadata=$(srcdir)/$(METADATA)
+
+generated-stamp: $(API) $(srcdir)/$(ADDITIONAL_API) $(build_customs)
+ rm -f generated/* && \
+ $(GAPI_CODEGEN) --generate $(API) \
+ --include $(INCLUDE_API) --outdir=generated --customdir=$(srcdir) --assembly-name=$(ASSEMBLY_NAME) \
+ && touch generated-stamp
+
+$(ASSEMBLY): $(build_sources) generated-stamp notify-sharp.snk
+ $(CSC) /unsafe /out:$(ASSEMBLY) /target:library $(references) $(build_sources) $(GENERATED_SOURCES)
+
+install-data-local:
+ @if test -n '$(TARGET)'; then \
+ echo "$(GACUTIL) /i $(ASSEMBLY) /f $(GACUTIL_FLAGS)"; \
+ $(GACUTIL) /i $(ASSEMBLY) /f $(GACUTIL_FLAGS) || exit 1; \
+ fi
+
+uninstall-local:
+ @if test -n '$(TARGET)'; then \
+ echo "$(GACUTIL) /u $(ASSEMBLY_NAME) $(GACUTIL_FLAGS)"; \
+ $(GACUTIL) /u $(ASSEMBLY_NAME) $(GACUTIL_FLAGS) || exit 1; \
+ fi
+
Property changes on: trunk/notify-sharp/notify/generated
___________________________________________________________________
Name: svn:ignore
+ *.cs
.*.swp
Added: trunk/notify-sharp/notify/notify-sharp.metadata
===================================================================
--- trunk/notify-sharp/notify/notify-sharp.metadata 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/notify/notify-sharp.metadata 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,4 @@
+<?xml version="1.0"?>
+
+<metadata>
+</metadata>
Added: trunk/notify-sharp/notify/notify-sharp.snk
===================================================================
(Binary files differ)
Property changes on: trunk/notify-sharp/notify/notify-sharp.snk
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/notify-sharp/notify-sharp.pc.in
===================================================================
--- trunk/notify-sharp/notify-sharp.pc.in 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/notify-sharp.pc.in 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,9 @@
+prefix=@prefix@
+exec_prefix=@exec_prefix@
+libdir=@libdir@
+
+Name: Notify#
+Description: Notify# - libnotify .NET Bindings
+Version: @VERSION@
+Requires: libnotify
+Libs: -r:${libdir}/mono/notify-sharp/notify-sharp.dll
Property changes on: trunk/notify-sharp/sources
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
notify-sharp-sources.xml
libnotify
*.gz
.*.swp
Added: trunk/notify-sharp/sources/Makefile.am
===================================================================
--- trunk/notify-sharp/sources/Makefile.am 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/sources/Makefile.am 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,40 @@
+source = notify-sharp-sources.xml
+
+SVN_URL = http://svn.galago-project.org/trunk/libnotify
+
+LIBNOTIFY_VERSION=0.4.0
+TARBALL_URL=http://www.galago-project.org/files/releases/source/libnotify
+TARBALL_DIR=libnotify-$(LIBNOTIFY_VERSION)
+TARBALL_NAME=$(TARBALL_DIR).tar.bz2
+
+if USE_NOTIFY_SVN
+GET_METHOD = get-from-svn
+else
+GET_METHOD = get-from-tarball
+endif
+
+all: $(GET_METHOD)
+ gapi2-parser $(srcdir)/$(source)
+
+get-from-tarball:
+ if test ! -d libnotify; then \
+ if test ! -f $(TARBALL_NAME); then \
+ wget $(TARBALL_URL)/$(TARBALL_NAME); \
+ fi; \
+ tar -xjvf $(TARBALL_NAME); \
+ mv $(TARBALL_DIR) libnotify; \
+ rm -f $(TARBALL_NAME); \
+ fi
+
+get-from-svn:
+ @if test -d libnotify; then \
+ cd libnotify && svn up; \
+ else \
+ svn checkout $(SVN_URL); \
+ fi
+
+uninstall-local:
+ rm -rf libnotify
+
+EXTRA_DIST = $(source)
+DISTCLEANFILES = libnotify $(TARBALL_NAME)
Added: trunk/notify-sharp/sources/notify-sharp-sources.xml.in
===================================================================
--- trunk/notify-sharp/sources/notify-sharp-sources.xml.in 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/sources/notify-sharp-sources.xml.in 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,9 @@
+<gapi-parser-input>
+ <api filename="../notify/notify-api.raw">
+ <library name="libnotify">
+ <namespace name="Notify">
+ <dir>@srcdir@/libnotify/libnotify</dir>
+ </namespace>
+ </library>
+ </api>
+</gapi-parser-input>
Property changes on: trunk/notify-sharp/tests
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
*.bak
*.exe
.*.swp
Added: trunk/notify-sharp/tests/Makefile.am
===================================================================
--- trunk/notify-sharp/tests/Makefile.am 2006-04-29 23:47:11 UTC (rev 2794)
+++ trunk/notify-sharp/tests/Makefile.am 2006-05-04 08:31:34 UTC (rev 2795)
@@ -0,0 +1,14 @@
+ASSEMBLIES = ../notify/notify-sharp.dll
+REFERENCES = \
+ $(addprefix /r:, $(ASSEMBLIES)) \
+ -pkg:gtk-sharp-2.0
+
+TARGETS =
+
+noinst_SCRIPTS = $(TARGETS)
+
+all: $(TARGETS)
+
+EXTRA_DIST =
+CLEANFILES = $(TARGETS)
+
More information about the galago-commits
mailing list