<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Le 21 juin 2012 à 11:34, Manuel Klimek a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: arial, helvetica, sans-serif"><font size="2"><div class="gmail_quote">On Thu, Jun 21, 2012 at 10:43 AM, Charles Davis <span dir="ltr"><<a href="mailto:cdavis@mymail.mines.edu" target="_blank">cdavis@mymail.mines.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><div class="h5"><div>On Jun 20, 2012, at 6:19 PM, Chandler Carruth wrote:</div>
<br><blockquote type="cite"><div style="font-family:arial,helvetica,sans-serif"><font size="2"><div class="gmail_quote" style="font-size:12px">On Wed, Jun 20, 2012 at 5:13 PM, Nick Lewycky <span dir="ltr"><<a href="mailto:nlewycky@google.com" target="_blank">nlewycky@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><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><div><br></div><div>There are definitely missing features in cmake. I'm actually working on adding one of them: support for compiler-rt. There are likely some others.</div>
<div><br></div><div>That said, I actually agree -- I think that cmake, while ugly, can be made to support all of our use cases. There are some use cases that autoconf+make can't support, so I'd rather we just pick cmake and bang on it until it works the way we want.</div>
</div></font></div></blockquote></div></div>Now hold on there. I thought Daniel was supposed to be working on a new build system, based almost entirely in Python, specifically because he thought CMake was, uh... inadequate (to say the least). I've CC'd him in the hopes of getting his opinion.</div>
</div></blockquote><div><br></div><div>I'd be interested what about CMake is inadequate. The way CMake is used in llvm seems somewhat suboptimal, but I don't see how doing the same thing in python would be better ...</div>
<div><br></div><div>(not saying that cmake is perfect)</div></div></font></div></blockquote><div><br></div><div>It never was about writing a build system in python to replace existing one, it was about unifying the way (libraries) dependencies are expressed in LLVM by cmake and configure/make.</div></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-- Jean-Daniel</div><div><br></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>