[Qt] Update to 6.10.1

[Neumann-A]

Blocked by:

• Android SDK update (>=35, currently 34)
• resolution https://qt-project.atlassian.net/browse/QTBUG-143110 (unless I want to patch the two failing ports to explicitly cast)

[Neumann-A]

@BillyONeal: This PR seems to require an update of the android SDK to make the android pipeline happy.

The default platform SDK android-36 not found, using the latest installed android-34 instead.

/mnt/vcpkg-ci/b/qtbase/src/here-src-6-6bf147c64f.clean/src/android/jar/src/org/qtproject/qt/android/QtDisplayManager.java:243: error: cannot find symbol
        if (Build.VERSION.SDK_INT < Build.VERSION_CODES.VANILLA_ICE_CREAM)
                                                       ^
  symbol:   variable VANILLA_ICE_CREAM
  location: class VERSION_CODES

[rokm]

If it helps, in Qt 6.10.1 QString::arg() stopped accepting arguments of types that implicitly convert to integral types, as per note found at https://doc.qt.io/qt-6/qstring.html#arg-2:

In Qt versions prior to 6.10.1, this function accepted arguments of types that implicitly convert 
to integral types. This is no longer supported, except for (unscoped) enums, because it also 
accepted types convertible to floating-point types, losing precision when those were printed 
as integers. A backwards-compatible fix is to cast such types to a C++ type whose displayed 
form matches your intent (int, float, ...).

---

At the moment, at least paraview build seems to be failing due to this:

/mnt/vcpkg-ci/b/paraview/src/3849afafb2-5a32203628.clean/ThirdParty/QtTesting/vtkqttesting/pqAbstractItemViewEventTranslator.cxx:121:28: error: no matching function for call to ‘QString::arg(Qt::MouseButtons)’
  119 |       QString info = QString("%1,%2,%3,%4,%5,%6")
      |                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  120 |                        .arg(mouseEvent->button())
      |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~
  121 |                        .arg(mouseEvent->buttons())
      |                        ~~~~^~~~~~~~~~~~~~~~~~~~~~~

---

Also kf6archive:

/mnt/vcpkg-ci/b/kf6archive/src/v6.7.0-619a9ab2f9.clean/src/karchive.cpp: In member function ‘virtual bool KArchive::open(QIODeviceBase::OpenMode)’:
/mnt/vcpkg-ci/b/kf6archive/src/v6.7.0-619a9ab2f9.clean/src/karchive.cpp:162:66: error: no matching function for call to ‘QString::arg(QIODeviceBase::OpenMode&)’
  162 |         setErrorString(tr("Could not open device in mode %1").arg(mode));

[ajtribick]

Might be worth bumping kf6archive to 6.21.0 to see if that fixes it. The mentioned example does seem to be fixed there, at least: https://github.com/KDE/karchive/blob/5f258908e5d8166008c06285036ebc9ee5e1b692/src/karchive.cpp#L182-L184

[Neumann-A]

Might be worth bumping kf6archive to 6.21.0

this is something for a different PR since bumping it probably requires bumping more KDE ports than just that one

[SunBlack]

Might be worth bumping kf6archive to 6.21.0

this is something for a different PR since bumping it probably requires bumping more KDE ports than just that one

Currently there is only one kf6 port, all other are still kf5. The kf6 port is now updated #49740.

[nickdademo]

What blockers remain for this PR? :)

[Neumann-A]

What blockers remain for this PR? :)

Android CI needs new SDK. Otherwise Android is red and I wont merge with master until that is resolved

[tsondergaard]

Hi @Neumann-A,

Android CI needs new SDK. Otherwise Android is red and I wont merge with master until that is resolved

Is there an issue or pr to fix/update the Android SDK then? I was not able to find anything with a search for "android sdk".

[Neumann-A]

78f987f

[BillyONeal]

#49981 will contain the Android build tools update.

[BillyONeal]

Android update is landed

[JavierMatosD]

@Neumann-A would you like to absorb #49429 change as well?

[Neumann-A]

@Neumann-A would you like to absorb #49429 change as well?

No I didnt plan to update this further since Qt already moved to 6.10.2 . Either merge that PR first or this one. I also don't exactly know what you are trying to achieve with this question since it will trigger a CI rebuild either way and the only thing you avoid is an additional Qt version in the registry.

[JavierMatosD]

@Neumann-A would you like to absorb #49429 change as well?

No I didnt plan to update this further since Qt already moved to 6.10.2 . Either merge that PR first or this one. I also don't exactly know what you are trying to achieve with this question since it will trigger a CI rebuild either way and the only thing you avoid is an additional Qt version in the registry.

No problem.