Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Caching] Remove capture clang extra files #81389

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cachemeifyoucan
Copy link
Contributor

After removing the CASFS implementation for clang modules, there is no need to capture clang extra file that sets up the VFS for the clang modules since all content imported by ClangImporter is dependency scanned and available via include-tree.

Update the test to check that clang content found via -Xcc VFS options can currently work without capture the headermaps and vfs overlays.

After removing the CASFS implementation for clang modules, there is no
need to capture clang extra file that sets up the VFS for the clang
modules since all content imported by ClangImporter is dependency
scanned and available via include-tree.

Update the test to check that clang content found via `-Xcc` VFS options
can currently work without capture the headermaps and vfs overlays.
@cachemeifyoucan
Copy link
Contributor Author

This depends on a patch to remove CASFS based clang module implementation (currently conflicts due to some PR under review). Ideally, CASFS implementation needs to be removed first since that code path depending on collecting addition files from clang importer.

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