Hello,

Not having libudev results in not having hotplugging and proper device 
discovery for the evdev inputs plugins (and platforms that have the input stuff 
built-in, like eglfs).

This does not mean those plugins will not build or will not work since there is 
a (limited) fallback option that resorts to poking the /dev/input/event devices 
directly. Disabling libudev for desktop builds is acceptable since the evdev 
input support is mostly interesting to embedded targets and those will build 
from source.

Best regards,
Laszlo

________________________________________
From: [email protected] 
[[email protected]] on behalf of Koehne 
Kai [[email protected]]
Sent: Monday, October 21, 2013 4:29 PM
To: [email protected]
Subject: [Development] Removing libudev dependency from binary packages?

Hi there,

In the latest Linux binary packages for 5.2 libQt5Webkit depends on 
libudev.so.0, which isn't installed (or at least not in this version) on a lot 
of distributions:

https://bugreports.qt-project.org/browse/QTBUG-34176

The easiest fix would be to configure Qt with -no-libudev / remove libudev 
headers etc from the build machines. Anyhow, it seems also other Qt modules use 
it if it's available, namely Qt5SerialPort, libqgtk2, libqevdevtableplugin, 
libqevdevtouchplugin.so, libqevdevkeyboardplugin.so, libqevdevmouseplugin.so, 
libqevdevtabletplugin.so .

Can anyone in the knowing clarify how important libudev is for them? What will 
break if we don't link against libudev anywhere (like we did with 5.1.1)?

Regards

Kai

--
   Kai Köhne, Senior Software Engineer - Digia, Qt
   Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
   Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
   Sitz der Gesellschaft: Berlin. USt-IdNr: DE 286 306 868
   Registergericht: Amtsgericht Charlottenburg, HRB 144331 B


_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to