Just did a build with and without Clang. The difference comes out to about 12MiB, actually -- 69MiB for LLVM, and 81MiB for LLVM+Clang. 12MiB is, incidentally, the size of the /usr/libexec/clang-cc file you mentioned, so that's basically all the size difference. Attached is a PKGBUILD which builds LLVM+Clang, comment out the mv line from build() to build only LLVM. On Mon, Oct 26, 2009 at 7:37 PM, Ranguvar <ranguvar@archlinux.us> wrote:
Sorry, no idea what you're talking about in that first paragraph? Where is the PKGBUILD? And what do you mean by scan-* wrappers?
On Mon, Oct 26, 2009 at 7:16 PM, Tobias Kieslich <tobias@justdreams.de>wrote:
Thanks,
I posted my llvm-clang-svn PKGBUILD in AUR, not all of the things made it into the actual build. I like to have all scan-* wrappers included as they are handy and depend on each other (scan-build -V invokes scan-view automatically after a test build). They PKGBUILD is in the comments of the package.
If you look at the llvm binaries provided you'll see the clang package is bigger than the gcc stuff. However, the way they package it makes me think it might be trick to separate clang from llvm but it sure is worth a try.
-T
On Mon, 26 Oct 2009, Ranguvar wrote:
Very well, I'll make a prototype PKGBUILD that has sections for each install and then post it here, good luck :)
I do think it odd though that Clang would be larger than GCC, I guess we'll have to see.