True, but to make this work in 1.8 you just have to write a single .scm
file for the module which loads the shlib and re-exports all the right
symbols. And maybe a little else, but I am pretty sure not much.
Easy for a C programmer no doubt, but not so easy for a lowly scripter
Quoth Greg Troxel [EMAIL PROTECTED]:
but...
To build Guile-PG you need to have installed both the PostgreSQL
frontend library libpq, and a version of Guile that can load binary
module (a b c) from file a/b/c.so or a/b/c/libc.la under `%load-path'.
I believe the last bit means
Sebastian Tennant [EMAIL PROTECTED] writes:
Quoth Greg Troxel [EMAIL PROTECTED]:
but...
To build Guile-PG you need to have installed both the PostgreSQL
frontend library libpq, and a version of Guile that can load binary
module (a b c) from file a/b/c.so or a/b/c/libc.la under
Clinton Ebadi [EMAIL PROTECTED] wrote:
(define-module (pg whatever)
#:export (guile-pg symbols ...))
(load-extension libwhateverpg guile_pg_init)
Is roughly what you need. Assuming that there is an init function in
guile-pg that creates all of bindings for the library
