20.1 A Module Loading Subsystem

back: a complex gnu autotools project
forward: initialising the module loader
 
fastback: a complex gnu autotools project
up: a complex gnu autotools project
fastforward: a loadable module
top: autoconf, automake, and libtool
contents: table of contents
index: index
about: about this document

As you saw in 18. Using GNU libltdl , I need to put an invocation of the macro `AC_LIBTOOL_DLOPEN' just before `AC_PROG_LIBTOOL' , in the file `configure.in' . But, as well as being able to use libtoolize --ltdl , which adds libltdl in a subdirectory with its own subconfigure, you can also manually copy just the ltdl source files into your project(45), and use AC_LIB_LTDL in your existing `configure.in' . At the time of writing, this is still a very new and (as yet) undocumented feature, with a few kinks that need to be ironed out. In any case you probably shouldn't use this method to add `ltdl.lo' to a C++ library, since `ltdl.c' is written in C. If you do want to use libltdl with a C++ library, things will work much better if you build it in a subdirectory generated with libtoolize --ltdl .

For this project, lets:

 
 $ cp /usr/share/libtool/libltdl/ltdl.[ch] sic/ 

The Sic module loader is probably as complicated as any you will ever need to write, since it must support two kinds of modules: modules which contain additional built-in commands for the interpreter; and modules which extend the Sic syntax table. A single module can also provide both syntax extensions and additional built-in commands.


This document was generated by Gary V. Vaughan on May, 24 2001 using texi2html


GNU Autoconf, Automake and Libtool
GNU Autoconf, Automake, and Libtool
ISBN: 1578701902
EAN: 2147483647
Year: 2002
Pages: 290

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net