feat(aspect): support toolchain feature external_include_paths #319
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When this feature is active, some include paths in `CompilationContext` are automatically moved to `external_includes`. This allows Bazel to pass them to the compiler via `-isystem` to silence compiler warnings for external headers. Resolves: #299
martis42
deleted the
support_toolchain_feature_external_include_paths
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When this feature is active, some include paths in
CompilationContextare automatically moved toexternal_includes. This allows Bazel to pass them to the compiler via-isystemto silence compiler warnings for external headers.DWYU is however only compatible to
external_include_pathsstarting from Bazel 7.0.0.Resolves: #299