Version of libgphoto installed on system

[mgineer85]

Hey, it seems gp.gp_library_version(gp.GP_VERSION_VERBOSE)} always returns the version of the installed library in the system.

If it is installed with --prefer-binaries the more recent included version is used, but the function still returns the system version information.

Is there any way to check if the precompiled version coming along with the latest python-gphoto2 is used?

[jim-easterbrook]

I didn't know about --prefer-binaries, it sounds as if it leaves scope for doing a source installation. I use --only-binary :all: to ensure a binary installation.

First find out where python-gphoto2 is installed:

$ pip show gphoto2
Name: gphoto2
Version: 2.5.1
Summary: Python interface to libgphoto2
Home-page: https://github.com/jim-easterbrook/python-gphoto2
Author: Jim Easterbrook
Author-email: jim@jim-easterbrook.me.uk
License: GNU LGPL
Location: /home/jim/.local/lib/python3.6/site-packages
Requires: 
Required-by: 

Then check you have a libgphoto2 directory installed with python-gphoto2:

$ ls -l /home/jim/.local/lib/python3.6/site-packages/gphoto2/libgphoto2/
total 636
drwxr-xr-x  2 jim users   4096 Nov  7  2023 camlibs
drwxr-xr-x  2 jim users   4096 Nov  7  2023 iolibs
-rwxr-xr-x  1 jim users 138872 Nov  7  2023 libgphoto2_port.so.12
-rwxr-xr-x  1 jim users 495392 Nov  7  2023 libgphoto2.so.6
drwxr-xr-x 24 jim users   4096 Nov  7  2023 locale
drwxr-xr-x  2 jim users   4096 Nov  7  2023 vusb

If this is all as it should be, then use ldd to ensure python-gphoto2 is using the correct libraries:

$ ldd /home/jim/.local/lib/python3.6/site-packages/gphoto2/_version.cpython-36m-x86_64-linux-gnu.so
        linux-vdso.so.1 (0x00007ffc6a88c000)
        libgphoto2.so.6 => /home/jim/.local/lib/python3.6/site-packages/gphoto2/libgphoto2/libgphoto2.so.6 (0x00007f7ed1102000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f7ed0f88000)
        libgphoto2_port.so.12 => /home/jim/.local/lib/python3.6/site-packages/gphoto2/libgphoto2/libgphoto2_port.so.12 (0x00007f7ed0f7b000)
        libpython3.6m.so.1.0 => /usr/lib64/libpython3.6m.so.1.0 (0x00007f7ed0c9b000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7ed0c75000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f7ed0a7e000)
        libltdl.so.7 => /usr/lib64/libltdl.so.7 (0x00007f7ed0a73000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f7ed0a6e000)
        libexif.so.12 => /usr/lib64/libexif.so.12 (0x00007f7ed0800000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7ed1192000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00007f7ed0a68000)

[jim-easterbrook]

Yes, I use it and have included MacOS arm64 binaries since python-gphoto2 version 2.5.1, released in October 2024.

[mgineer85]

So could Linux arm64 now also be added?

[jim-easterbrook]

Yes, it probably could. I didn't know there was much demand for it. I'm currently building and uploading to PyPI 22 different wheels. On a modern computer installing from source with pip is pretty quick, the only problem is getting inexperienced users to install the -dev package with their OS package manager.

[jim-easterbrook]

I've uploaded some arm64 wheels to PyPI.