Re: Making camlibs and iolibs relocatable
Marcus Meissner <[email protected]>
| Newsgroups | gmane.comp.multimedia.gphoto.devel |
|---|---|
| Message-ID | <YVQfPjBwqarwBUzd@jet> |
Hi, On Tue, Sep 28, 2021 at 01:41:05PM +0100, Jim Easterbrook wrote: > I've recently added "binary wheels" to my Python interface to libgphoto2. > These include pre-built copies of libgphoto2 v2.5.27 and are much quicker > and easier for a user to install as they don't have to install libgphoto2 > (development headers) and compile the interface files. > > One problem I encountered was the hard coding of absolute paths into where > libgphoto2 looks for its camlibs and iolibs. Luckily the CAMLIBS and IOLIBS > environment variables solve that problem, but I'd rather they weren't > labelled as for "broken/test installations". From my point of view this is a valid usage scenario. The libgphoto2 toplevel configure can set --with-camlibdir=PATH already to set the default, the libgphoto2_port configure would need --with-iolibdir=PATH to set the default, But you can use it with CAMLIBS and IOLIBS already I would say. Ciao, Marcus