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

Use gir-parser #1577

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Use gir-parser #1577

wants to merge 1 commit into from

Conversation

bilelmoussaoui
Copy link
Member

Switch from the in-house gir files parsing to a separate crate I built. It uses quick-xml internally.

For now this is capable of generating almost all gtk bindings, most of the failures are arrays related.

let parent = elem
.attr("parent")
.map(|s| self.find_or_stub_type(ns_id, s));
let parent = elem.parent().map(|s| self.find_or_stub_type(ns_id, s));
let typ = Type::Class(Class {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of using custom types for these things, could we move over to just using directly the types provided by your parser?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would require a huge amount of changes to be done before doing the switch. I rather do that as a second step and my intention for now is to make the gir types wrappers of the ones from the types provided by the parser + TypeId + fields for overrides the type sets

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants