Skip to content
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

Stop using Qt private API #25

Open
special opened this issue May 26, 2019 · 0 comments
Open

Stop using Qt private API #25

special opened this issue May 26, 2019 · 0 comments
Labels
enhancement New feature or request qt Qt/QML Frontend

Comments

@special
Copy link
Contributor

special commented May 26, 2019

The only use of private Qt API is QMetaObjectBuilder. If that is fixed, we can get proper ABI compatibility and not risk breakage as Qt moves forward.

The output of QMetaObjectBuilder is the moc-style metaobject structures. They aren't trivial, but the format is covered under Qt's ABI. If the code is extracted, it can be used safely.

There are some complications in pulling that out of Qt where it's using other private API, but none that seem insurmountable.

@special special added enhancement New feature or request qt Qt/QML Frontend labels May 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request qt Qt/QML Frontend
Projects
None yet
Development

No branches or pull requests

1 participant