Re: [Development] Backporting the "stop unloading plugins" change to 5.6

2016-10-14 Thread Liang Jian
I don't care custom plugin, What I care is the plugins loaded by qt itself, such as qpa plugin, images format plugins ..., These plugins are needed for all qt programs, we can't avoid the leaks caused by not unloading these plugins if my understanding to this issue is right (Maybe you don't

Re: [Development] QtBase WIP branch request

2016-10-14 Thread Morten Sorvig
> On 12 Oct 2016, at 22:57, James Turner wrote: > > >> On 7 Oct 2016, at 02:32, Morten Sorvig wrote: >> >> >> What is actually in development? The scope is outlined in QTBUG-49827 and >> includes >> - Improving expose event handling >> -

Re: [Development] Multiple Qt branches on Coverity Scan

2016-10-14 Thread Oswald Buddenhagen
On Thu, Oct 13, 2016 at 02:43:13PM +0100, Giuseppe D'Angelo wrote: > On 13/10/16 14:35, Marc Mutz wrote: > > Will the -lts version start out with its own CIDs or will identical issues > > have the same CIDs in both projects? If they're different, we'll have a > > mess. > > The idea was to share

Re: [Development] Qt build without Virtual Keyboard

2016-10-14 Thread Mitch Curtis
Qt Quick has always been mandatory for Qt Virtual Keyboard, as the keyboard itself is a Qt Quick Item. I don’t know where or how you got the sources, but you can just remove the qtvirtualkeyboard directory to avoid it being built. If you’re using Git, you can use –module-subset when

[Development] Qt build without Virtual Keyboard

2016-10-14 Thread Alexander Nassian
Hi, We are trying to build 5.7 on Linux without OpenGL support (so no QtQuick either) and are facing a build error in qtvirtualkeyboard „Module quick not found“. Is QtQuick now mandatory, or is this a known bug? And why is the virtual keyboard building at all when choosing L-GPL? That’s not

Re: [Development] Backporting the "stop unloading plugins" change to 5.6

2016-10-14 Thread Thiago Macieira
Em sexta-feira, 14 de outubro de 2016, às 11:07:34 PDT, Thiago Macieira escreveu: > What do you prefer? > > 1) leak > 2) crash and leak > > Either way, the dlclose() call will not happen. > > Note that this has nothing to do with freeing memory. Only the dlclose(). Actually, there's no

Re: [Development] Backporting the "stop unloading plugins" change to 5.6

2016-10-14 Thread Thiago Macieira
Em sexta-feira, 14 de outubro de 2016, às 07:10:00 PDT, Thiago Macieira escreveu: > We are talking in this change about QFactoryLoader, which is a Qt API and > which is ALWAYS used until program exit. I meant internal Qt API. -- Thiago Macieira - thiago.macieira (AT) intel.com Software

Re: [Development] Backporting the "stop unloading plugins" change to 5.6

2016-10-14 Thread Thiago Macieira
Em sexta-feira, 14 de outubro de 2016, às 16:08:27 PDT, Liang Jian escreveu: > I don't care custom plugin, What I care is the plugins loaded by qt > itself, such as qpa plugin, images format plugins ..., These plugins are > needed for all qt programs, we can't avoid the leaks caused by not >