![]() ![]() I was building all dependencies with Clang, so was passing "-s compiler=clang" The only difference between clang and clang-cl is the default way they accept command line arguments - otherwise, they are the same, so both commands will link with MSVC libs / dlls. If you check the list in your link, most of the components are "complete" or "mostly complete". Same for the entire Windows SDK, and so on. You will always mix binaries with clang on windows - for example, clang doesn't reimplement the MSVC runtime, it uses the libraries / DLLs provided by MSVC. So I am not sure is it really safe to mix Clang-compiled and MSVC-compiled libraries ATM. It would be also consistent with how most projects detect that they are compiled with MSVC. This change would allow any compiler which claims to be compatible with the given MSVC version to be used. (currently, this step isn't necessary, because as I described in Missing MSVC version checks in conanbuildinfo.cmake #1838, the MSVC version checks are incomplete and pass even when they shouldn't)
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |