Unfortunately, clang-cl only supports a very limited subset of CL's flags. And if you want to talk to clang directly you have to go through an extra layer of indirection by using -Xclang -flag. By using clang directly you get the whole power of clang without arbitrary limitations (and as a bonus you can now compiler your software on mac and linux).
Unfortunately, clang-cl only supports a very limited subset of CL's flags. And if you want to talk to clang directly you have to go through an extra layer of indirection by using -Xclang -flag. By using clang directly you get the whole power of clang without arbitrary limitations (and as a bonus you can now compiler your software on mac and linux).
I tried using clang-cl recently but it produced a ton of linker errors for basic math functions. Does that mean clang-cl does not provide its own libc? And is there some guide that explains various C options on windows?
"opting in" to VS 2017 is recommended when building Chrome for 64-bit Windows to get improved incremental linking support. (We still link Chrome on Windows with link.exe even when compiling with Clang.)
[+] [-] DannyBee|8 years ago|reply
Errr, use clang-cl, and "yes it is". That's the whole point of clang-cl :)
[+] [-] Leandros|8 years ago|reply
[+] [-] chris_wot|8 years ago|reply
[+] [-] bla2|8 years ago|reply
[+] [-] martell|8 years ago|reply
Disclaimer: I am a LLVM Engineer working on a mingw-w64 standalone clang :)
[+] [-] Leandros|8 years ago|reply
[+] [-] brian-armstrong|8 years ago|reply
[+] [-] johncolanduoni|8 years ago|reply
[+] [-] anta40|8 years ago|reply
Ouch...
[+] [-] dxf|8 years ago|reply
"opting in" to VS 2017 is recommended when building Chrome for 64-bit Windows to get improved incremental linking support. (We still link Chrome on Windows with link.exe even when compiling with Clang.)
[+] [-] Leandros|8 years ago|reply