<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 13, 2017, at 11:43 AM, Zachary Turner <<a href="mailto:zturner@google.com" class="">zturner@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">s/run this lit target manually/run this CMake target manually (e.g. `ninja llvm-lit`)/</div></div></blockquote><div><br class=""></div>Great, thanks!</div><div><br class=""></div><div>vedant</div><div><br class=""><blockquote type="cite" class=""><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Sep 13, 2017 at 11:42 AM Zachary Turner <<a href="mailto:zturner@google.com" class="">zturner@google.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">llvm-lit is already put into <output-tree>/bin by CMake.<div class=""><br class=""></div><div class="">There is a CMake target called `llvm-lit` that will generate the <output-dir>/bin/llvm-lit script. If you built only a few specific llvm targets such as FileCheck, etc then you may need to run this lit target manually. If you just run "ninja" for example, or "ninja check-llvm", it's automatically generated.</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Sep 13, 2017 at 11:39 AM Vedant Kumar <<a href="mailto:vsk@apple.com" target="_blank" class="">vsk@apple.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Thanks for working on this.<div class=""><br class=""></div><div class="">One question: do you know what's the fastest way to create a working <output-tree>/bin/llvm-lit program? By 'working', I mean: assuming I've already built llvm-config and the relevant test dependencies (FileCheck, opt, etc), I can run llvm-lit on a single test.</div><div class=""><br class=""></div><div class=""><br class=""><div class=""></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Sep 13, 2017, at 9:19 AM, Zachary Turner via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="m_813577795380368818m_2725101164844892610Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi all, I've got <a href="https://reviews.llvm.org/D37756" target="_blank" class="">https://reviews.llvm.org/D37756</a> up for review currently which simplifies a lot of the logic in our lit config files.<div class=""><br class=""></div><div class="">For most people, this will be completely transparent and "just work", but it breaks one workflow that people should be aware of.</div><div class=""><br class=""></div><div class="">Problem: If you run lit by putting llvm-config in your path and then running <source-root>/utils/lit/lit.py <source-root>/<path-to-test-file> then this is not going to work anymore.</div><div class=""><br class=""></div><div class="">Luckily, there's an easy fix:</div><div class=""><br class=""></div><div class="">Solution: Run <output-tree>/bin/llvm-lit.py <source-root>/<path-to-test-file></div></div></div></blockquote><div class=""><br class=""></div></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class="">Will llvm-lit.py be added to <output-tree>/bin, or is this supposed to be <output-tree>/bin/llvm-lit?</div><div class=""><br class=""></div><div class="">vedant</div><br class=""><blockquote type="cite" class=""><div class=""></div></blockquote></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Happy to answer any questions here or on the code review.</div></div></div></blockquote></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div></blockquote></div>
</div></blockquote></div><br class=""></body></html>