[systemd-devel] Can apps ship their own copy of libudev?

Cristian Rodríguez crrodriguez at opensuse.org
Fri Oct 25 01:49:25 CEST 2013


El 24/10/13 09:15, Koehne Kai escribió:
> Hi,
> 
> First time I post to the list, so please bear with me :) I'm a developer working on Qt. The Qt project just released a  beta of the upcoming version 5.2, and to help people to test it we've been also releasing an installer with binaries for Linux that is supposed to work on a variety of distributions. 
> 
> One of the problems [1] we still have to fix is our libudev.so.0 dependency ... That is, we're building the packages on Ubuntu 11.10 and link against system libudev.so.0 , while some modern distributions are (solely) providing libudev.so.1. For some parts of Qt the libudev dependency is actually not that important , and we can disable it. However, for the QtSerialPort library I've been told libudev is crucial: It uses it to enumerate all available ports.
> 
> So, to overcome this we've been thinking about building & shipping our own copy of libudev (renamed , or statically linked, to avoid clashes) ...

I strongly recommend you not to do this, instead please talk with the
relevant distribution maintainers in order to get adequate binaries
released for each distribution.

I not only believe, but I will bet good money that what your are trying
to do will in the end working really poorly if at all.



-- 
"If debugging is the process of removing bugs, then programming must be
the process of putting them in." - Edsger Dijkstra


More information about the systemd-devel mailing list