<div dir="ltr">I haven't stared deeply at LLDB's usage of make, but I think adding CMake to the mix is a step in the wrong direction. CMake isn't a make replacement, it's a meta-build system and autoconf replacement. Once you generate build files, you'll still have an external dependency on some other build system (ninja or msbuild).<div>
<br></div><div>Aren't most LLDB test programs simple enough to be linked with something like the lit shell interpreter?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 18, 2014 at 3:55 PM, <span dir="ltr"><<a href="mailto:jingham@apple.com" target="_blank">jingham@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is mostly historical. So long as I don't have to do it, I don't really mind one way or the other. OTOH, beware, this sort of thing is sticky...<br>
<br>
Jim<br>
<div class=""><br>
<br>
> On Jul 18, 2014, at 3:47 PM, Zachary Turner <<a href="mailto:zturner@google.com">zturner@google.com</a>> wrote:<br>
><br>
> I'm not very well versed in MAKE, but an issue I'm encountering currently is the use of MAKE in compiling the test files. Is there any reason CMake can't be used here? There's a lot of shell-specific logic in the Makefile currently that is hard to reproduce on Windows, so if we can port everything to CMake it might be helpful.<br>
><br>
> Thoughts?<br>
</div>> _______________________________________________<br>
> lldb-dev mailing list<br>
> <a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev</a><br>
<br>
_______________________________________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev</a><br>
</blockquote></div><br></div>