Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add PrivateFrameworks as additional Swift Testing framework path #1396

Merged
merged 1 commit into from
Feb 20, 2025

Conversation

plemarquand
Copy link
Contributor

This is essentially the same change made in:
swiftlang/swift-package-manager#8199

VS Code would be able to leverage it for regular runs with swift test but because when debugging we launch the xctest executable directly to run tests, we must include the same framework search paths as SPM.

This is essentially the same change made in:
swiftlang/swift-package-manager#8199

VS Code would be able to leverage it for regular runs with `swift test`
but because when debugging we launch the xctest executable directly to
run tests, we must include the same framework search paths as SPM.
@award999 award999 merged commit 5550413 into swiftlang:main Feb 20, 2025
16 checks passed
@award999
Copy link
Contributor

Verified 5550413

award999 pushed a commit that referenced this pull request Feb 20, 2025
This is essentially the same change made in:
swiftlang/swift-package-manager#8199

VS Code would be able to leverage it for regular runs with `swift test`
but because when debugging we launch the xctest executable directly to
run tests, we must include the same framework search paths as SPM.
@plemarquand plemarquand deleted the private-framework-path branch February 20, 2025 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants