[6.1] Apply toolset's debugger
property in swift run
#8257
Merged
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.
Cherry-pick of #8252, merged as 88e2af7.
Explanation: Per SE-0378 toolsets can specify an optional
debugger
property, which so far had no effect. We should respect this property inswift run
invocations when any toolsets or Swift SDKs are selected.This allows running and debugging cross-compiled products in an environment other than the host, e.g. a container runtime when cross-compiled to Linux, QEMU or a firmware flasher and serial port setup script with Swift Embedded for microcontrollers, or in a Wasm runtime for a Wasm binary.
Scope: Only impacts
swift-run
when a toolset or a Swift SDK are selected.Risk: Low, due to limited scope and automated testing.
Testing: Added a new test cause to the existing XCTest suite.
Issue: rdar://143814083
Reviewer: @dschaefer2