Rather then requiring the user to specify runtime the compiler
runtime and C++ standard library, or trying to guess them which is
error-prone, use auto-detection by parsing the compiler link output.
Details
Details
- Reviewers
beanz vitalybuka rnk
Diff Detail
Diff Detail
- Repository
- rCRT Compiler Runtime
Event Timeline
Comment Actions
This got reverted because MSVC cl doesn't support --print-libgcc-file-name so the runtime check broke. Now we check if that option is supported prior to using it.
Comment Actions
So after testing this on Windows, I found out it was actually -### that's breaking. The problem is that I cannot use check_c_compiler_flag because -### breaks CMake so I have to use compiler detection instead, clang-cl also seems to be refusing both -### and -print-libgcc-file-name so disabling both on Windows. Let me know if you have any other idea on how to address this.