Skip to content

Driver: forwarding driver invocations to the new driver when SWIFT_USE_NEW_DRIVER is defined #34154

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

Merged
merged 1 commit into from
Oct 2, 2020

Conversation

nkcsgexi
Copy link
Contributor

@nkcsgexi nkcsgexi commented Oct 1, 2020

This allows us to experiment with the new swift-driver without changing build systems.

@nkcsgexi
Copy link
Contributor Author

nkcsgexi commented Oct 1, 2020

@swift-ci Please Build Toolchain macOS Platform

2 similar comments
@nkcsgexi
Copy link
Contributor Author

nkcsgexi commented Oct 2, 2020

@swift-ci Please Build Toolchain macOS Platform

@nkcsgexi
Copy link
Contributor Author

nkcsgexi commented Oct 2, 2020

@swift-ci Please Build Toolchain macOS Platform

@nkcsgexi
Copy link
Contributor Author

nkcsgexi commented Oct 2, 2020

@swift-ci please smoke test

…E_NEW_DRIVER is defined

This allows us to experiment with the new swift-driver without changing build systems.
@nkcsgexi nkcsgexi force-pushed the forward-call-new-driver branch from ef0de2a to 11b2251 Compare October 2, 2020 21:02
@nkcsgexi
Copy link
Contributor Author

nkcsgexi commented Oct 2, 2020

@swift-ci please smoke test

@nkcsgexi nkcsgexi merged commit a8c48d1 into swiftlang:main Oct 2, 2020
@nkcsgexi nkcsgexi deleted the forward-call-new-driver branch October 2, 2020 23:27
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