<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 20, 2012, at 5:13 PM, Nick Lewycky <<a href="mailto:nlewycky@google.com">nlewycky@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family:arial,helvetica,sans-serif"><font><div>Is there anybody who is certain that our autoconf dependency needs to stay around? Are there developers stuck on systems that don't have a recent enough cmake in their most recent release, or maybe are using some features from configure+make that the cmake build system doesn't implement?</div>
<div><br></div><div>If nobody pipes up, I might actually try actually removing it!</div></font></div></blockquote><br></div><div>I think this is premature, although I consider it a worthy goal. Right now, the only motivation we have for removing "configure+make" is that we don't like having two build systems, but that's not good enough.</div><div><br></div><div>Some things that CMake needs to do well for it to become the only way to build LLVM/Clang:</div><div> - Optionally build and install compiler-rt </div><div> - Optionally build and install libc++</div><div> - Ease-to-use cross-compilation support</div><div> - Documentation to make it easy to understand how to do the above</div><div> - LLDB?</div><div> - LLVM testsuite support</div><div><br></div><div>And some value-add that might make CMake motivating for others:</div><div> - Easy bootstrap</div><div> - Build packages/installers</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><br></body></html>