Skip to content

Added a new getSingleFrontendInvocationFromDriverArgumentsV4 function. #1852

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

Conversation

cwakamo
Copy link
Contributor

@cwakamo cwakamo commented Mar 23, 2025

This variant adds a compilerExecutableDir parameter which gets passed along to the Driver during initialization. This allows callers of getSingleFrontendInvocationFromDriverArgumentsV4 to set a custom compilerExecutableDir, which influences paths passed to the frontend for things like the in-process plugin library.

This addresses rdar://problem/147692019.

This variant adds a `compilerExecutableDir` parameter which gets passed along to the `Driver` during initialization.
This allows callers of `getSingleFrontendInvocationFromDriverArgumentsV4` to set a custom `compilerExecutableDir`, which influences paths passed to the frontend for things like the in-process plugin library.

This addresses <rdar://problem/147692019>.
@cwakamo cwakamo added the enhancement New feature or request label Mar 23, 2025
@cwakamo cwakamo requested a review from artemcm March 23, 2025 23:37
@cwakamo cwakamo self-assigned this Mar 23, 2025
@cwakamo
Copy link
Contributor Author

cwakamo commented Mar 23, 2025

@swift-ci please test

@cwakamo cwakamo merged commit 3d5347b into swiftlang:main Mar 24, 2025
3 checks passed
@cwakamo cwakamo deleted the eng/PR-147692019-getSingleFrontendInvocationFromDriverArguments-compilerExecutableDir-arg branch March 24, 2025 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants