We intend to remove the .pro files for building Qt itself.
One remaining question is if we want to keep the .pro files of the examples.
I think we should.
In which case, the CMake CI jobs that build examples should build them both with CMake and in addition with qmake. This will ensure build coverage of qmake examples.
That also raises the question, which of the cmake or qmake projects will be the source of truth.
Do we want the CMake projects to be the source of truth? In that case we won't be able to use pro2cmake, but will have to do manual modifications of the .pro files.
|For Gerrit Dashboard: QTBUG-85986|
|310667,46||CMake: Build examples with qmake against a CMake built Qt||dev||qt/qtbase||Status: MERGED||+2||0|
|310668,30||CMake: Try to build qmake examples on more configs||dev||qt/qt5||Status: MERGED||+2||0|
|310669,9||WIP: CMake: Try to build qmake examples in qtsvg||dev||qt/qtsvg||Status: ABANDONED||-2||0|
|310817,2||CMake: Workaround building DBus 'car' example with qmake||dev||qt/qtbase||Status: MERGED||+2||0|
|323938,3||CMake: Work around building dbus 'controller' example with qmake||dev||qt/qtbase||Status: MERGED||+2||0|
|325459,2||CMake: Work around building dbus 'controller' example with qmake||6.0||qt/qtbase||Status: MERGED||+2||0|
|325576,2||CMake: Build examples with qmake against a CMake built Qt||6.0||qt/qtbase||Status: MERGED||+2||0|