Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-25 Thread Thiago Macieira
On Tuesday 25 November 2014 13:45:31 Lisandro Damián Nicanor Pérez Meyer wrote: > > Actually, the reason that you *need* to pass -system-xxx on distributions > > is to make sure that Qt will use the system lib. In other words, if you > > forget your BuildRequires: tag, the build for Qt should fail

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-25 Thread Lisandro Damián Nicanor Pérez Meyer
On Monday 24 November 2014 19:58:16 Thiago Macieira wrote: > On Monday 24 November 2014 19:35:33 Thiago Macieira wrote: > > > default configure options. At the moment, we have to pass an insane > > > amount > > > of -system-libfoo and -linked-libbar switches. > > > > Agreed. > > > > I'm already c

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-24 Thread Thiago Macieira
On Monday 24 November 2014 19:35:33 Thiago Macieira wrote: > > default configure options. At the moment, we have to pass an insane amount > > of -system-libfoo and -linked-libbar switches. > > Agreed. > > I'm already changing the D-Bus switch to default to linked unless you're on > OS X. You cou

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-24 Thread Thiago Macieira
On Tuesday 25 November 2014 03:05:03 Kevin Kofler wrote: > Thiago Macieira wrote: > > Packagers can and should force the linking. This is about the > > distribution- agnostic binaries we produce and are available from > > qt-project.org. > > But my point is that the defaults in the configure scrip

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-24 Thread Kevin Kofler
Thiago Macieira wrote: > Packagers can and should force the linking. This is about the > distribution- agnostic binaries we produce and are available from > qt-project.org. But my point is that the defaults in the configure script should be friendlier to distribution packagers. For the binaries y

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-23 Thread Thiago Macieira
On Sunday 23 November 2014 19:55:53 Allan Sandfeld Jensen wrote: > The difference is with dlopen we can support more than one major version > with the same binary making it possible to upgrade udev for instance > without having to upgrade all of Qt at the same time. In this case it > doesn't matter

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-23 Thread Allan Sandfeld Jensen
On Sunday 23 November 2014, Thiago Macieira wrote: > On Sunday 23 November 2014 11:53:46 Allan Sandfeld Jensen wrote: > > QtWebKit and QtWebEngine does not support linking directly to libudev, > > but they will only try to dlopen libudev.so.1 or libudev.so.0 in that > > order, and being major versi

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-23 Thread Thiago Macieira
On Sunday 23 November 2014 11:53:46 Allan Sandfeld Jensen wrote: > QtWebKit and QtWebEngine does not support linking directly to libudev, but > they will only try to dlopen libudev.so.1 or libudev.so.0 in that order, and > being major version if a libudev.so.2 is made it can co-exists with > libude

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-23 Thread Allan Sandfeld Jensen
On Sunday 23 November 2014, Thiago Macieira wrote: > On Sunday 23 November 2014 08:22:28 Kevin Kofler wrote: > > Sorry, but as distribution packagers, we really no NOT like dlopened > > > libraries, for several reasons: > Packagers can and should force the linking. This is about the distribution-

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-23 Thread Thiago Macieira
On Sunday 23 November 2014 08:22:28 Kevin Kofler wrote: > Sorry, but as distribution packagers, we really no NOT like dlopened > libraries, for several reasons: Packagers can and should force the linking. This is about the distribution- agnostic binaries we produce and are available from qt-projec

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-22 Thread Kevin Kofler
Pau Garcia i Quiles wrote: > Today I installed an snapshot of Qt 5.4.0 for Linux x86 on my Kubuntu > 14.04 and found a problem: it links to libudev.so.0, while Ubuntu 14.04 > provides libudev.so.1. > > I was wondering if it would be a good idea for Qt to move from explicit > linking to dlopen/dlsy

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-21 Thread Koehne Kai
>There's dlopen code in QtSerialPort. Something went wrong with the build or >the source code since that was introduced... > >It's a regression, we had that fixed. Indeed. I created https://bugreports.qt-project.org/browse/QTBUG-42805 Regards Kai ___

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-19 Thread Thiago Macieira
On Wednesday 19 November 2014 18:12:20 Pau Garcia i Quiles wrote: > > What library is that? I thought we did dlopen libudev... > > libQt5SerialPort There's dlopen code in QtSerialPort. Something went wrong with the build or the source code since that was introduced... It's a regression, we had

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-19 Thread Pau Garcia i Quiles
On Wed, Nov 19, 2014 at 5:59 PM, Thiago Macieira wrote: > On Wednesday 19 November 2014 11:38:41 Pau Garcia i Quiles wrote: > > Today I installed an snapshot of Qt 5.4.0 for Linux x86 on my Kubuntu > 14.04 > > and found a problem: it links to libudev.so.0, while Ubuntu 14.04 > provides > > libude

Re: [Development] Explicit linking vs dlopen/dlsym

2014-11-19 Thread Thiago Macieira
On Wednesday 19 November 2014 11:38:41 Pau Garcia i Quiles wrote: > Today I installed an snapshot of Qt 5.4.0 for Linux x86 on my Kubuntu 14.04 > and found a problem: it links to libudev.so.0, while Ubuntu 14.04 provides > libudev.so.1. What library is that? I thought we did dlopen libudev... --

[Development] Explicit linking vs dlopen/dlsym

2014-11-19 Thread Pau Garcia i Quiles
Hello, Today I installed an snapshot of Qt 5.4.0 for Linux x86 on my Kubuntu 14.04 and found a problem: it links to libudev.so.0, while Ubuntu 14.04 provides libudev.so.1. I was wondering if it would be a good idea for Qt to move from explicit linking to dlopen/dlsym. That would help supporting d