Bug: swift_import
depending on other swift_import
errors
#1461
Labels
type: bug
Something isn't working
swift_import
depending on other swift_import
errors
#1461
When using
swift_import
in Xcode 15-16 we noticed the.swiftinterface
files were trying to be found at theMacOSX
SDK root:Which then causes issues building downstream targets. This seems to only happen for
swift_import
targets that havedeps
which are otherswift_import
targets. One use-case of this we have is pre-compilingswift-syntax
where the built products are exposed asswift_import
targets.See #1460 for an example that reproduces the issue.
Examples
Sandboxed (Xcode 15.4.0)
Sanbodxed (Xcode 16.1.0)
Spawn strategy local (Xcode 15.4.0)
bazel clean --expunge && bazel build //test/fixtures/module_interface:client --spawn_strategy=local --xcode_version=15.4.0 INFO: Found 1 target... Target //test/fixtures/module_interface:client up-to-date: bazel-bin/test/fixtures/module_interface/client INFO: Elapsed time: 9.571s, Critical Path: 2.78s INFO: 43 processes: 13 internal, 30 local. INFO: Build completed successfully, 43 total actions
Spawn strategy local (Xcode 16.1.0)
This seems to be a regression only when
--spawn_strategy=local
and going from Xcode 15 -> Xcode 16 🙃The text was updated successfully, but these errors were encountered: