Re: Making camlibs and iolibs relocatable

On 13/10/2021 13:17, Hans Ulrich Niedermann wrote:
> 
> If it helps you in any way, we now (i.e. in 2.5.27.1 in git since commit
> 94d9912e from 2021-10-12) a way to build libgphoto2 and libgphoto2_port
> such that the default location it looks for camlibs and iolibs can be
> set at configure time:
> 
>       configure \
>           camlibdir=/where/to/install/the/camlibs \
>           DEFAULT_CAMLIBS=/where/to/find/the/camlibs \
>           iolibdir=/where/to/install/the/iolibs \
>           DEFAULT_IOLIBS=/where/to/find/the/iolibs
> 
> The defaults should be sane:
> 
>    * If camlibdir= is not set at configure time, use a default location
>      based on ${libdir} to find out where to install the camlibs.
> 
>    * If DEFAULT_CAMLIBS is not set at configure time, use the value of
>      ${camlibdir} to find out where to look for the camlibs.
> 
>    * Analogous behaviour for iolibs.

I think I tried one of those earlier, but discovered it has to be an 
absolute path. The Python interface can legitimately be installed in one 
of several different places, so a relative path is needed.

> What we do not have at this time is a way to change the driver lookup
> location at runtime with an API function call. That has been proposed
> in https://github.com/gphoto/libgphoto2/pull/534 but I have
> not thought much about it so far. I certainly do not want to hurry
> changes to the public API and ABI as those tend to stick for a long
> time.

I agree with you. I've got a working solution now so I'm happy if there 
are no further changes.

-- 
Jim Easterbrook                 <http://www.jim-easterbrook.me.uk/>