GNU Info

(g-wrap.info)Accessing the wrapped API from the target language

---

Next: Coping With Old Guile Versions Prev: Generating the glue code Up: Generating and using the glue code

---

Enter node , (file) or (file)node

Interfacing the library and glue code to the interpreter
========================================================

The methods for integrating support for a g-wrapped API into various
target languages vary, so these will have to be dealt with on a case by
case basis.

At the moment only the primitive tool g-wrap-config is documented here.
It can provide the information needed for linking g-wrap into a target
executable for each of the languages g-wrap supports (presuming linking
even makes sense).  Consider this entire area one that's still under
development, so expect the details to change.

Right now code can be statically linked to the interpreters, or loaded
dynamically as shared libraries.  To find out which libraries are
required use the g-wrap-config command.  It may be invoked as follows:

`g-wrap-config --version'
     show version information

`g-wrap-config --help'
     show this message

`g-wrap-config --c-compile-args LANGUAGE'
     C compile args for LANGUAGE

`g-wrap-config --c-link-args LANGUAGE'
     C link args for LANGUAGE

`g-wrap-config --c-static-link-args LANGUAGE'
     C static link args for LANGUAGE

where (at the moment) LANGUAGE may be either rscheme or guile.  Examples
for each of the target languages will be available in the distribution.

This infrastructure is probably not sufficient in the long run if g-wrap
is extended to support many languages, but it's a start, and it handles
the current scope fairly well.