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

Hi LLVM-folks,

is there a way to use the llvm-build tool for out-of-tree projects?
Makefile.rules supposes llvm-build to be located in PROJ_SRC_ROOT and this
does not hold for out-of-tree projects, the same applies to
Makefile.llvmbuild that is searched for in PROJ_OBJ_ROOT. I think
PROJ_SRC_ROOT should be replaced by LLVM_SRC_ROOT and PROJ_OBJ_ROOT should
be replaced by LLVM_OBJ_ROOT, right?

Ciao, Fabian
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130122/a2f31c1e/attachment.html>

Hi Fabian,

 > is there a way to use the llvm-build tool for out-of-tree
projects?
> Makefile.rules supposes llvm-build to be located in PROJ_SRC_ROOT and this
does
> not hold for out-of-tree projects, the same applies to Makefile.llvmbuild
that
> is searched for in PROJ_OBJ_ROOT. I think PROJ_SRC_ROOT should be replaced
by
> LLVM_SRC_ROOT and PROJ_OBJ_ROOT should be replaced by LLVM_OBJ_ROOT, right?
for an out-of-tree build you can use llvm-config to get include paths and so on.
I don't think there is any point bothering with llvm-build for this case.

Ciao, Duncan.

On 22 Jan 2013, at 12:04, Duncan Sands wrote:
> for an out-of-tree build you can use llvm-config to get include paths and
so on.
> I don't think there is any point bothering with llvm-build for this
case.
CMake works nicely for out-of-tree projects.  I have an optimiser plugin that
builds this way.  I'm not sure if it's fixed now, but the autoconf
builds used to not install the CMake plugins, which was a problem if packagers
decided to use autoconf.

David

P.S. Weren't we planning on removing the Make-based build system in the next
few months a year ago?