Re: [Development] BC/SC in patch releases (particularly enum additions)

On 23 Aug 2023, at 15:39, Marc Mutz via Development wrote: Hi, I cannot find Eddy's email in between, In case you're still looking for it: https://lists.qt-project.org/pipermail/development/2023-August/044348.html //! Paul -- Development mailing list Development@qt-project.org

Re: [Development] QtFluentMQ

Hello, >>If that is the ambition in the longer term, but you’d nevertheless want to >>start developing the project as a Qt module, then a repository in the >>playground/ namespace on our gerrit server can be a good start. That's actually the status we've left the discussion at from the

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

Hi, The issue here is that MinGW GCC is issuing a warning and that we compile with -Werror to treat warnings as errors. c++ - Importing inline functions in MinGW - Stack Overflow has a similar case. LLVM-MinGW

Re: [Development] BC/SC in patch releases (particularly enum additions)

On Wednesday, 23 August 2023 06:39:32 PDT Marc Mutz via Development wrote: > I cannot resist noting that the third item, in particular, is a problem > for QOperatingSystemVersion, which, despite years of yours truly's > hammering of that particular nail, is still exported as a > non-polymorphic

Re: [Development] QtFluentMQ

Hello QtFluentMQ Team, The project as you have described it sounds very cool and could be interesting for many Qt users building distributed systems. So thanks for the work so far and for reaching out! As for providing a repository on our gerrit server for your project, and perhaps moving it

Re: [Development] Failed to run configure.bat in qt/qt5 repository on Windows?

On Wednesday, 23 August 2023 06:03:24 PDT Alexandru Croitor via Development wrote: > Looking at the log, it appears that mingw's windres.exe can't handle spaces > in paths passed to -I? > > -I "C:/Program Files/PostgreSQL/14/include" > > cc1.exe: fatal error: Files/PostgreSQL/14/include: No

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Tuesday, 22 August 2023 23:35:56 PDT Haowei Hsu wrote: > Hello, Thiago. > > > No, I mean, why do you want to get Qt 6.2.4 in the first place? > > I didn't say that it had to be *6.2.4*. In fact, I've also tried to build > other Qt6 releases, such as: *6.1, 6.3, 6.5*... etc. And have you

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On 23 Aug 2023, at 08:35, Haowei Hsu wrote: Hello, Thiago. No, I mean, why do you want to get Qt 6.2.4 in the first place? I didn't say that it had to be 6.2.4. In fact, I've also tried to build other Qt6 releases, such as: 6.1, 6.3, 6.5... etc. However, I found during the process that when

[Development] On the use of the inline keyword

Hi, Every now and then we get a sporadic MinGW error because someone writes the moral equivalent of the following: class Q_FOO_EXPORT QMeep { QBar bar() const; }; inline QBar QMeep::bar() const; Resulting in something like this: qmeep.h:

Re: [Development] BC/SC in patch releases (particularly enum additions)

> On 23 Aug 2023, at 15:09, Edward Welbourne via Development > wrote: > > Lars Knoll (23 August 2023 13:32) wrote >> We have been adding new enum values in certain cases. The operating >> system versions needing to be amended to support a new version of >> macOS is one example. That has

Re: [Development] BC/SC in patch releases (particularly enum additions)

Hi, I cannot find Eddy's email in between, but from what I can gleam from Lars' quoting of it, I'd be fine with adding enum values in patch releaes, provided that - they're documented (with \since x.y._z_ for each x.y.z they were new in (hypotheically, 6.5.3, 6.6.1, 6.7), and in

Re: [Development] BC/SC in patch releases (particularly enum additions)

Lars Knoll (23 August 2023 13:32) wrote > We have been adding new enum values in certain cases. The operating > system versions needing to be amended to support a new version of > macOS is one example. That has happened a couple of times within LTS > releases as far as I remember. > > We’ve also

Re: [Development] Failed to run configure.bat in qt/qt5 repository on Windows?

Hi, Looking at the log, it appears that mingw's windres.exe can't handle spaces in paths passed to -I? -I "C:/Program Files/PostgreSQL/14/include" cc1.exe: fatal error: Files/PostgreSQL/14/include: No such file or directory compilation terminated. In any case, you can work around it by either

Re: [Development] QtFluentMQ

Hello, I forgot to mention that we're looking forward to a qtlab repository creation to migrate the Kafka soruces and developpe the AMQP support project as a Qt module. The design proposal is built around the bridge pattern which is a PIMPL tree. We have people rooting for a plugin based arch

Re: [Development] BC/SC in patch releases (particularly enum additions)

> On 23 Aug 2023, at 11:48, Edward Welbourne via Development > wrote: > > On Tuesday, 22 August 2023 14:27:09 PDT Marc Mutz via Development wrote: I think we should decide what we mean by forward BC and SC and describe it in https://wiki.qt.io/Qt-Version-Compatibility more

Re: [Development] Failed to run configure.bat in qt/qt5 repository on Windows?

Oops! I forgot to add one step in the above commands. There should be: - *git checkout 6.2.4* between the Step 3 and Step 4. Therefore, it should be: 1. *chdir /d D:\Repo\tmp* 2. *git clone https://github.com/qt/qt5.git qt-6.2.4* 3. *chdir

[Development] Qt Creator Survey - Qt Group

Hi everyone, Whether you are a Qt Creator user or not, the Qt Group would like to hear your thoughts and experiences as an IDE user. Please take our survey to help us improve Qt Creator's user experience: https://www.surveymonkey.com/r/qtcreatorsurvey2023 Cheers, Pedro Bessa Community

Re: [Development] BC/SC in patch releases (particularly enum additions)

On Tuesday, 22 August 2023 14:27:09 PDT Marc Mutz via Development wrote: >>> I think we should decide what we mean by forward BC and SC and >>> describe it in https://wiki.qt.io/Qt-Version-Compatibility more >>> precisely. On 23.08.23 04:48, Thiago Macieira wrote: >> I thought the rule was "no

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

Hello, Thiago. > No, I mean, why do you want to get Qt 6.2.4 in the first place? I didn't say that it had to be *6.2.4*. In fact, I've also tried to build other Qt6 releases, such as: *6.1, 6.3, 6.5*... etc. However, I found during the process that when I initialize submodules in the *dev*