-
Notifications
You must be signed in to change notification settings - Fork 20
Genbindings on Qt 6.8.1 errors #152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I might just make a branch with my changes because I am looking at switching to aqt so that you can target specific versions. I don't know if that would be beneficial or not, but I found it easier to use aqt when I am building software consuming |
Thanks for trying this out! This level of problem is pretty normal for changing the Qt version, it will take a few attempts of adding typedefs and allowlist changes, but it should be solveable. The KnownEnums thing looks correct to me, i'm not sure yet why it didn't work. As some other workarounds, can you try making it a KnownTypedef to I would like to keep generating miqt against 6.4 headers (or even older 6.2 - #139). Qt has forwards ABI compatibility, a binary compiled against older Qt 6.4 headers can successfully use a newer Qt 6.8 dll/so library at runtime. This gives all the benefits of Qt's latest internal improvements and bugfixes, while still allowing users with an older "system qt" (i.e. Linux distros) to still run a release binary. The only downside is missing bindings for any newly introduced functions. A middle ground would be to generate these separately into some additional (e.g.) qt68 directory. If aqt can install multiple Qt versions side-by-side that would be really interesting. |
Cross-referencing #112 for the last attempt to upgrade genbindings to scan the Qt 6.7 headers, |
Thanks mappu, aqt can install multiple versions side by side, I'll change my branch to target the older version of Qt from #139 and see if aqt install works as expected. Which version of 5.x would you ideally like to support? |
5.15. My reasoning was based on what version of Qt is shipped in supported distros - although it's true that Ubuntu 20.04 is still supported while offering only Qt 5.12, I think in 2025, it's more than enough to draw the line at Qt 5.15. |
With 6.8.3No issues with GenerationManjaro/Arch stuff
Possibly Manjaro/Arch stuffSome private headers are in
|
I noticed that the
genbindings
script is running against the latest qt6 available in bookworm which at this point in time appears to be 6.4.2.With the work being done in #118 to update for clang 19, I figured it may be worth seeing if Qt6.8.1 has any issues in genbindings as well.
Here is my modified
genbindings.Dockerfile
. I have switched to usingaqtinstall
to install Qt and just for this test, removed the Qt5 buildergenbindings.Dockerfile
genbindings.Dockerfile
cmd/genbindings/config-allowlist.go
cmd/genbindings/config-allowlist.go
cmd/genbindings/config-libraries.go
cmd/genbindings/config-libraries.go
When I run
make genbindings
I get the following errors now:/opt/Qt/6.8.1/gcc_64/include/QtCore/qabstracteventdispatcher.h:35:13: error: no type named 'TimerId' in namespace 'Qt'
/opt/Qt/6.8.1/gcc_64/include/QtCore/qabstractitemmodel.h:150:26: error: no type named 'strong_ordering' in namespace 'Qt'
And then some issues cascading downstream from those.
I have tried (as you can see above) to add
Qt::TimerId
toKnownEnums
but it hasn't seemed to have done anythingI'm finding this library super helpful so I am trying to find ways to help contribute so I appreciate any help you give me
make genbindings log
make genbindings log
The text was updated successfully, but these errors were encountered: