-
Notifications
You must be signed in to change notification settings - Fork 746
Bindgen tries to generate bindings for methods even with --ignore-methods #826
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
Labels
Comments
@fitzgen emilio told me you are investigating this, but I don't see any issue open, nor any pr related, so I just open one in case we forget. This is a blocker for stylo, as far as I can see. |
Yeah, and the regressing PR is #770. I guess I can also look into it tomorrow. |
Thanks for filing this. First half of a fix is at #827. If I leave the
|
fitzgen
added a commit
to fitzgen/rust-bindgen
that referenced
this issue
Jul 20, 2017
This makes only generating certain kinds of items more robust, since we don't need to keep checking whether codegen is enabled for different kinds of items all over the place, and can do it the once. It should also reduce the number of items we have to consider in our various analyses for which we don't ultimately care about the answer. Fixes rust-lang#826
fitzgen
added a commit
to fitzgen/rust-bindgen
that referenced
this issue
Jul 20, 2017
This makes only generating certain kinds of items more robust, since we don't need to keep checking whether codegen is enabled for different kinds of items all over the place, and can do it the once. It should also reduce the number of items we have to consider in our various analyses for which we don't ultimately care about the answer. Fixes rust-lang#826
fitzgen
added a commit
to fitzgen/rust-bindgen
that referenced
this issue
Jul 20, 2017
This makes only generating certain kinds of items more robust, since we don't need to keep checking whether codegen is enabled for different kinds of items all over the place, and can do it the once. It should also reduce the number of items we have to consider in our various analyses for which we don't ultimately care about the answer. Fixes rust-lang#826
bors-servo
pushed a commit
that referenced
this issue
Jul 20, 2017
…not-to, r=emilio Only whitelist items for which we intend to generate bindings This means that we only need to check in one place, rather than at ever call site. This makes it so that we don't generate methods for the test case, but if I add the `--target` flag like in the original #826 test case, then I get a panic about an unknown ABI. I figure this change is worth landing now, and we can land the fix for the panic as a follow up. r? @upsuper
tmfink
pushed a commit
to tmfink/rust-bindgen
that referenced
this issue
Aug 4, 2017
This makes only generating certain kinds of items more robust, since we don't need to keep checking whether codegen is enabled for different kinds of items all over the place, and can do it the once. It should also reduce the number of items we have to consider in our various analyses for which we don't ultimately care about the answer. Fixes rust-lang#826
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Input C/C++ Header
Bindgen Invocation
Actual Results
Expected Results
This panics when the target is win32 because we don't support
thiscall
, while for other platforms, it doesn't panic, but it still generates a binding function for the method.RUST_LOG=bindgen
OutputThe text was updated successfully, but these errors were encountered: