libtool/tests/mdemo
Ralf Wildenhues 85953e3b87 Add .gitignore files.
* .gitignore, doc/.gitignore, libltdl/.gitignore,
libltdl/config/.gitignore, libltdl/m4/.gitignore,
tests/.gitignore, tests/cdemo/.gitignore,
tests/demo/.gitignore, tests/depdemo/.gitignore,
tests/f77demo/.gitignore, tests/fcdemo/.gitignore,
tests/mdemo/.gitignore, tests/mdemo2/.gitignore,
tests/pdemo/.gitignore, tests/tagdemo/.gitignore:
New files.

Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
2008-04-16 21:31:03 +02:00
..
.cvsignore
.gitignore Add .gitignore files. 2008-04-16 21:31:03 +02:00
configure.ac * HACKING (Licensing Rules): Explain the various license texts 2007-03-25 12:12:44 +00:00
foo1.c * HACKING (Licensing Rules): Explain the various license texts 2007-03-25 12:12:44 +00:00
foo2.c * HACKING (Licensing Rules): Explain the various license texts 2007-03-25 12:12:44 +00:00
foo.h * HACKING (Licensing Rules): Explain the various license texts 2007-03-25 12:12:44 +00:00
main.c * tests/mdemo-exec.test: Also try absolute library names. 2007-07-24 05:10:03 +00:00
Makefile.am * tests/mdemo/Makefile.am (@LIBLTDL@): Update outdated 2008-02-11 21:51:43 +00:00
mlib.c * HACKING (Licensing Rules): Explain the various license texts 2007-03-25 12:12:44 +00:00
README
sub.c * HACKING (Licensing Rules): Explain the various license texts 2007-03-25 12:12:44 +00:00

This is mdemo, an example package that uses GNU libtool with an
Automake-generated environment to build two simple modules and 
a program.

It demonstrates how to build both dynamic and static libraries
that can be dlopened. mdemo uses libtool's portable dlopen
wrapper called "libltdl". 
All exported symbols are prefixed with "libname_LTX_" to avoid
symbols conflicts, especially when linking statically.
libltdl will automatically cut the prefix off to get the real name.

Note that on Windows, for the purposes of illustrating ltdl, the
libraries *are* built as dll's, but do not have the __declspec
machinery to make them suitable for loading at link time.  This is
only for clarity inside this example, look at the example in ../demo
to see how the __declspec macros should be set up.