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

2023-07-20 Thread Martin Storsjö
On Thu, 20 Jul 2023, Cristian Adam via Development wrote: On 07/20/2023 15:48, Cristian Adam via Development wrote: At How to open Windows crash dumps? | Qt Forum this is one case of using Windows minidump files with MinGW, which is not supported. With the LLVM MinGW

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

2023-07-20 Thread Martin Storsjö
On Thu, 20 Jul 2023, Thiago Macieira wrote: On Thursday, 20 July 2023 06:14:24 PDT Martin Storsjö wrote: So are you saying that you're building your app with a non-default CRT selected with the -mcrtdll option? Yes. If you use the GCC -mcrtdll option for picking a non-default CRT, it would

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

2023-07-20 Thread Thiago Macieira
On Thursday, 20 July 2023 06:14:24 PDT Martin Storsjö wrote: > So are you saying that you're building your app with a non-default CRT > selected with the -mcrtdll option? Yes. > If you use the GCC -mcrtdll option for picking a non-default CRT, it would > work unless you're also linking, even stat

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

2023-07-20 Thread Cristian Adam via Development
On 07/20/2023 15:48, Cristian Adam via Development wrote: At How to open Windows crash dumps? | Qt Forum this is one case of using Windows minidump files with MinGW, which is not supported. With the LLVM MinGW and the PDB format

Re: [Development] std::optional for Q_PROPERTY

2023-07-20 Thread Kai Uwe Broulik
Hi, > That would mostly work, unless you want > a RESETable property, where RESET shouldn't lead to a nullopt value. It’s perfectly valid to have RESET set the value to whatever it thinks is correct, isn’t it? All it means is I can assign `undefined` from QML and have _something_ come out of i

Re: [Development] std::optional for Q_PROPERTY

2023-07-20 Thread Fabian Kosmale via Development
Hi, as far as QMetaType is concerned: We need a way to have some introspection on the "contained" type. That can't really be shoehorned into the current QMetaTypeInterface, because that one has neither enough space, nor a useable function pointer that could be hijacked. However, incrementing the Q

Re: [Development] std::optional for Q_PROPERTY

2023-07-20 Thread Pierre-Yves Siret
Le jeu. 20 juil. 2023 à 15:41, Kai Uwe Broulik a écrit : > Hi everyone, > > something that came up during this year’s KDE Akademy was that we > believe Q_PROPERTY should be able to handle std::optional, such that you > get a null QVariant out of it if it has no value. The main use case > being in

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

2023-07-20 Thread Thiago Macieira
On Thursday, 20 July 2023 06:03:27 PDT Cristian Adam via Development wrote: > On 07/20/2023 14:47, Thiago Macieira wrote: > > To Cristian: is the proposal to also switch from libstdc++ to libc++? > > Yes, LLVM MinGW only comes with libc++. Thanks, then that's doubly binary-incompatible. We canno

Re: [Development] std::optional for Q_PROPERTY

2023-07-20 Thread Elias Steurer via Development
Hi, I would like to voice my support for this and even extend the idea: * std::expected would also be nice here, because it can tell you /what/ went wrong. Yes, I know it is C++23... * Support for smart pointers, see QTBUG-60136 . It is alread

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

2023-07-20 Thread Cristian Adam via Development
On 07/19/2023 18:14, Thiago Macieira wrote: On Wednesday, 19 July 2023 08:46:27 PDT Cristian Adam via Development wrote: Hi, we are thinking of migrating from GCC MinGW to LLVM MinGW. The ticket in question is [QTBUG-107516] Migrate from GCC MinGW to LLVM-MinGW - Qt Bug Tracker

[Development] std::optional for Q_PROPERTY

2023-07-20 Thread Kai Uwe Broulik
Hi everyone, something that came up during this year’s KDE Akademy was that we believe Q_PROPERTY should be able to handle std::optional, such that you get a null QVariant out of it if it has no value. The main use case being interfacing “more modern C++” with QML in a type-safe way, rather t

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

2023-07-20 Thread Martin Storsjö
On Thu, 20 Jul 2023, Thiago Macieira wrote: On Wednesday, 19 July 2023 23:48:43 PDT Martin Storsjö wrote: Switching with those flags works, as long as you're building a C-only executable and linking libgcc statically (and not linking in any static libraries that were built for another CRT). I'm

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

2023-07-20 Thread Cristian Adam via Development
On 07/20/2023 14:47, Thiago Macieira wrote: > On Thursday, 20 July 2023 01:50:50 PDT Hasselmann Mathias via Development > wrote: >> MSYS2 has a configuration matrix on their website: >> https://www.msys2.org/docs/environments/ > Thanks, that's very informative. > > To Cristian: is the proposal to a

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

2023-07-20 Thread Thiago Macieira
On Thursday, 20 July 2023 01:50:50 PDT Hasselmann Mathias via Development wrote: > MSYS2 has a configuration matrix on their website: > https://www.msys2.org/docs/environments/ Thanks, that's very informative. To Cristian: is the proposal to also switch from libstdc++ to libc++? -- Thiago Maci

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

2023-07-20 Thread Thiago Macieira
On Wednesday, 19 July 2023 23:48:43 PDT Martin Storsjö wrote: > Switching with those flags works, as long as you're building a C-only > executable and linking libgcc statically (and not linking in any static > libraries that were built for another CRT). I'm pretty sure that libstdc++ > touches lots

[Development] [Announce] Qt Creator 11 released

2023-07-20 Thread List for announcements regarding Qt releases and development via Announce via Development
We are happy to announce the release of Qt Creator 11! https://www.qt.io/blog/qt-creator-11-released -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@qt.io https://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintun

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

2023-07-20 Thread Hasselmann Mathias via Development
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] [RFCs] Migrate from GCC MinGW to LLVM MinGW

2023-07-20 Thread Kai Köhne via Development
> From: Development on behalf of Yang Fan > > Sent: Thursday, July 20, 2023 3:55 AM > To: Cristian Adam > Cc: development@qt-project.org > Subject: Re: [Development] [RFCs] Migrate from GCC MinGW to LLVM MinGW > > I wanted to point out that MSYS2 offers precompiled packages of Qt6 in > four di

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

2023-07-20 Thread Martin Storsjö
On Thu, 20 Jul 2023, Martin Storsjö wrote: On Wed, 19 Jul 2023, Thiago Macieira wrote: It's also orthogonal, because GCC supports UCRT too, with this patch: https://github.com/msys2/MINGW-packages/raw/ 8d9ebb74412c1faabc2a3935bfc705bec19edb9a/mingw-w64-gcc/0006-Windows-New- feature-to-allow-ov