Some I can think of:
- Slower git operations.
- Slower build times for qtdeclarative devs. You can use e.g. ninja targets,
but you would have to do this every time you build. Ideally we’d add a
configure option for this, like -no-gui in qtbase, so that they don’t need to
build qtquickcontrols2.
I would really be interested if there are other leaf modules that have this
issue. If it's just qtquickcontrols2 then perhaps merging into qtdeclarative
would be the easiest solution after all.
Taking a quick look through the qtquickcontrols2’s changes, it seems a large
number(half?) of them ar
Hi all,
We have released Qt 6.1.1 today, see https://www.qt.io/blog/qt-6.1.1-released
Like written in the post Qt for Python is also available by the usual means.
Big thanks to everyone involved!
br,
Jani Heikkinen
Release Manager
___
Development mail
Good point. I guess you implied this in "all the relevant examples", but just
to spell it out: this would also allow other leaf repositories that currently
depend on qtdeclarative.git, but might not want to depend on
qtquickcontrols2.git for whatever reason, to use controls in their examples.
F
> -Original Message-
> From: Volker Hilsheimer
> Sent: Friday, 4 June 2021 4:51 PM
> To: Mitch Curtis
> Cc: development@qt-project.org
> Subject: Re: [Development] Solutions for ensuring that changes in upstream
> modules are tested with downstream modules before merging
>
> > On 4 Jun 2
