[LLVMdev] Using 'llvm-build' for out-of-tree projects

[Alexey Samsonov]

On Tue, Jan 22, 2013 at 9:12 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:

> Jean-Daniel Dupas <devlists at shadowlab.org> writes:
>
> >> P.S. Weren't we planning on removing the Make-based build system in
> >> the next few months a year ago?
> >
> > It always lacks some important features, like building compiler-rt
> > with just-built clang: http://llvm.org/bugs/show_bug.cgi?id=14109
>

Yeah, using just-built clang would probably be a good feature, but for now
we
(sanitizer devs) "can live with" using a host compiler for building runtime
libraries
and maintaining both Clang and gcc builds.


>
> The configure&make build works on more homogeneous environments than
> CMake. Implementing the requirement you mention seems easy enough while
> using toolchains where clang/clang++ works as a drop-in replacement for
> the platform compiler (i.e. gcc/g++ on Linux). For the general case, it
> looks quite tricky.
>
> The feature can be implemented for the easy case (POSIX&gcc, which, most
> likely, is what everybody uses) and reject it for the rest.


> BTW, is compiler-rt integrated in the CMake LLVM/Clang build process, or
> is it a separate step?
>

It is integrated. Running "make", "make check-all" or "make install" in
your build
tree do compiler-rt related work as well. However, AFAIK there is little
CMake support
for building compiler-rt for various Apple platforms.


>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>



-- 
Alexey Samsonov, MSK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130123/1a004359/attachment.html>