cargo: Forward cflags to bindgen via BINDGEN_EXTRA_CLANG_ARGS
#172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a crate invokes `bindgen` through a `build.rs` script to generate Rust code files, it should be using the headers that target Android rather than system headers. The include paths for these are already set up in the `cflags` that we pass to `cc-rs` (for `clang`), and can be trivially reused for `bindgen`'s `clang`.
manon-traverse
approved these changes
Jun 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a crate invokes
bindgenthrough abuild.rsscript to generate Rust code files, it should be using the headers that target Android rather than system headers. The include paths for these are already set up in thecflagsthat we pass tocc-rs(forclang), and can be trivially reused forbindgen'sclang.