[Development] moc output changes coming
Volker Hilsheimer
volker.hilsheimer at qt.io
Mon Nov 25 12:24:02 CET 2024
> On 14 Nov 2024, at 17:00, Thiago Macieira <thiago.macieira at intel.com> wrote:
>
> 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 else in qtscxml.
With all the changes merged into qtbase, my daily toplevel build where all submodules are checked out at origin/dev I’m now running into the following beauty when building qtopcua:
~~~/moc_qopcuanodeids.cpp(40): fatal error C1067: compiler limit: 64K limit on size of a type record has been exceeded
This is a debug build with VS2022, cl version 19.41.34123. The issue would probably not happen in a release build. gcc and clang seem to cope as well.
The type in question is https://doc.qt.io/qt-6/qopcua-nodeids.html#Namespace0-enum, which is massive and probably generated from a spec.
But if we do that kind of thing, then it’s probably a safe bet that clients will also generate meta-object relevant types from some spec or some other APIs (such as a COM type library or similar; hello ActiveQt, at least).
This will break the submodule update once the qtbase changes reach qtopcua, so P0 ticket at https://bugreports.qt.io/browse/QTBUG-131516
Volker
More information about the Development
mailing list