What they did was to move registration of meta object content to runtime. They
basically have structs with static variables and they rely on initialization of
these variables at program start-up. It's a lot of macro magic and relies on
things like __LINE__ to create unique tokens.
The info abov
On Tuesday 23 June 2015 10:17:40 Knoll Lars wrote:
> Qt 5.6:
>
> * We make 5.6 a long term supported release
> * We still support C++98 compilers in this release (for the last time),
> i.e. We keep the 5.5 compiler baseline
> * WEC7 will be still supported
> * QNX 6.5 is not supported anymore
> *
On Thursday 25 June 2015 09:04:43 Thiago Macieira wrote:
> On Thursday 25 June 2015 09:37:32 Heikkinen Jani wrote:
> > Hi all,
> >
> >
> > We must freeze the Qt 5.5.0 content now so please don't push any new
> > changes in '5.5.0' branch anymore; those won't be staged. Final qt5.git
> > integrati
On Thursday 25 June 2015 09:37:32 Heikkinen Jani wrote:
> Hi all,
>
>
> We must freeze the Qt 5.5.0 content now so please don't push any new changes
> in '5.5.0' branch anymore; those won't be staged. Final qt5.git integration
> is now ongoing & when it succeed final Qt5.5.0 packages will be crea
On Thursday 25 June 2015 13:55:00 Bubke Marco wrote:
> Wrapping Qt container around standard container is quite a good idea to
> interact with other code. So Qt Container would be standard container +
> COW. One of the complains I hear very often is that Qt is an island and
> sadly in many cases I
On Thursday 25 June 2015 13:18:17 Cristian Adam wrote:
> They've got rid of moc and plan to replace Qt containers with std ones.
If they got rid of moc, then they also got rid of QtDBus, QtScript and QtQml.
That doesn't sound like a "fork of Qt".
Getting rid of moc is waiting for SG7 from the st
Wrapping Qt container around standard container is quite a good idea to
interact with other code. So Qt Container would be standard container + COW.
One of the complains I hear very often is that Qt is an island and sadly in
many cases I must agree. I think we should discuss the integration of t
On Thu, Jun 25, 2015 at 1:04 PM, Knoll Lars
wrote:
>
>
> Well, please tell me where this is such a big problem that we *have to
> have* VS2013 when it comes to our APIs. For our implementation inside Qt,
> we can work with slightly older compilers. It’s not the end of the world
> and our users wo
On 25/06/15 12:43, "Teske Daniel" wrote:
>On Thursday 25 Jun 2015 12:09:54 Knoll Lars wrote:
>> On 25/06/15 11:43, "Teske Daniel" wrote:
>>
>>
>> >> * WEC7 not supported anymore, WEC2013 supported
>> >
>> >So what is the time frame for dropping WEC2013? Because that's the time
>> >Qt
>> >will
On Thursday 25 Jun 2015 12:09:54 Knoll Lars wrote:
> On 25/06/15 11:43, "Teske Daniel" wrote:
>
>
> >> * WEC7 not supported anymore, WEC2013 supported
> >
> >So what is the time frame for dropping WEC2013? Because that's the time
> >Qt
> >will be stuck with MSVC2012.
>
>
> WEC2013 just came o
On 25/06/15 11:43, "Teske Daniel" wrote:
>> * WEC7 not supported anymore, WEC2013 supported
>So what is the time frame for dropping WEC2013? Because that's the time
>Qt
>will be stuck with MSVC2012.
WEC2013 just came out. I’m afraid we’ll be stuck with it for some time.
Cheers,
Lars
_
> * WEC7 not supported anymore, WEC2013 supported
So what is the time frame for dropping WEC2013? Because that's the time Qt
will be stuck with MSVC2012.
daniel
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman
Hi all,
We must freeze the Qt 5.5.0 content now so please don't push any new changes in
'5.5.0' branch anymore; those won't be staged. Final qt5.git integration is now
ongoing & when it succeed final Qt5.5.0 packages will be created for testing.
br,
Jani
_
13 matches
Mail list logo
