swig/Examples/chicken/egg
2013-04-19 22:47:28 +01:00
..
Makefile Chicken makefiles tweaks for consistency with other languages - still more to be done though 2013-04-19 22:47:28 +01:00
mod1.i Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00
mod2.i Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00
multi.setup Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00
multi_init.scm Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00
README Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00
single.i Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00
single.setup Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00
test.scm Chicken: a few bug fixes, a new example and some new test suite runme, and some doc updates 2005-04-05 17:48:31 +00:00

These examples show how to build a chicken extension module in the form of an
egg.  There are two eggs that get built, single.egg which contains a single
module which is built with -nounit and multi.egg, which contains two modules
mod1 and mod2.  These are built normally, and multi_init.scm loads them both.
Read section "17.4.2 Building chicken extension libraries" in the manual
for a description of these two techniques.

To build:

$ make
$ make setup
$ make run

$ make clean

The eggs are built into an eggs subdirectory, because chicken-setup has
problems installing eggs when there are other files named similar in
the same directory.  The make setup step runs chicken-setup to install
the eggs into the eggs/install directory.