[LLVMdev] RFC: LLVM Release Documentation Changes

[Brooks Davis]

On Sat, Feb 26, 2011 at 10:50:23PM +0000, Renato Golin wrote:
> On 25 February 2011 22:46, Bill Wendling <wendling at apple.com> wrote:
> > Duncan brought up the question of how to release clang. It would be nice to package clang by itself without all of the LLVM tools. Basically, making it a standalone package. I have no problem with this (in fact, I think it's a great idea), but it does mean changing Makefiles and stuff. Any help with this would be greatly appreciated.
> 
> Hi Bill,
> 
> We were discussing exactly that this week. With Clang inside LLVM's
> tree, it's hard for us to create separate (internal) products for
> them, so we can build and test them separately (EDG+LLVM against
> Clang+LLVM). But I'm not sure we're the most common types of users...
> 
> I believe the Debian package for Clang is separate from LLVM, which
> makes sense, but that might be hard to produce, given that they're too
> tightly coupled... Debian maintainers would know more... ;)

We're doing separate builds in the FreeBSD ports collection.  You have
to have the LLVM source try around and we configure against the whole
tree, but we can build against and installed version of llvm with only a
few hacks.  The basic process is:

- extract llvm and clang sources.
cd <llvm-src-root>
./configuire <args>
ln -s ${PREFIX}/include/llvm/Intrinsics.gen <llvm-src-root>/include/llvm
cd utils/unittest/googletest
gmake
cd <llvm-src-root>/tools/clang
gmake
gmake install

The need to build googletest is relatively recent.  Oddly, if you just
install libGoogleTest.a as part of the LLVM package build you get build
errors.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110301/7fac90a2/attachment.sig>