[cfe-dev] Difficulties preparing libtooling based workshop

[Richard]

In article <CACs=tyLv3xa6T=7SjcZobRzkdcXPW8U3zris_HwyXScYjAAT8g at mail.gmail.com>,
    Reid Kleckner <rnk at google.com> writes:

> In particular, I don't want to distribute a whole pile of static libraries
> in the standard toolchain build of LLVM and Clang.
> 
> There are a couple of ways to avoid it, both of which require work:
> 1. Split into a libLLVM.dll, clang.dll, and clangTooling.ll
> 2. Create a separate installation with the usual static libraries
> 
> IMO doing 1 is the best, because then we can shrink the installation
> footprint even further by avoiding 4 copies of a statically linked clang:
> clang.exe, clang-cl.exe, clang++.exe, and msbuild-bin/cl.exe
> 
> The problem is that there's no easy way to just blithely export everything
> on Windows like we would do on Linux, and we don't have any existing
> annotations for our C++ APIs.

This is something I can contribute longer-term.  I'll take a look at
what's necessary for doing it.

In the meantime, I'm going to look into a means for packaging headers
and standard libraries for a refactoring tool separate from the
existing package for clang.
-- 
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
     The Computer Graphics Museum <http://ComputerGraphicsMuseum.org>
         The Terminals Wiki <http://terminals.classiccmp.org>
  Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>