[Runtimes] handle incremental builds that have non nested swiftmodules #82937
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.
Before #82571, we would generate a binary swiftmodule file at
<build folder>/<module>.swiftmodule
, while now in the same location we generate a directory.Trying an incremental run on top of a build folder generated with the old logic will fail during configuration with an error similar to
To reduce churn in CI and at desk, delete such remnant from the previous logic.
Addresses rdar://155466197