It will not block CI.
Best regards, Mikhail ________________________________ From: Kari Oikarinen Sent: Thursday, March 21, 2019 1:13 PM To: Mikhail Svetkin; development@qt-project.org Subject: Re: [Development] CMake branch On 21.3.2019 14.00, Mikhail Svetkin wrote: > * > > * > > Hi everyone! > > > We’ve had an internal discussion about wip/cmake branch. > > > We thought maybe it is a good idea to merge wip/cmake into dev branch. > > > The advantages are: > > - It allows our contributors to play with CMake in dev branch > > - Speed-up the build of QtBase > > - Easy to find a lot of bugs in CMake port > > - CI could have a nightly build with CMake and generate a report > > - We can synchronize CMakeFiles and *.pro files > > > The disadvantages are: > > - Any changes should be passed by CI > > > Do you have any objections? > > ** > Would this have blocking CI or not? The stated disadvantage (which surely shouldn't be entirely negative) implies that it would be. But the build being nightly hints that it would not be. A blocking build would mean that all changes need to leave the CMake build working. So everyone would need to take care of both build systems. A more defined transition point and only one official build system at a time would be nicer. Or at least trying to minimize the time of having two. Unless of course we'd already be ready to drop building Qt with qmake, but I guess that's not where we are yet. Is that expected to happen during 5.x series at all or only with Qt 6? -- Kari
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
