Skip to content

Conversation

zmiklank
Copy link
Contributor

@zmiklank zmiklank commented Jul 3, 2025

Dynamically discover the Clang resource directory path by calling clang -print-resource-dir.

This fixes build failures on systems where the Clang include path is not in a location relative to the LLVM library directory (e.g., /usr/lib vs. /usr/lib64). The discovered path is passed to the C++ code as a preprocessor definition, making the solution generic.

Dynamically discover the Clang resource directory path by calling `clang
-print-resource-dir`.

This fixes build failures on systems where the Clang include path is not
in a location relative to the LLVM library directory (e.g., `/usr/lib`
vs. `/usr/lib64`). The discovered path is passed to the C++ code as a
preprocessor definition, making the solution generic.

Signed-off-by: Zuzana Miklankova <[email protected]>
@zmiklank zmiklank marked this pull request as draft July 3, 2025 10:47
@zmiklank
Copy link
Contributor Author

zmiklank commented Jul 3, 2025

Problem with this patch is that the upstream builder image does not seem to contain any system-wide clang installation.

@zmiklank zmiklank closed this Jul 25, 2025
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.

1 participant