[lldb-dev] Prebuilt binary for Windows
Vadim Chugunov via lldb-dev
lldb-dev at lists.llvm.org
Thu Jan 19 18:57:00 PST 2017
I don't know an easy way to accomplish that. While app-local deployment is
now supported, the set of deployed dlls depends on the host OS version
(according to this
<https://blogs.msdn.microsoft.com/vcblog/2015/03/03/introducing-the-universal-crt/>).
I've opened a bug <http://llvm.org/bugs/show_bug.cgi?id=31699> for now.
On Thu, Jan 12, 2017 at 4:12 PM, Reid Kleckner <rnk at google.com> wrote:
> On Thu, Jan 12, 2017 at 10:18 AM, Vadim Chugunov via lldb-dev <
> lldb-dev at lists.llvm.org> wrote:
>
>> I was referring to this: https://support.microsof
>> t.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows.
>> Granted, it was probably marked as non-critical, so some users may have
>> skipped it.
>>
>> > One of the redist options is to include an MSU in your installer that
>> tells Windows Update to add UCRT to the list of components it updates
>>
>> We should figure out how to do that.
>>
>> But meanwhile, do people here agree that LLVM should be built with the
>> /MD flag?
>>
>
> We should do whatever makes it really simple to add clang to path and run
> it without any DLL conflicts. If it's easy to copy the vc runtime DLLs into
> our package in a compatible way, great, so long as users can unzip the
> package and run it from whereever it is without installing any
> dependencies. Static linking just happens to be the easiest way to achieve
> that.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20170119/4d5b67df/attachment.html>
More information about the lldb-dev
mailing list