[Development] Raising minimum CMake version to 3.16 for Qt6
Some Qt modules rely on being able to extract metatypes from a CMake target. That logic, implemented in the qt6_extract_metatypes() command from Qt6CoreMacros.cmake, requires CMake behavior that was added in CMake 3.16. The implementation of that command checks this and halts with an error if CMake 3.15 or earlier is detected. That check has been there since Qt 6.0.0-alpha1. To our knowledge, there have been no bug reports related to this constraint. Until now, we’ve been aiming to make CMake 3.14 the minimum version for user projects (it is higher for building Qt itself). The above demonstrates that we actually require 3.16 and have done so since the beginning of Qt6. Right now, this might only have affected projects that were using or depended on qtdeclarative, although my understanding is that users of qtremoteobjects might also be affected. Given that we haven’t received any reports about this from user projects in the year since the code added this constraint, and that we expect to rely more on the metatypes going forward rather than less, the CMake Ports team proposes to raise the minimum CMake version for user projects to CMake 3.16. From what we can tell, the original target of 3.14 was likely based on the CMake versions available in major Linux distributions at the time, but 3.16 or later now seems to be widely enough available (Ubuntu 20.04 is the main blocker for being able to go any higher than 3.16). Craig Scott ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt 6 docs: noexcept and constexpr
On Tue, May 4, 2021 at 3:04 PM Giuseppe D'Angelo wrote: > No. I'd say a qdoc bug/feature request is in order. > Right, I opened an issue on JIRA[1] about it, thanks. On Tue, May 4, 2021 at 6:34 PM Topi Reiniö wrote: > QDoc uses libclang to parse the C++ sources, and there are cases where C++ > attributes/specifiers are not exposed in the AST provided by libclang. > It's possible to create workarounds for these limitations, but these are > yet to be implemented. > Strange. Anyway I tried to attach the bugreport[1] to the 'Qt6 Documentation' epic but JIRA didn't allow me. I assume it's about permissions and such, so if you want to move it there, you're going to need to do it yourself. [1]: https://bugreports.qt.io/browse/QTBUG-93439 ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt 6 docs: noexcept and constexpr
Hi, No, those are indeed missing from the generated documentation. QDoc uses libclang to parse the C++ sources, and there are cases where C++ attributes/specifiers are not exposed in the AST provided by libclang. It's possible to create workarounds for these limitations, but these are yet to be implemented. \topi From: Development on behalf of Konstantin Shegunov Sent: Tuesday, May 4, 2021 1:06 PM To: Qt development mailing list Subject: [Development] Qt 6 docs: noexcept and constexpr Hi, Is qdoc supposed to mark the mentioned declarations? I just checked the Qt 6 docs for the QFlags and it doesn't seem to indicate either, although they are declared as such in code. Am I missing something here? ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt 6 docs: noexcept and constexpr
Hi, Is qdoc supposed to mark the mentioned declarations? I just checked the Qt 6 docs for the QFlags and it doesn't seem to indicate either, although they are declared as such in code. Am I missing something here? ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt 6.0.4 released
Hi, We have released Qt 6.0.4 today, see https://www.qt.io/blog/qt-6.0.4-released Big thanks to everyone involved! br, Jani Heikkinen Release Manager ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
