[Development] Removing libudev dependency from binary packages?

Thiago Macieira thiago.macieira at intel.com
Thu Oct 24 13:23:12 CEST 2013

On quinta-feira, 24 de outubro de 2013 10:56:00, Koehne Kai wrote:
> > -----Original Message-----
> > From: development-bounces+kai.koehne=digia.com at qt-project.org
> > [mailto:development-bounces+kai.koehne=digia.com at qt-project.org] On
> > Behalf Of Laszlo Papp
> > Sent: Wednesday, October 23, 2013 5:45 PM
> > To: Sune Vuorela
> > Cc: development at qt-project.org
> > Subject: Re: [Development] Removing libudev dependency from binary
> > packages?
> > 
> > [...]
> > We agreed with Kai on IRC, when discussing this topic, that we would ask
> > the udev mailing list for an authoritative reply unless someone can
> > confirm that on this list just as well.
> Actually I just checked the sources, and libudev is licensed under LGPL 2.1
> or newer. That means AFAIK that we can link against it statically in the
> open source version of Qt, but not in the enterprise one ... Not sure
> whether it's worth a try then? Just for practical purposes I think the
> opensource and enterprise binaries shouldn't deviate too much.

We can link to it in the enterprise version. It's only required that 
recipients of the libQt5SerialPort.so.5 library be able to relink with a 
different libudev. Since the source code for QtSerialPort is open, the 
requirement is taken care of.

The problem does not apply to static libraries in the first place, either.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131024/4de40e84/attachment.sig>

More information about the Development mailing list