[PATCH] D101479: [Driver] Support libc++ in MSVC

Adrian McCarthy via Phabricator via cfe-commits cfe-commits at lists.llvm.org
Tue May 11 08:35:42 PDT 2021


amccarth added a comment.

In D101479#2748475 <https://reviews.llvm.org/D101479#2748475>, @mstorsjo wrote:

> In D101479#2748189 <https://reviews.llvm.org/D101479#2748189>, @amccarth wrote:
>
>> In D101479#2733354 <https://reviews.llvm.org/D101479#2733354>, @mstorsjo wrote:
>>
>>> Not sure if we want the desicion between static and shared libc++ be coupled with `/MT` and `/MD`, as one can quite plausibly want to use e.g. a static libc++ with `/MD`.
>>
>> I don't understand this.  When would someone want to use `/MD` and not get the DLL version of the run-time libraries?
>
> Whether one wants to link against the CRT statically or dynamically, and libc++ statically or dynamically, are two entirely separate things. I would e.g. expect that Chrome is built with a statically linked libc++ but linked against the dynamic CRT.

Ah, thanks for explaining that!  In the VC++ stack, `/MD` and `/MT` make the DLL/static choice for the CRT, the C++ standard library, and the compiler runtime.[1]  It never occurred to me that someone might want to select these independently.

[1]:  https://docs.microsoft.com/en-us/cpp/c-runtime-library/crt-library-features?view=msvc-160


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D101479/new/

https://reviews.llvm.org/D101479



More information about the cfe-commits mailing list