Simplify the paths to module maps generated by the Swift build rules. #560
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.
Since we pass these module maps directly to the compiler with
-fmodule-map-file
, we don't need them to be named exactlymodule.modulemap
, so the extra subdirectory is also unnecessary.This change also migrates generation of the modulemap file content for the generated header's module to the same code (
module_maps.bzl
) already used byswift_clang_module_aspect
, instead of having its own separate code path.PiperOrigin-RevId: 354324121
(cherry picked from commit 5f51ca9)