Re: [Development] Qt Creator 15 RC released

[heart] Maija Metso reacted to your message: From: Development on behalf of List for announcements regarding Qt releases and development via Announce via Development Sent: Thursday, November 14, 2024 12:46:39 PM To: List for announcements regarding Qt re

Re: [Development] moc output changes coming

On Thursday 14 November 2024 02:20:16 Mountain Standard Time Volker Hilsheimer via Development wrote: > Did you build Qt SCXML? Build fails now with: > > error: "qtmochelpers.h not found or too old.” Yes, but it looks like I never pushed the fix. I found it yesterday when working on something e

[Development] [Announce] Qt Creator 15 RC released

We are happy to announce the release of Qt Creator 15 RC! https://www.qt.io/blog/qt-creator-15-rc-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

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

On 2024-11-14, Joerg Bornemann via Development wrote: > On 11/14/24 09:14, Sune Vuorela wrote: > >>> Or is it more specific that you think that the backports-provided cmake >>> will not be stable enough for building software? >>> >>> CMake is generally very good in regards to compatibility and b

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

On 11/14/24 09:14, Sune Vuorela wrote: Or is it more specific that you think that the backports-provided cmake will not be stable enough for building software? CMake is generally very good in regards to compatibility and building older and newer projects. The change in Debian unstable from

Re: [Development] moc output changes coming

> error: "qtmochelpers.h not found or too old.” Should be fixed by https://codereview.qt-project.org/c/qt/qtscxml/+/604244 -- Ivan From: Development on behalf of Volker Hilsheimer via Development Sent: Thursday, November 14

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

On 2024-11-13, Alexandru Croitor via Development asked: Which debian stable version are you using? On 13. Nov 2024, at 15:38, Sune Vuorela replied: >>> Debian stable is debian 12. It ships with 3.25. Alexandru Croitor (13 November 2024 16:04) replied: > At the same time, debian 13 will r

Re: [Development] moc output changes coming

> On 12 Nov 2024, at 03:48, Thiago Macieira wrote: > > The changes to moc are getting integrated. The next batch will include a > change to the output revision number, so qtmetamacros.h and moc must match. > Because we decided that moc does not need to keep compatibility, you may need > to r

Re: [Development] Deprecated vs deprecated-to-be-removed APIs in Qt

Hi Jarek, > Would it be possible to turn on warnings for deprecations that are going to > be removed, and at the same: time turn off other deprecation warnings which > are not going to be removed? That can be done if the to-be-removed APIs would use some new macro instead of QT_DEPRECATED_VERSION

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

one point to consider is that cmake does not have any run-time dependencies and it is extremely easy to install independently from the OS: the binaries provided by kitware are fully self-contained and can be installed in parallel to system-provided cmake. Installing binaries compiled by someone

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

Hi, Just out of curiosity, what are the features added to cmake 3.26 that makes it so much better than 3.25 and which Qt really needs? Cheers, BogDan. În ziua de miercuri, 13 noiembrie 2024, la 17:04:15 EET, Alexandru Croitor via Development a scris: > > On 13. Nov 2024, at 16:01, Alexandru

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

On 2024-11-13, Alexandru Croitor via Development wrote: > Do you consider it unreasonable due to backports being 'backports', so not > 'stable', thus you are completely against installing any software from there? Yes. Also I need other projects I work at to not pull in a too new CMake by accid

Re: [Development] Deprecated vs deprecated-to-be-removed APIs in Qt

Would it be possible to turn on warnings for deprecations that are going to be removed, and at the same: time turn off other deprecation warnings which are not going to be removed? From: Development on behalf of Alex Blasche via Development Sent: Thurs

Re: [Development] Deprecated vs deprecated-to-be-removed APIs in Qt

Hi, Let's move forward with the given patch. Patch discussion seems to have mostly settled with only marginal (if any) improvement discussions. Once this has merged I propose we simply start going systematically through the code base per directory or module (depending on reasonable number of ca