[Development] Changing definition of Qt meta macro to allow tools integration

Knoll Lars Lars.Knoll at theqtcompany.com
Thu Mar 31 10:01:54 CEST 2016

On 31/03/16 08:38, "Development on behalf of Olivier Goffart" <development-bounces+lars.knoll=theqtcompany.com at qt-project.org on behalf of olivier at woboq.com> wrote:

>Am Mittwoch, 30. März 2016, 21:04:50 CEST schrieb Thiago Macieira:
>> On quinta-feira, 31 de março de 2016 00:10:48 PDT Olivier Goffart wrote:
>> > The question is rather, the Qt creator that will be release in 2 years
>> > will
>> > maybe want to use these macros to auto complete signals/slots and
>> > properties. I would assume some people would still have a LTS version of
>> > Qt
>> > which would then be, say Qt 5.6.4.   So then it would be valable to habe
>> > this patch in the LTS branch.
>> I don't think it's valuable because those tools will need to deal with Qt
>> 5.6.0 and older.
>Why would they need to deal with 5.6.0 specifically?  
>As you said in another mail, 5.6 is LTS, not 5.6.0

I’m with Olivier here. We will not support 5.6.0 in three years anymore. What we will support is 5.6.x (x being the latest available patch level release).

So it does make sense to put the patch into 5.6, if the creator team is interested in using it.


More information about the Development mailing list