Skip to content

Enable clang resource dir headers access for cppinterop's deployment #592

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

Closed
wants to merge 1 commit into from

Conversation

anutosh491
Copy link
Collaborator

@anutosh491 anutosh491 commented May 26, 2025

Description

This should fix the failing CI for cppinterop

Type of change

Please tick all options which are relevant.

  • Bug fix
  • New feature
  • Requires documentation updates

Testing

Please describe the test(s) that you added and ran to verify your changes.

Checklist

  • I have read the contribution guide recently

@anutosh491 anutosh491 marked this pull request as draft May 26, 2025 07:22
Copy link
Collaborator

@mcbarton mcbarton left a comment

Choose a reason for hiding this comment

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

I don't think we should be fetching this package as part of CppInterOps Emscripten build. The ci builds against the head of a release branch, and not a particular release. This could produce an inconsistency I believe (the package also seems to only be available for llvm 20 and not 19). My suggestion is this PR be modified to take advantage of this PR in xeus-cpp once its in compiler-research/xeus-cpp#312 (to be changed later today to clang_resource_dir instead of llvm_resource_dir), and point xeus-cpp in the ci towards the resource directory we already have.

@anutosh491
Copy link
Collaborator Author

Hey @mcbarton check my comment (the second comment) on the xeus-cpp . This was just a dummy PR showing why something like this won't work.

Thanks

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