Re: [Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

Il 04/04/25 20:15, Thiago Macieira ha scritto: The QMetaType registration process takes type names into account to determine if two types are the same or not. That may be the right thing for the majority of types, but it's not for everything. For example, if two libraries have two different "str

Re: [Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

On Friday, 4 April 2025 13:07:12 Pacific Daylight Time Milian Wolff wrote: > Agreed to all of this. But for me at least, the impact of visibility on non- > polymorphic types, which you don't use dynamic cast nor throw as > exceptions, was, so far, not clear at all. And this is the "new" part. Also

Re: [Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

On Freitag, 4. April 2025 17:44:49 Mitteleuropäische Sommerzeit Thiago Macieira wrote: > On Friday, 4 April 2025 08:07:27 Pacific Daylight Time Milian Wolff wrote: > > Because if you do so, and the type is public (i.e. all-inline), then you > > would not be able to safely put that into a `std::any

[Development] Public 6.8 branch will be closed soon

Hi all, Qt 6.9.0 was recently released so we will soon close the public 6.8 branch. The current estimate for the branch closing is on Wed 16th of April 2025. After closing the 6.8 branch, the tqtc/lts-6.8 branches will be used instead. All module maintainers not working in The Qt Company will

[Development] [Announce] We released Qt Design Studio 4.7.1

We released Qt Design Studio 4.7.1 today, see https://www.qt.io/blog/qt-design-studio-4.7-released Big thanks to everyone involved! Best Regards, Thomas Hartmann ___ Announce mailing list annou...@qt-project.org https://lists.qt-project.org/listinfo/a

[Development] Nominating Moss Heim for approver rights

Hello Qt development I would like to nominate Moss Heim as an approver for the Qt project. Moss has been working as a Senior Engineer on QtWebEngine for over a year, with many contributions on Linux and the new webengine frame api, https://doc.qt.io/qt-6/ qwebengineframe.html[1] Authored chan

Re: [Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

On Friday, 4 April 2025 11:15:35 Pacific Daylight Time Thiago Macieira wrote: > BTW, I said we "have the same problem with QMetaType", but in reality we > don't because we take this into account. > friend bool comparesEqual(const QMetaType &lhs, > const QMetaType &

Re: [Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

On Friday, 4 April 2025 10:31:48 Pacific Daylight Time Giuseppe D'Angelo via Development wrote: > (I'm still unsure about _how_ the attribute works, specifically how does > it figure out the TU and thus the shared library in which to pin the > RTTI information?) I haven't looked at the patch, but

Re: [Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

On 04/04/2025 17:44, Thiago Macieira wrote: The conclusion from this is that, from the point of view of the C++ language, they*are* different types, even if they have the same mangling and can (and are) passed across library boundaries in by value, by pointer, in containers, etc. The big proble

Re: [Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

On Friday, 4 April 2025 08:07:27 Pacific Daylight Time Milian Wolff wrote: > Because if you do so, and the type is public (i.e. all-inline), then you > would not be able to safely put that into a `std::any` in one DSO and > extract it in another DSO. The worst thing is that this is only detectable

[Development] PSA: symbol visibility and export macros need to be re-thought for clang/libc++

Hey all, I recently learned that my understanding of how symbol visibility works, and how one is supposed to use the export macros we all know from Qt and KDE (and that I have used for the last ~20 years) is incorrect for clang/libc++. This is mostly a PSA at this stage only, as I cannot yet ac

Re: [Development] Nominating Moss Heim for approver rights

+1 from me (disclaimer: we work in the same team 🙂) Best, Michael From: Development on behalf of Allan Sandfeld Jensen Sent: Friday, April 4, 2025 2:41 PM To: Qt development mailing list Subject: [Development] Nominating Moss Heim for approver rights Hello Qt

Re: [Development] Nominating Moss Heim for approver rights

+1 Moss makes lots of reviews and always spots weak points in the build system area. Regards, Alexey Alexey Edelev Software Engineer Qt Group Erich-Thilo-Str. 10 12489 Berlin, Germany alexey.ede...@qt.io www.qt.io [https://s3.eu-north-1.amazonaws.com/email-signature-tool-

Re: [Development] Nominating Moss Heim for approver rights

Corrected links On Friday 4 April 2025 14:41:32 Central European Summer Time Allan Sandfeld Jensen wrote: > > Authored changes: > https://codereview.qt-project.org/q/owner:moss.h...@qt.io[1] > Reviews: > https://codereview.qt-project.org/q/reviewer:moss.h...@qt.io[2] > > Best regards, > Allan