Simplify clang vs clang++ selection process when compiling sources #20712
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Base the choice solely on whether
emcc
orem++
was used on the command line. This means that the handling C vs C++ input files will now simply match that of the underlying compiler.When running
clang
there is automatic language selection at the lower level such that thatclang -c file.cc
will run with-x c++
internally andclang -c file.c
will run with-x c
internally.The situation with
clang++
(and nowem++
) is a bit different in that runningclang++
on.c
input file not automatically use C mode and will generate a warning:Previously we were hiding the warning but using
clang
internally even if the user ran withemc++
.