Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Scott Bloom
On Saturday, 15 June 2019 12:22:34 PDT Bogdan Vatra via Development wrote: > > Why must they be built in one go? Why can't they be separate builds > > stitched together? Or even completely separate builds as on Linux > > and all the other Unix? > > Because qmake can build them in one go and la

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Konstantin Tokarev
16.06.2019, 00:22, "Thiago Macieira" : > On Saturday, 15 June 2019 12:22:34 PDT Bogdan Vatra via Development wrote: >>  > Why must they be built in one go? Why can't they be separate builds >>  > stitched together? Or even completely separate builds as on Linux and all >>  > the other Unix? >> >>

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Thiago Macieira
On Saturday, 15 June 2019 12:22:34 PDT Bogdan Vatra via Development wrote: > > Why must they be built in one go? Why can't they be separate builds > > stitched together? Or even completely separate builds as on Linux and all > > the other Unix? > > Because qmake can build them in one go and last

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Bogdan Vatra via Development
În ziua de sâmbătă, 15 iunie 2019, la 19:32:52 EEST, Thiago Macieira a scris: > On Friday, 14 June 2019 23:45:47 PDT Bogdan Vatra via Development wrote: [...] > > > So, as long as we need to provide libs, (qml) plugins for debug & release > > I think building them in one go is a must have feature

Re: [Development] unique_ptr and Qt, Take 2

2019-06-15 Thread Ville Voutilainen
On Sat, 15 Jun 2019 at 02:30, Matthew Woehlke wrote: > >> OTOH, I just realized a problem with that... when the new child needs to > >> take its parent in the ctor for other reasons. I don't know if there is > >> an easy solution to that. (Of course, you can still pass the parent with > >> createC

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Thiago Macieira
On Friday, 14 June 2019 23:45:47 PDT Bogdan Vatra via Development wrote: > > I wouldn't call that a hard requirement. Separate builds for debug and for > > release are acceptable, the same way that we've ostensibly had support for > > shared-and-release builds but in practice they're always built s

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Thiago Macieira
On Saturday, 15 June 2019 02:18:28 PDT Jean-Michaël Celerier wrote: > You can download a CMake static binary (https://cmake.org/download/) that Whether we need to require such a thing is a point of discussion for the Qt 6.0 release. That's the same as requirements on libraries: if we require a P

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Sérgio Martins via Development
On 2019-06-15 07:45, Bogdan Vatra via Development wrote: Hi, În ziua de joi, 13 iunie 2019, la 18:22:14 EEST, Thiago Macieira a scris: On Thursday, 13 June 2019 01:06:06 PDT Bogdan Vatra via Development wrote: > Hi, > > There is one more missing feature to add to your list: build & debug >

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Jean-Michaël Celerier
Hello :) > What makes you think that you can build Qt for any platform with cmake found in Ubuntu 16.04 (or any later version) ? You can download a CMake static binary (https://cmake.org/download/) that runs fine on Ubuntu 16.04 (or 12.04 or CentOS 6 for that matters) - and it wouldn't be hard to

Re: [Development] Proposing CMake as build tool for Qt 6

2019-06-15 Thread Kevin Kofler
Bogdan Vatra via Development wrote: > According to https://code.qt.io/cgit/qt/qtbase.git/tree/CMakeLists.txt? > h=wip/cmake#n1 Qt needs CMake *3.15.0* which is not even released. This > means you'll need *NEXT* Ubuntu LTS (20.04?) to build Qt, this means we > should put Qt6 on pause until 2022 :)