Re: [cmake-developers] QtAutogen suggestions

2016-11-28 Thread Sebastian Holtermann
Am 28.11.2016 um 17:00 schrieb Brad King: > On 11/28/2016 10:25 AM, Sebastian Holtermann wrote: >> I'm going ahead then. > > Thanks. BTW, please sign up for a gitlab.kitware.com account > (optionally via GitHub OAuth) so that we can include you in > discussion of related issues. For example:

Re: [cmake-developers] QtAutogen suggestions

2016-11-28 Thread Brad King
On 11/28/2016 10:25 AM, Sebastian Holtermann wrote: > I'm going ahead then. Thanks. BTW, please sign up for a gitlab.kitware.com account (optionally via GitHub OAuth) so that we can include you in discussion of related issues. For example: * https://gitlab.kitware.com/cmake/cmake/issues/16460

Re: [cmake-developers] QtAutogen suggestions

2016-11-28 Thread Sebastian Holtermann
Am 28.11.2016 um 15:57 schrieb Brad King: > On 11/25/2016 05:37 PM, Sebastian Holtermann wrote: >> There are some issues with QtAutogen that still bother me and >> that I would like to change. > > Great! We currently have no dedicated maintainer for it and I have > little understanding of the

Re: [cmake-developers] QtAutogen suggestions

2016-11-28 Thread Brad King
On 11/25/2016 05:37 PM, Sebastian Holtermann wrote: > There are some issues with QtAutogen that still bother me and > that I would like to change. Great! We currently have no dedicated maintainer for it and I have little understanding of the tools and use cases associated with it myself. It

[cmake-developers] QtAutogen suggestions

2016-11-25 Thread Sebastian Holtermann
Hi. There are some issues with QtAutogen that still bother me and that I would like to change. 1) Most files get generated in ${CMAKE_CURRENT_BINARY_DIR}/${TARGETNAME}_automoc.dir Is the ".dir" suffix neccessary? I think is should be removed. 2) Moc files that are manually included by a