Optionally generate a "C"-like header with imported items #100
Conversation
This file contains hidden or 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
Given syntex_syntax2 is a quite old parser, it doesn't support more recent syntax (especially macro expansions). This means API symbols created by macros using new features will not be tested. This allows a user to set abort_on_errors, and ctest will fail if the crate to be tested can't be parsed.
…tion' linker errors
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
While adding various bindings and now trying to refactor defining those with macros in
openssl-sysI wanted to check what functions I ended up importing (and their expected "C type"), and whether I lost or broke something.With this a separate C-like file can be generated in
build.rs(.out_items("items.h")) and e.g. printed in a separate binary with:This is mostly for debugging / "human" tracking of changes, so I don't see a need to test this.
I also hit a few other minor issues and added fixes, although they all should be independent.