On Sunday, 13 March 2022 05:51:39 PDT Alexey Rochev wrote:
> You mean second component of version by minor, right? So supported range
> for 6.3 is 6.0-6.7 (or 6.3-6.7)?
It would if we had made that decision earlier. Starting with 6.3, it will be
N-4 to N+4, so for 6.3 it is 6.3 to 6.7.
> I think
Hi,
See
https://lists.qt-project.org/pipermail/development/2021-November/041917.html
Quote:
>Apart from that, after internal discussion I have to lower expectations
>regarding our commitment to this. I don't see us creating the test
>infra for testing the build of different host/target Qt combi
You mean second component of version by minor, right? So supported range
for 6.3 is 6.0-6.7 (or 6.3-6.7)?
I think it would be a good idea to test this in CI builds. If support of
different host Qt versions is not guaranteed then users can't rely on
binary Qt builds provided by their distributions
On Saturday, 12 March 2022 14:24:20 PST Alexey Rochev wrote:
> Does cross-compiling Qt6 (for Android) require exact same version of
> host Qt to build correctly? I'm assuming that it does since when I
> tried to cross-compile 6.2.2 using host 6.2.3 (don't ask me why) it
> failed with a strange erro
Does cross-compiling Qt6 (for Android) require exact same version of
host Qt to build correctly? I'm assuming that it does since when I
tried to cross-compile 6.2.2 using host 6.2.3 (don't ask me why) it
failed with a strange error (in cmake_automoc_parser) and it was gone
when I updated the cross-
