[Development] Removing libudev dependency from binary packages?
sirspudd at gmail.com
Tue Oct 22 07:45:52 CEST 2013
I still don't follow the need for remove udev support:
There udev is as far back as Lucid. Where is it not present, exactly?
When you remove it from webkit, you remove joypad hotplug detection.
When you remove it from Qt, you remove the only generalized mechanism
for hot plugging USB devices on Linux systems. Are we doing this in
order to facilitate the same package being used from Ubuntu 13.10
through to Slackware 1.0?
On Mon, Oct 21, 2013 at 3:18 PM, Thiago Macieira
<thiago.macieira at intel.com> wrote:
> On segunda-feira, 21 de outubro de 2013 23:07:25, Thiago Macieira wrote:
>> - libqgtk2: fix, it doesn't need libudev
>> The fix for libqgtk2 can probably be:
>> linux: QMAKE_LFLAGS += -Wl,--as-needed
> Can anyone check if the other plugins linking to QtPlatformSupport also have
> the udev dependency?
> The fix for platforms other than Linux is to split QtPlatformSupport into
> multiple libraries, one per purpose. At the very least, one library per
> *external* dependency.
> Or simply remove the library and let the few files that each plugin needs be
> compiled multiple times (this would also require moving the wayland plugin
> back into qtbase). Not a solution for 5.2, I guess.
> We may want to investigate turning on --as-needed everywhere. I've been
> building Qt with that flag for years. However, it might introduce problems
> related to building a new version of Qt when an older version is already
> present and installed, even though we are apparently already doing what we
> need to do (pass --rpath-link).
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel Open Source Technology Center
> Development mailing list
> Development at qt-project.org
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
Cave canem, te necet lingendo
More information about the Development