Re: How CLSQL finds and loads foreign libraries

On Tue, 19 Apr 2005 14:08:45 -0400, MichaelL-mTnyLpuDpHxWk0Htik3J/[email protected] wrote:

> Actually, I thought the "real" solution was to remove the absolute
> paths and simply let Windows do the search! I think that's what I
> did in my copy. Obviously that means that the libraries have to be
> on the path.  Perhaps there could also be a way to supply a hard
> coded path, but I think that should be the "alternate" rather than
> default approach.

Hmm, I was under the (wrong, as it turns out) impression that this
won't work.  I thought that if absolute paths weren't provided there'd
be some pathname merging within the Lisp image unrelated to foreign
libraries.

But I re-read the corresponding documentation entries for LispWorks
and AllegroCL and it looks as if they both load shared libraries as
usual on Windows as well as on other platforms.

So, in that case I fully agree with you - I think absolute paths
should be removed from CLSQL or made optional.  I'd be willing to
provide a patch if Kevin agrees.

Cheers,
Edi.