mkdoc: Work around a problematic deprecation_example header dep #15069
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 collecting the list of package headers, in the case of the deprecation example (which has no package library) we were ending up with two different copies of the header being passed to mkdoc:
The first one is the path we want -- the one used while compiling, and thus the one with a matching
-I
flag. The second one is a correct dependency, but not used for compiling, so does not have any matching-I
flag, so breaks mkdoc.Here, we customize our skylark header collection to ignore the second file.
(Note that #15066 and #15068 are also required for Bazel 4.1 builds to succeed.)
This change is