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

On 31/03/16 20:33, "Development on behalf of Thiago Macieira" wrote: >On quinta-feira, 31 de março de 2016 08:01:54 PDT Knoll Lars wrote: >> >Why would they need to deal with 5.6.0

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

On quinta-feira, 31 de março de 2016 08:01:54 PDT Knoll Lars wrote: > >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

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

On 31/03/16 08:38, "Development on behalf of Olivier Goffart" 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

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

On 03/31/2016 12:10 AM, 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

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

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 >

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

Op 31/03/2016 om 06:04 schreef 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

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

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

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

Am Mittwoch, 30. März 2016, 12:39:58 CEST schrieb Thiago Macieira: > On quarta-feira, 30 de março de 2016 21:35:55 PDT Olivier Goffart wrote: > > > > I am also wondering in which branch to push this. Should it go in Qt > > > > 5.6 > > > > LTS so newer Qt creator can benefit of it starting from Qt

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

On quarta-feira, 30 de março de 2016 21:35:55 PDT Olivier Goffart wrote: > > > I am also wondering in which branch to push this. Should it go in Qt 5.6 > > > LTS so newer Qt creator can benefit of it starting from Qt 5.6.1? > > > > You've proposed it for dev, but I think it deserves at least 5.7.

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

Am Mittwoch, 30. März 2016, 08:58:48 CEST schrieb Thiago Macieira: > On quarta-feira, 30 de março de 2016 16:08:52 PDT Olivier Goffart wrote: > > Hi, > > > > As I am working on porting qdoc using clang, this is yet another time a > > tool is using clang to get information about Qt code and Qt

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

On quarta-feira, 30 de março de 2016 16:08:52 PDT Olivier Goffart wrote: > Hi, > > As I am working on porting qdoc using clang, this is yet another time a tool > is using clang to get information about Qt code and Qt meta macro (signals, > slots, properties, ...) > > This has been done before:

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

Hi, As I am working on porting qdoc using clang, this is yet another time a tool is using clang to get information about Qt code and Qt meta macro (signals, slots, properties, ...) This has been done before: qtcreator's clang code model [1], moc-ng [2], kdevelop, ... In each case, we need to