<div dir="ltr"><div>Only my first question (the one about CMake) was answered. Would someone be willing to answer my other questions so I can understand & pursue that route instead?<br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Aug 12, 2013 at 2:19 PM, Matthew O'Connor <span dir="ltr"><<a href="mailto:thegreendragon@gmail.com" target="_blank">thegreendragon@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hi all,<br><br></div>I'm in the process of creating a new LLVM project based on the instructions from <a href="http://llvm.org/docs/Projects.html" target="_blank">http://llvm.org/docs/Projects.html</a>.<br>
<br></div>I have a bunch of questions:<br><br> 1. What is the relationship between CMake and the configure + Makefile build systems for LLVM? If I intend to just use configure + Makefile, do I need to worry about any of the CMake stuff?<br>
</div><br> 2. My first attempt was to copy the sample project, tweak the autoconf stuff, and remake. I ended up getting the follow error:<br> llvm[2]: Linking Release+Asserts executable exe (without symbols)<br> llvm/Release+Asserts/lib/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':<br>
Process.cpp:(.text+0x525): undefined reference to `setupterm'<br> Process.cpp:(.text+0x52e): undefined reference to `has_colors'<br></div> It appears that the sample project doesn't contain a library dependency on vterm. In comparing the autoconf in sample with the one at the parent of LLVM, the sample one doesn't contain references to vterm. Is this intentional?<br>
<br></div> 3. I decided to go the "simple" route of just hardcoding a Makefile that includes a Makefile.common that I wrote that hardcode defines LLVM_SRC_ROOT, LLVM_OBJ_ROOT, etc.<br></div> When I did this, I got an error about a missing configure, so I added one. My next build complained about a missing config.status, so I added one. Neither of them do anything.<br>
</div> At this point, I was able to build my library & tool without any issues. <br></div> Is the intention that only configure exists in the source repository and that running it creates the config.status script?<br>
</div> Is the intention of the config.status script that it recreates a configuration based on how it was configured?<br><br></div> 4. I find all of the autoconf stuff somewhat confusing & overwhelming. I'd like to find a simpler configure script that does the appropriate variable substitution in my Makefile.common. Is there a reasonable example of that? Or would it be better to learn how to properly generate the autoconf configure scripts?<br>
<br>Thanks,<br>Matthew<br><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div>
</blockquote></div><br></div>