[llvm-dev] LLVM pre-built installer package for windows

Paul Hancock via llvm-dev llvm-dev at lists.llvm.org
Mon Apr 17 15:59:04 PDT 2017

I know static linking is the desired/standard option for using LLVM, it's the same for the ubuntu/debian packages (about 400MB in usr/lib/llvm-4.0). I'm just wondering why there isn't a install package for windows where we already have clang, which would require the library to be built for windows anyway...

I definitely didn't mean dynamic linking as with a library like this you cant exactly change the library version without altering some of the using code anyway, making dynamic use mostly pointless...

- Paul

From: Reid Kleckner <rnk at google.com>
Sent: 18 April 2017 06:32
To: Paul Hancock
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] LLVM pre-built installer package for windows

No, we don't provide any pre-built packages with headers and libs.

The main reason is that LLVM is typically statically linked. Distributing the .libs bloats the size of the installation, which is already needlessly large due to statically linking LLVM into various executables. Providing an extra -dev package takes time and effort that we haven't spent.

On Sun, Apr 16, 2017 at 3:13 PM, Paul Hancock via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:

Just realised about this while upgrading my multi-platform project to 4.0.0, for linux you simply go "apt clang-x.x llvm-x.x-dev..." etc and off you go. However for windows the only pre-built install package seems to be clang, without the LLVM headers and such...

Do we have a installer package for windows that allows us to install the LLVM development headers+libraries (ie; the same thing as the ubuntu/debian packages but for windows) without having to do it manually with the source? If not is there any particular reason why?

- Paul

LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170417/bbbc606f/attachment-0001.html>

More information about the llvm-dev mailing list