[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: dynamic loading of native code modules]

From: Rob Browning
Subject: Re: address@hidden: dynamic loading of native code modules]
Date: Wed, 24 Apr 2002 15:40:12 -0500
User-agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu)

Andreas Rottmann <address@hidden> writes:

> No, here we talk about extension .so files, don't we? These are
> loaded via libltdl (which has ugly error messages, by the way) and
> thus one can specify the directory to load the lib from.

Current policy is that guile's extension libs are also to be
dynamically linkable directly into applications.  This means that
lt_dlopen is not the only way they're loaded.  Hence the need for
LD_LIBRARY_PATH or similar.

i.e. if you write an app that uses scm_make_u8vector from srfi-4, then
you have to "-l link" against libguilesrfi-srfi4.  For your app to ru,
libguilesrfi-srfi4 will have to either have an appropriate rpath, an
appropriate LD_LIBRARY_PATH, or be in one of the standard locations.

Rob Browning
rlb,, and
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

reply via email to

[Prev in Thread] Current Thread [Next in Thread]