Please note that COMPILER_RT_CAN_EXECUTE_TESTS is still OFF, so this only affects stuff when everything is ready to flip the switch.
Details
Diff Detail
Event Timeline
Two things:
- Should we add -o to clang-cl? MSVC ignores it silently, and CMake
always uses it when it does its initial test compile.
- Should we even use clang-cl when building compiler-rt? Do we have lots
of CFLAGS in compiler-rt? We will either have to expose them as core
clang-cl options, or switch to the regular clang driver. Do you need this
to handle /MT or /MD?
cmake/Modules/AddCompilerRT.cmake | ||
---|---|---|
140 | There cannot be a space between -Fo and its argument. =/ |
- Should we add -o to clang-cl?
MSVC ignores it silently, and CMake always uses it when it does its initial test compile.
I don't see any reasons not to do that.
- Should we even use clang-cl when building compiler-rt? Do we have lots of CFLAGS in compiler-rt?
We will either have to expose them as core clang-cl options, or switch to the regular clang driver.
Do you need this to handle /MT or /MD?
I think we can start using clang-cl as a secondary compiler building c-rt so we have extra test coverage, but stick with CL as a primary compiler until we declare clang-cl production-quality.
CMakeLists.txt | ||
---|---|---|
65 | Ah, good idea -- I forgot about the "OBJ" possibility :) | |
cmake/Modules/AddCompilerRT.cmake | ||
140 | What Reid says. |
_OUT makes no sense to me. You can probably use EXE/OBJ instead.