No description
  • C# 97.9%
  • Makefile 1.1%
  • Shell 0.5%
  • M4 0.5%
Find a file
Andrés G. Aragoneses ba006f4708 Fix build
1497594612 introduced
a build breakage by accident.
2015-07-07 13:59:51 +02:00
build build: Bump mono dependency to 3.2.8 2015-05-09 16:17:42 +02:00
Hyena Fix build 2015-07-07 13:59:51 +02:00
Hyena.Data.Sqlite Windows: Specify CallingConvention everywhere (bgo#751045) 2015-07-06 21:04:04 +02:00
Hyena.Gui osx: fix some native library names (bgo#752030) 2015-07-06 21:25:53 +02:00
.gitattributes Add a .gitattributes to unset crlf for *.sln 2011-06-03 15:55:20 +02:00
.gitignore add obj/ dirs to .gitignore 2011-02-03 11:16:40 -06:00
autogen.sh Revamp build system to be compatible with Banshee's 2010-05-25 15:31:05 -07:00
configure.ac build: Bump mono dependency to 3.2.8 2015-05-09 16:17:42 +02:00
COPYING [release] Prepare for 0.3 release 2010-05-06 17:58:10 -07:00
hyena.doap [release] Update configure.ac, .doap, and NEWS for 0.5 2010-10-06 14:45:53 -05:00
Hyena.sln Hyena.sln: Adjust naming convention policy to match our guidelines 2013-11-16 12:00:30 +01:00
Makefile.am build: The target 'hg' depends on Hyena being built 2011-07-18 17:58:52 +01:00
Makefile.include Working make-fu 2009-08-13 12:00:41 -07:00
NEWS [release] Update configure.ac, .doap, and NEWS for 0.5 2010-10-06 14:45:53 -05:00
README [build] Assume submodules build in lib/Hyena/ subdir 2010-06-17 15:24:22 -07:00

This is a library of useful GUI and non-GUI C# code, originally used in Banshee.

NOTE
** It is not API stable, and so is not installed to the GAC.**

There are three ways to use Hyena in your app:

1) Require it as an external dep; copy its .dll files into your project

   Applications using it should make a local copy of whatever components you use.
   That is, you should consider Hyena a build-time dependency, not a run-time, since
   at run-time your app will contain a copy of Hyena.

   There are variables defined in the pkg-config files that contain assemblies 
   and files needed for a given component of Hyena (eg hyena, hyena.data.sqlite, 
   and hyena.gui).

   pkg-config --variable=Assemblies hyena
   pkg-config --variable=Files hyena
   
   You can look at PDF Mod for an example of how to use Hyena:

   http://git.gnome.org/cgit/pdfmod/tree/configure.ac
   http://git.gnome.org/cgit/pdfmod/tree/Makefile.am
   http://git.gnome.org/cgit/pdfmod/tree/src/Makefile.am

2) Include it as a submodule in your git repo

   This is advantageous if you want to closely track and maybe contribute
   back to Hyena.  It also means developers don't have to install Hyena
   themselves from packages or git.

     git submodule add git://git.gnome.org/hyena lib/Hyena
     git submodule update --init
     git add .gitmodules

   Then you'll need to add Hyena to your build system.  See Banshee's setup:

     http://git.gnome.org/cgit/banshee/tree/configure.ac
     http://git.gnome.org/cgit/banshee/tree/Makefile.am

   You can also include the appropriate .csproj in your .sln.  Set them to
   build under the 'Submodule' configuration, and the binaries will get
   outputted to ../../bin from the Hyena checkout directory.

3) Bundle the .dll files in your project

   It's an expedient, but not good form for FOSS projects.