Skip to content

Allow setting the clang++ environment variable #1605

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 2 commits into from
May 14, 2024

Conversation

etcwilde
Copy link
Contributor

'+' isn't allowed in environment variable names so it's impossible to set the Clang++ executable at the moment. Replace + with X so that we can set SWIFT_DRIVER_CLANGXX_EXEC to set the clang++ executable.

Fixes: rdar://128007218

'+' isn't allowed in environment variable names so it's impossible to
set the Clang++ executable at the moment. Replace `+` with `X` so that
we can set `SWIFT_DRIVER_CLANGXX_EXEC` to set the clang++ executable.
@etcwilde etcwilde requested a review from artemcm May 13, 2024 16:33
@etcwilde
Copy link
Contributor Author

@swift-ci please test

Copy link
Contributor

@artemcm artemcm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanxx!

Could you please add a simple test for this env var causing the expected effect on tool lookup? There's some examples already, like testSwiftHelpOverride.

Check that the clang override environment variables actually do
something. Note that clang++ is only used to link on non-Darwin
platforms when the interop mode is swift-5.9.
@etcwilde
Copy link
Contributor Author

@swift-ci please test

@etcwilde
Copy link
Contributor Author

@swift-ci please test Windows

@etcwilde etcwilde merged commit dd5bbca into swiftlang:main May 14, 2024
3 checks passed
@etcwilde etcwilde deleted the ewilde/accept-clangxx-env-var branch May 18, 2024 18:48
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.

2 participants