Re: [Development] Breaking up QtPlatformSupport

2012-03-15 Thread Oswald Buddenhagen
On Wed, Mar 14, 2012 at 11:07:56AM +1000, ext Lincoln Ramsay wrote: > On 03/12/2012 11:56 PM, ext Thiago Macieira wrote: > > qmake does not add a dependency on the .a file, so the other target doesn't > > get > > relinked. > > Qtopia had a large number of .a files and this hit us hard so we devis

Re: [Development] Breaking up QtPlatformSupport

2012-03-13 Thread Lincoln Ramsay
On 03/12/2012 11:56 PM, ext Thiago Macieira wrote: > qmake does not add a dependency on the .a file, so the other target doesn't > get > relinked. Qtopia had a large number of .a files and this hit us hard so we devised a workaround. # A function to create explicit dependencies in a Makefile de

Re: [Development] Breaking up QtPlatformSupport

2012-03-13 Thread Lincoln Ramsay
On 03/12/2012 08:24 PM, ext Thiago Macieira wrote: > Adding -l flags does not work because of the way qmake works. When you write: > > QT += platformsupport-private > LIBS += -lfoo > > or when you write: > > LIBS += -lfoo > QT += platformsupport-private > > This will always

Re: [Development] Breaking up QtPlatformSupport

2012-03-13 Thread Jørgen Lind
> > We can talk about making it into a nicer API in a future version of Qt, but > > for Qt 5, we should keep it as it is. > > Understood. I'm not against out-of-qtbase plugins. I am against forcing them > to use private and changing API like QtPlatformSupport. Ah, now I see. This is where the mi

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread Thiago Macieira
On segunda-feira, 12 de março de 2012 15.28.01, gunnar.sle...@nokia.com wrote: > > Building plugins outside of QtBase will continue to be permitted, provided > > they don't use QtPlatformSupport. That library is just convenience for us. > > There is absolutely no public API there. If there are thin

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread gunnar.sletta
On Mar 12, 2012, at 11:24 AM, ext Thiago Macieira wrote: > On segunda-feira, 12 de março de 2012 09.31.11, Jørgen Lind wrote: >>> This will be hard to do with qmake, so the easier way out is to remove the >>> .a altogether and use .pri files only. That requires moving the Wayland >>> platform plu

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread Thiago Macieira
On segunda-feira, 12 de março de 2012 15.23.33, Simon Hausmann wrote: > The thing about platformsupport is that it is not a convenience library, it > is at this moment absolutely essential for writing a real world platform > plugin That statement does not match the fact that it's a static lib with

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread Simon Hausmann
On Monday, March 12, 2012 02:56:02 PM ext Thiago Macieira wrote: > On segunda-feira, 12 de março de 2012 11.50.17, morten.sor...@nokia.com wrote: > > On Mar 12, 2012, at 11:24 AM, ext Thiago Macieira wrote: > > > Anyway, either way this library will be gone. The most likely solution > > > is > > >

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread Thiago Macieira
On segunda-feira, 12 de março de 2012 11.50.17, morten.sor...@nokia.com wrote: > On Mar 12, 2012, at 11:24 AM, ext Thiago Macieira wrote: > > Anyway, either way this library will be gone. The most likely solution is > > that we will break it up into many smaller .a libraries. > > One other thing I'

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread morten.sorvig
On Mar 12, 2012, at 11:24 AM, ext Thiago Macieira wrote: Anyway, either way this library will be gone. The most likely solution is that we will break it up into many smaller .a libraries. One other thing I've noticed is that linking agains an .a library breaks incremental builds: touch qfontengin

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread Thiago Macieira
On segunda-feira, 12 de março de 2012 09.31.11, Jørgen Lind wrote: > > This will be hard to do with qmake, so the easier way out is to remove the > > .a altogether and use .pri files only. That requires moving the Wayland > > platform plugin back into qtbase. > > Pretty please with sugar on top, do

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread lars.knoll
On 3/12/12 9:31 AM, "ext Jørgen Lind" wrote: >> This will be hard to do with qmake, so the easier way out is to remove >>the .a >> altogether and use .pri files only. That requires moving the Wayland >>platform >> plugin back into qtbase. >> >Pretty please with sugar on top, do NOT do this. I

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread Jørgen Lind
> This will be hard to do with qmake, so the easier way out is to remove the .a > altogether and use .pri files only. That requires moving the Wayland platform > plugin back into qtbase. > Pretty please with sugar on top, do NOT do this. I understand that you only see the "Wayland" side of thing

Re: [Development] Breaking up QtPlatformSupport

2012-03-12 Thread Oswald Buddenhagen
On Sun, Mar 11, 2012 at 05:59:16PM +0100, ext Thiago Macieira wrote: > This will be hard to do with qmake, so the easier way out is to remove the .a > altogether and use .pri files only. > well, there is also the option to split it into multiple .a files which have their own dependency lists. the

[Development] Breaking up QtPlatformSupport

2012-03-11 Thread Thiago Macieira
Hello After the alpha, I'd like to dismantle the QtPlatformSupport library and fix it properly. It should be broken up into smaller libraries or back into .pri files to be included. I know this is not going to be a popular change, but please bear with me on the explanation: Due to a mistake in t