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

Rust bindings potential issues when using bindgen #389

Closed
mundusnine opened this issue Jun 20, 2019 · 1 comment
Closed

Rust bindings potential issues when using bindgen #389

mundusnine opened this issue Jun 20, 2019 · 1 comment

Comments

@mundusnine
Copy link
Contributor

In reference to this I decided to test out how this could be done with kinc using bindgen

Notes from my tests:

  • While testing it out with Kore I had issues with the wrapper.h files where if display.h uses system.h but it is not yet found by the compilation it just errors out saying it can't find it. Basically, orderring of the *.h includes in the wrapper.h impacts compilation like normal compilation(it's using clang to parse source files). I believe that even with good ordering it may still be an issue(see last point).

  • While testing with Kinc, the KINC_FUNC def was not found and bindgen just errored out.

  • Bindgen seems to prefer single-file headers. In my tests I tried with the cute headers and generation went smoothly for most of the headers. Files that worked did not have includes.

@RobDangerous
Copy link
Member

I do not intend to use an automatic binding generator so none of this is an issue.

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

No branches or pull requests

2 participants