On Fri, Mar 22, 2019 at 12:53 PM Joerg Bornemann wrote:
> I believe that this means a reduced feature set for the CMake port.
That's not what I wanted to say:-)
All buildsystems all have things where they are nice to use and other
areas where they are less nice.
I want a build system for Qt
Am Freitag, den 22.03.2019, 10:45 + schrieb Jedrzej Nowacki:
> I'm supporting Mikhail' proposal and I'm probably a bit guilty of the
> thread
> too. As some of you know I'm not enthusiastic about any build system. I
> really
> think that there are too complex for the purpose. What I care
On 3/21/19 5:39 PM, Tobias Hunger wrote:
> We do not want to port all the qmake-quirks over to cmake. We get enough
> quirks
> for free straight from cmake:-)
I believe that this means a reduced feature set for the CMake port.
What kind of things do we expect to go away that we take for granted
On 3/21/19 5:01 PM, Alex Blasche wrote:
- We can synchronize CMakeFiles and *.pro files
>>> I do not understand this part.
>> We can ask people to update CMakeFiles after updating pro files.
>
> I don't think that you can make this a requirement at this point in time. You
> may find
On Friday, March 22, 2019 9:58:33 AM CET Simon Hausmann wrote:
> Am 21.03.19 um 15:54 schrieb Tobias Hunger:
>
> > My idea was to ask for merging wip/cmake after
> > https://bugreports.qt.io/browse/QTBUG-73925 (aka. "milestone 1"). At that
> > point
the branch would be in a state where people
: Mikhail Svetkin
Sent: Friday, March 22, 2019 10:49
To: Simon Hausmann; development@qt-project.org
Subject: Re: [Development] CMake branch
I think it is not bad idea in general, but I think we need to wait only some of
them (maybe only build qtsvg and qt5).
I think instead of creating new branches
Hausmann
Sent: Friday, March 22, 2019 9:58 AM
To: development@qt-project.org
Subject: Re: [Development] CMake branch
Am 21.03.19 um 15:54 schrieb Tobias Hunger:
> My idea was to ask for merging wip/cmake after
> https://bugreports.qt.io/browse/QTBUG-73925 (aka. "milestone 1").
Hi,
You can find it here
https://code.qt.io/cgit/qt/qtbase.git/tree/util/cmake/pro2cmake.py?h=wip/cmake
> On 22. Mar 2019, at 10:06, Julius Bullinger
> wrote:
>
> On 22.03.2019 09:58, Simon Hausmann wrote:
>
>> I think earlier last year we never considered this even, but today
>> the
From: Development on behalf of Julius
Bullinger
Sent: Friday, March 22, 2019 10:06
To: development@qt-project.org
Subject: Re: [Development] CMake branch
On 22.03.2019 09:58, Simon Hausmann wrote:
> I think earlier last year we never considered this even, but to
On 22.03.2019 09:58, Simon Hausmann wrote:
I think earlier last year we never considered this even, but today
the quality of the .pro file converter has made this a possibility
worth trying.
Is this converter available somewhere? We're currently planning to
migrate a project from qmake to
Am 21.03.19 um 15:54 schrieb Tobias Hunger:
> My idea was to ask for merging wip/cmake after
> https://bugreports.qt.io/browse/QTBUG-73925 (aka. "milestone 1"). At that
> point
> the branch would be in a state where people can work on Qt (for certain
> platforms) using cmake and do
On 21.03.2019 19:10, André Pönitz wrote:
> On Thu, Mar 21, 2019 at 03:06:18PM +, Mikhail Svetkin wrote:
>>> I find it hard to believe that this improves the quality of Qt 5.14 or 5.15.
>>> Effectively you are proposing that we don't have any blocking CI for those
>>> two
>>> Qt releases.
On Thu, Mar 21, 2019 at 03:06:18PM +, Mikhail Svetkin wrote:
> > I find it hard to believe that this improves the quality of Qt 5.14 or 5.15.
> > Effectively you are proposing that we don't have any blocking CI for those
> > two
> > Qt releases. Otherwise you would have to implement very
Hello,
I really like the idea Mikhail proposed. I would even go as far as to add one
platform where we start testing building Qt with CMake in the CI once we reach
a level where we are comfortable with it.
I think it makes sense to get the CMake port more exposed and let people play
with it
Am Donnerstag, den 21.03.2019, 15:26 + schrieb Mikhail Svetkin:
> > I do not understand this part.
>
> We can ask people to update CMakeFiles after updating pro files.
Creator has two build systems and that is a constant PITA.
If we decide to do this, then we need to have one CMake build
On 21.03.19 17:01, Alex Blasche wrote:
>>> We need volunteers for this! I do not see the team currently trying to
>>> port
>> Qtbase to CMake having the necessary resources.
>>
>> I think people do not want to just play with CMake. They want to build Qt
>> (in our
>> case QtBase) with CMake and
> -Original Message-
> From: Development On Behalf Of
> Mikhail Svetkin
>>> - We can synchronize CMakeFiles and *.pro files
> > I do not understand this part.
> We can ask people to update CMakeFiles after updating pro files.
I don't think that you can make this a requirement at this
lp with keeping
cmake up-to-date with qmake.
Let's send a patch and see what happens.
Best regards,
Mikhail
From: Mikhail Svetkin
Sent: Thursday, March 21, 2019 4:06 PM
To: Alex Blasche
Cc: development@qt-project.org
Subject: Re: [Development] CMake branch
>
__
From: Volker Hilsheimer
Sent: Thursday, March 21, 2019 1:51 PM
To: Mikhail Svetkin
Cc: development@qt-project.org
Subject: Re: [Development] CMake branch
On 21 Mar 2019, at 13:00, Mikhail Svetkin
mailto:mikhail.svet...@qt.io>> wrote:
Hi everyone!
We’ve had an internal discussion a
Hi all,
On Thu, 2019-03-21 at 12:51 +, Volker Hilsheimer wrote:
> The advantages are:
> - It allows our contributors to play with CMake in dev branch
> - Speed-up the build of QtBase
How so?
> - Easy to find a lot of bugs in CMake port
> - CI could have a nightly build with CMake and
From: Development on behalf of Mikhail
Svetkin
>The disadvantages are:
> - Any changes should be passed by CI
I find it hard to believe that this improves the quality of Qt 5.14 or 5.15.
Effectively you are proposing that we don't have any blocking
On 21 Mar 2019, at 13:00, Mikhail Svetkin
mailto:mikhail.svet...@qt.io>> 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
@qt-project.org
Subject: Re: [Development] CMake branch
Could you explain the stated disadvantage further then?
--
Kari
On 21.3.2019 14.21, Mikhail Svetkin wrote:
> It will not block CI.
>
>
>
>
> Be
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:
>> *
>>
>> *
ikarinen
> *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!
>>
>
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:
> *
>
>
] 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:
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
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
29 matches
Mail list logo
