From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-user@gnu.org, Sebastian Tennant <sebyte@smolny.plus.com>
Subject: Re: Debian guile-1.8 and ttn guile-pg
Date: Tue, 27 May 2008 15:04:27 +0200 [thread overview]
Message-ID: <87prr7oq3o.fsf@ambire.localdomain> (raw)
In-Reply-To: <rmiiqwz5303.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "Tue, 27 May 2008 08:46:04 -0400")
⎛⎞ Greg Troxel <gdt@ir.bbn.com>
⎝⎠ Tue, 27 May 2008 08:46:04 -0400
> (define-module (database postgres))
> (load-extension "/ABS/PATH/TO/libpostgres.so.0.0.0"
> "scm_init_database_postgres_module")
(I presume you are either consing up the path or substituting
it with autoconf.)
Yes, either way or even both (whatever will work).
My understanding is slightly fuzzy, but I think that defines
the guile-pg symbols in the (database postgres) module, but
will not necessarily export them.
OK.
The 1.4-style module loading seems to do the equivalent of
define-public.
Yes.
I did make guile-pg work with a scheme load file as you write
above once, and I also had a number of export statements.
So in addition to the above, there needs to be `define-public'
for each proc? Can that be phrased as an `#:export' clause in
the `define-module' form (prior to the `load-extension' call)?
thi
next prev parent reply other threads:[~2008-05-27 13:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 16:34 Debian guile-1.8 and ttn guile-pg Sebastian Tennant
[not found] ` <20080329135511.68737330@altosw.be>
2008-03-30 12:11 ` Sebastian Tennant
2008-03-30 15:34 ` David Pirotte
2008-03-30 16:17 ` Sebastian Tennant
2008-03-31 19:04 ` Greg Troxel
2008-05-25 18:08 ` Thien-Thi Nguyen
2008-05-27 12:46 ` Greg Troxel
2008-05-27 13:04 ` Thien-Thi Nguyen [this message]
2008-05-27 16:17 ` David Pirotte
2008-05-28 12:29 ` Thien-Thi Nguyen
2008-05-28 19:18 ` Greg Troxel
-- strict thread matches above, loose matches on Subject: below --
2008-03-31 20:18 dsmich
2008-03-31 20:38 ` Sebastian Tennant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prr7oq3o.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=gdt@ir.bbn.com \
--cc=guile-user@gnu.org \
--cc=sebyte@smolny.plus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).