libgpiod 2.x install over 1.6.3

[francescoangelini]

Hello everyone,

I'm a HW/FW developer and I'm trying to use the gpiolibd libraries in a Python project that should run on a SBC (Radxa Cubie a5e, based on an Allwinner A527 main processor). At the moment, on this board is installed Debian 12 "Bookworm" and I created a venv in which I installed gpiod 2.3.0, but I'm getting strange errors even if I try to run the basic examples (i.e. also on Chip.get_info() function that should be working). So i checked the libgpiod version installed on my system and I found

gpiod 1.6.3-1+b3
libgpiod-dev:arm64 1.6.3-1+b3
libgpiod2:arm64 1.6.3-1+b3
python3-libgpiod:arm64 1.6.3-1+b3

I realized that my problem was (probably) related to this version mismatch (I'm trying to use a 2.x Python module but I have the 1.x version of the libgpiod). I tried to upgrade all these libraries to the latest version but no update seems to be available via standard ways (apt update, apt upgrade etc...) so I followed the instructions here:

https://libgpiod.readthedocs.io/en/latest/building.html

Build completes apparently without errors and, as I can read from log-file, the updated libgpiod was created in /usr/local/lib (I can see libgpiod.a, libgpios.la and some other files). But it seems to me that my system still uses the old libraries version: a dpkg -l command outputs exactly the previous versions. Can you help me to understand how should I "activate" the new version? Is there a specific way to remove the 1.6.3 before building the new one?

Thank you very much and sorry if my question may be trivial.
Francesco

[brgl]

What are the errors you're seeing in python exactly? The gpiod package from pypi bundles the matching .c sources and links them statically to the C extension module. IOW, the python package should work no matter what version (if any) of libgpiod you have installed in your system.

[francescoangelini]

Thank you for your answer. I noticed that my venv was trying to use the freshly compiled library available in /usr/local/lib/ instead of the gpiod module installed with pip into the venv folder but. I don't know why; I simply removed (apt remove) gpiod from the system and now the virtual env is correctly referring to its gpiod module and now evertyhing seems to work correctly.