From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: Re: doc libdir and C code modules
Date: Mon, 06 Feb 2006 10:31:09 +0100 [thread overview]
Message-ID: <87lkworfz6.fsf@laas.fr> (raw)
In-Reply-To: <87zml86k72.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 04 Feb 2006 11:28:49 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> I added the words below to the manual as the last subsection in
> "Dynamic Libraries", to encourage packages to use libdir. I don't
> want to re-open the can of worms about versioning and stuff, this is
> intended just to describe the present situation.
Cool!
> When loaded with `(use-modules (foo bar))', the `load-extension'
> call looks for the `foobar-c-code.so' object file in the standard
> system locations, such as `/usr/lib' or `/usr/local/lib'.
Shouldn't there be a note saying that the actual shared library name
will follow the system's naming convention, be it `libfoobar-c-code.so',
`libfoobar-c-code.sl', `foobar-c-code.dll', etc.? Perhaps with a link
to `(libtool.info.gz)Libltdl interface' mentioning `lt_dlopenext ()'?
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-06 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 0:28 doc libdir and C code modules Kevin Ryde
2006-02-04 15:38 ` Neil Jerram
2006-02-05 23:21 ` Kevin Ryde
2006-02-07 0:03 ` Kevin Ryde
2006-02-09 9:49 ` Neil Jerram
2006-02-14 19:47 ` Greg Troxel
2006-02-06 9:31 ` Ludovic Courtès [this message]
2006-02-07 0:11 ` Kevin Ryde
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=87lkworfz6.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
/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).