Skip to content

Conversation

grynspan
Copy link
Contributor

The enable/disable testing library options are no longer used by swift build and can be removed.

The enable/disable testing library options are no longer used by `swift build`
and can be removed.
@grynspan
Copy link
Contributor Author

@swift-ci please test

@grynspan
Copy link
Contributor Author

@plemarquand Please confirm this won't break the VSCode plugin.

@plemarquand
Copy link
Contributor

LGTM, VS Code does a swift build --build-tests prior to doing a debug run, but isn't picky about building both test executables.

@grynspan grynspan enabled auto-merge (squash) July 17, 2024 14:13
@grynspan grynspan merged commit 7d0230b into main Jul 17, 2024
@grynspan grynspan deleted the jgrynspan/remove-test-options-from-swift-build branch July 17, 2024 15:58
grynspan added a commit that referenced this pull request Jul 17, 2024
grynspan added a commit that referenced this pull request Jul 18, 2024
…Testing enabled by default.) (#7789)

This PR refactors the previously-experimental Swift Testing support
logic so that only a single build product is produced when using both
XCTest and Swift Testing, and detection of Swift Testing usage is no
longer needed at compile time.

On macOS, Xcode 16 is responsible for hosting Swift Testing content, so
additional changes may be needed in Xcode to support this refactoring.
Such changes are beyond the purview of the Swift open source project.

This PR includes changes from the previous PRs numbered #7766, #7783,
#7784, and #7787.

Resolves rdar://120864035.

Co-authored-by: Pavel Yaskevich <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

command-line interface swift build Changes impacting `swift build`

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants