Re: What replaces scm_register_module_xxx (Doc update?)

[Rob Browning]

"Dale P. Smith" <address@hidden> writes:

> The new method is to use a .scm file that defines the module,
> dynamically loads the compiled code, and then exports whatever you
> need.

Right.

  (define-module (foo bar))
  (load-extension "libguile-foo-bar-v-1" "init_guile_foo_bar-v-1")
  (export foo-1)
  (export foo-2)
  (export bar-1)
  ...

Putting the library major version number into the shared lib name
isn't required by the code, but it's highly recommended for now.  This
will keep you from having .la name conflicts and from not being able
to know which version of your lib will get loaded if/when you need to
release libguile-foo-bar-v-2.  i.e. libguile-foo-bar-v-2.so.2.0.0.

This may just be a temporary practice.  It depends on what we figure
out during the 1.7 series regarding dynamic linking.

Hope this helps.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD