Re: [softwerk-dev] new release, plus "manual": SUCCESS!

[Paul Barton-D. <pb...@op...>]

>Isn't ldconfig supposed to take care of this? I mean like add the
>path /usr/local/lib or wherever the libs are installed into the
>/etc/ld.so.conf fi le (thats where it is on my system), then re-run
>ldconfig each time new libraries are installed. I guess setting
>LD_LIBRARY_PATH might make sense from within "configure", but it
>can't control that variable after it exits. Perhaps I'm
>mis-understanding the problem.

ldconfig controls system-wide libraries. because so many people didn't
like or had problems installing the libraries system wide, my programs
now come in tarballs that do a local install of the libraries. it
would be absurd to go around adding appl-specific directories to
ldconfig (i think so, anyway).

no, LD_LIBRARY_PATH isn't set after configure has finished, but when
using a locally installed set of libraries, we use the -rpath option
of ld(1) to encode the library location into the executable.

if you *do* do a system wide install of the libraries, then sure,
ldconfig is the way to handle it. but think of it this way: suppose
you decide to try out ardour as well. are you comfortable overwriting
the libs that you installed for softwerk ? some people will say
yes. some will say no. the current scheme is an attempt to keep them
both happy.

--p