Re: [Development] Failed to run configure.bat in qt/qt5 on MINGW64/MSYS2 shell?

Hi, MSYS2 provides prebuilt packages for Qt. I'd suspect the build scripts of theses packages being a good starting point for building modified versions of Qt with this toolchain: Latest: https://github.com/msys2/MINGW-packages/tree/6a7d1f44862b5cda846d554fd8e6ba6795a6a1cd/mingw-w64-qt6-base

Re: [Development] On the use of the inline keyword

Am 24.08.2023 um 21:42 schrieb Thiago Macieira: That warning looks like a bug in the compiler instead. So if there's no ill- effect, I'd just disable and ignore it. Seems like an easy fix, but breaks user code that explicitly enables this warning. Guess ignoring is not a good option, if one c

Re: [Development] [RFCs] Migrate from GCC MinGW to LLVM MinGW

Am 20.07.2023 um 04:21 schrieb Thiago Macieira: On Wednesday, 19 July 2023 18:55:34 PDT Yang Fan wrote: I wanted to point out that MSYS2 offers precompiled packages of Qt6 in four different environments: CLANGARM64, MINGW64, CLANG64, and UCRT64. Is there any difference between mingw64 and clang

Re: [Development] Module maintainers: QT_NO_CONTEXTLESS_CONNECT in your modules

Hi Peppe, thank you alot for this highly appreciated and super useful feature! Give up counting how often I forgot the context argument. Ciao Mathias Am 10.07.2023 um 18:02 schrieb Giuseppe D'Angelo via Development: Hi, https://codereview.qt-project.org/c/qt/qtbase/+/487560 introduces QT_NO_

Re: [Development] API style guide: scoped enum or not?

Am 04.05.2023 um 15:51 schrieb Sune Vuorela: In few cases the implicit conversion to underlying_type is kind of important. Especially in the cases where the api has int and is mostly used with enums or is somehow user extendable. Qt::ItemDataRole is one of them that comes to mind. switch(role

Re: [Development] qsizetype

My take on qsizetype: Just revert this failed experiment. It's a huge annoyance for little to no benefit. I'll never understand how this very broken and incomplete experiment could make it into Qt's main branch at all. Am 13.09.2022 um 15:12 schrieb Volker Hilsheimer: On 12 Sep 2022, at 20:04,

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

Hi, Just to make ensure all options are considered: How about the elephant in the room? How about "simply" implementing JSONC (JSON with Comments) in Qt's JSON parser instead? * People wonder regularly when they learnm that there are no comments in JSON. * JSONC is used by popular software

Re: [Development] Using '#pragma once' instead of include guards?

Sounds like an excellent plan. Ciao Mathias Am 12.10.2022 um 12:35 schrieb Volker Hilsheimer via Development: On 11 Oct 2022, at 22:11, Thiago Macieira wrote: On Tuesday, 11 October 2022 12:25:13 PDT Kyle Edwards via Development wrote: Speaking as co-maintainer of CMake, we have effectively

Re: [Development] Using '#pragma once' instead of include guards?

Am 11.10.2022 um 21:20 schrieb Kevin Kofler via Development: "locking you down to a vendor" is a funny argument when the Wikipedia article: https://en.wikipedia.org/wiki/Pragma_once cannot name a single compiler that does not support #pragma once, and 20 that do. Yes, it is supported in a way

Re: [Development] Using '#pragma once' instead of include guards?

I am surprised by the question: "It's non-standard and it's behavior is undefined" actually should be enough to avoid such feature. Actually if a reliable implementation of "#pragma once" would be possible, that feature would have been included in the C++ standard for a long time already, woul