Skip to content

Conversation

rherilier
Copy link

The resource directory is always retrieved from the system's default clang compiler instead of the targeted one.

I notice it after removing clang from my system (which is an alias for clang-16) while keeping clang-19 installed.

@MaskRay
Copy link
Owner

MaskRay commented Dec 1, 2024

I download prebuilt Clang packages on https://releases.llvm.org/download.html then set CMAKE_PREFIX_PATH to the root directory of the extracted tarball. ``Clang_EXECUTABLE` will respect that.

clang-${Clang_VERSION_MAJOR} will not work if the distribution only provides clang but not something like clang-19.

@rherilier
Copy link
Author

Thanks, I did not expect any differences between Windows and UNICES builds...

…ompiler

The resource directory was always retrieved from the system's default clang
compiler instead of the targeted one.
@rherilier rherilier force-pushed the fix-call-to-wrong-clang branch from 50d001c to 84b3c69 Compare December 6, 2024 16:09
@MaskRay MaskRay force-pushed the master branch 3 times, most recently from e403622 to cfc7c02 Compare August 15, 2025 06:45
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