[Development] CMake branch
Kari Oikarinen
kari.oikarinen at qt.io
Thu Mar 21 13:24:09 CET 2019
Never mind. The issue is of course that changes need to go through CI, even
though it doesn't check them.
--
Kari
On 21.3.2019 14.21, Mikhail Svetkin wrote:
> It will not block CI.
>
>
>
>
> Best regards,
> Mikhail
> --------------------------------------------------------------------------------
> *From:* Kari Oikarinen
> *Sent:* Thursday, March 21, 2019 1:13 PM
> *To:* Mikhail Svetkin; development at 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
--
---
Kari Oikarinen
Senior Software Engineer
The Qt Company
Elektroniikkatie 13
90590, Oulu, Finland
kari.oikarinen at qt.io
+358 50 5281010
http://qt.io
---
More information about the Development
mailing list