RFC: packaging for libtooling


I'm looking into packaging up everything you need (headers, libraries)
in order to make a refactoring tool using libtooling.

In the existing Windows packaging[1], you get what appears to me to be an
odd mix of items with no instructions for using them.

The Linux packaging[2][3] appears to give you almost everything I
expected to be there for libtooling.


1) Is this discrepency between platforms cooked into the CMake build
instructions, or is it an artifact of the way the builds are being created
for the LLVM download page? <http://llvm.org/releases/download.html&gt;

2) The LLVM download page contains a populated list for "Pre-built
Binaries:" and another unpopulated list named "Pre-built Binaries:"
after that. Where do I file a ticket on this to get it fixed?

3) Has anyone actually tried using the Linux package libraries and
headers to build a refactoring tool like remove-cstr-calls?

4) The share directory on the linux package only has a man page for
clang in it. Shouldn't the man pages for the other tools be included?

5) The linux package doesn't include any binaries for the "clang tools
extra" source package. Should these be included?

6) I was expecting a local copy of the doxygen to be included in the
docs folder, but it appears to only have a small handfull of manually
selected HTML files. Having a local copy of the doxygen is useful
because I can develop with reference documentation while disconnected
from the network (i.e. while on a plane or at a coffee shop without
wifi with my laptop). I can see how this is not relevant to an "end
user package" that just supplies you with the compiler. However, for
a developer of a refactoring tool, I think it's important to have in
some sort of package. Thoughts?

[1] <http://user.xmission.com/~legalize/tmp/clang/Windows-packaging.txt&gt;
[2] <http://user.xmission.com/~legalize/tmp/clang/Linux-packaging.txt&gt;
[3] <http://llvm.org/releases/3.4/clang+llvm-3.4-x86_64-unknown-ubuntu12.04.tar.xz&gt;