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

Attempt to fix-up clang-cl support #56

Closed
wants to merge 2 commits into from
Closed

Attempt to fix-up clang-cl support #56

wants to merge 2 commits into from

Conversation

nagisa
Copy link
Member

@nagisa nagisa commented Aug 18, 2021

If the user specifies CC=... then the previous fallback to clang
would fail to work if clang wasn't in the path. This is quite likely
on Windows in particular.

Lets just drop the use of preprocessor on Windows and directly code the
one constant that the preprocessor was handling.

If the user specifies `CC=...` then the previous fallback to `clang`
would fail to work if `clang` wasn't in the path. This is quite likely
on Windows in particular.

Lets just drop the use of preprocessor on Windows and directly code the
one constant that the preprocessor was handling.
@nagisa
Copy link
Member Author

nagisa commented Aug 18, 2021

@mati865 would it be possible to test this change?

@nagisa nagisa force-pushed the nagisa/clang-cl branch 2 times, most recently from 378f44a to eaab651 Compare August 18, 2021 10:39
@nagisa nagisa closed this Aug 18, 2021
@nagisa nagisa deleted the nagisa/clang-cl branch August 18, 2021 10:51
@mati865
Copy link
Contributor

mati865 commented Aug 18, 2021

I cannot test MSVC but updated rust-lang/rust#87680, thanks in advance.

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