[Top][All Lists]

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

Search path for C libraries

From: Ludovic Courtès
Subject: Search path for C libraries
Date: Tue, 18 Oct 2005 10:23:34 +0200
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)


Greg Troxel <address@hidden> writes:

> Perhaps dynamic-link should look in guilelibdir _only_ if an absolute
> path is not given, or a primitive that does this.  One important
> feature is that inclusion, dynamic link, etc. should be able to ensure
> it gets exactly what was searched for and tested at configure time.

Right.  This is one of the concerns that was raised by Vorfeed Canal
earlier I think.

Maybe the right way to do this would in fact to have module developers
generate the `dynamic-link' code at configure-time (using Autoconf
substitution) in order to hard-wire the library path.  Unfortunately,
this isn't very elegant and it precludes, for instance, running the
module's test suite before installing it (because `dynamic-link' would
either fail or load the wrong library).

This is why extending Neil's mechanism to C libraries might help here.


reply via email to

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