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 libclang include path in tests #252

Merged
merged 5 commits into from
Sep 11, 2024
Merged

Conversation

jnikula
Copy link
Owner

@jnikula jnikula commented Sep 8, 2024

Sort out C header stuff, update Docker images, and stop asking clang for the header search path during testing. This is no longer an issue with the current images.

Add the supported and upcoming releases.
Remove the EOL releases.
This is the package for C headers.
Split out the _Bool/bool tests and run them in C only. They're
problematic in C++ because they depend on stdbool.h, and specifically on
GCC version of it which defines _Bool bool for C++. This is problematic
on Alpine Linux which uses musl, as well as on macOS.

Annoyingly the anonymous struct names also change.
This reverts commit a114bf7 ("test: query system include args from
clang").

This is no longer an issue with any of the current Docker images, and
with the C/C++ includes sorted out. We should try to trust libclang to
have the header search path right.
@jnikula jnikula changed the title Test use libclang include path Use libclang include path in tests Sep 8, 2024
Copy link
Collaborator

@BrunoMSantos BrunoMSantos left a comment

Choose a reason for hiding this comment

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

This looks great!

Sorry it took me a while to start reviewing these, but I'm back now. Should be going over the following PRs soon as well :)

@jnikula jnikula merged commit 1243852 into master Sep 11, 2024
5 checks passed
@jnikula jnikula deleted the test-use-libclang-include-path branch September 11, 2024 12:59
@jnikula
Copy link
Owner Author

jnikula commented Sep 11, 2024

This looks great!

Sorry it took me a while to start reviewing these, but I'm back now. Should be going over the following PRs soon as well :)

Don't worry about it, and thanks for going through them!

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