<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 7, 2015 at 6:38 PM, Greg Fitzgerald <span dir="ltr"><<a href="mailto:garious@gmail.com" target="_blank">garious@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm hoping to revive the LLD standalone CMake build. I'm new to this<br>
build but it looks like it borrowed code from an old version of<br>
compiler-rt, which I did some work on last year. Like compiler-rt,<br>
I'd like to get the LLD build up running with only CMAKE_PREFIX_PATH<br>
instead of defining custom variables like LLD_PATH_TO_LLVM_BUILD and<br>
LLD_PATH_TO_LLVM_SOURCE. Any objection to that?<br>
<br>
Also, two files ELFLinkingContext.cpp and MachOLinkingContext.cpp<br>
include a private header from the LLVM source tree,<br>
"llvm/Config/config.h" to get access to HAVE_CXXABI_H. Can the<br>
dependency on HAVE_CXXABI_H be removed? If no, mind if I add a<br>
config.h.cmake to LLD's "include/lld/Config"?<br></blockquote><div><br></div><div>I personally would be opposed to adding configure machinery to LLD's build. It is just duplicating the machinery already in LLVM.</div><div><br></div><div>-- Sean Silva</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Greg<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</blockquote></div><br></div></div>