<div dir="ltr">Actually I'm wrong. llvm-lit is automatically put into the bin directory by CMake itself. You don't have to run ninja at all. </div><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 13, 2017 at 11:44 AM Vedant Kumar <<a href="mailto:vsk@apple.com">vsk@apple.com</a>> wrote:<br></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"><div><blockquote type="cite"><div>On Sep 13, 2017, at 11:43 AM, Zachary Turner <<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>> wrote:</div><br class="m_-783839424469874869Apple-interchange-newline"><div><div dir="ltr">s/run this lit target manually/run this CMake target manually (e.g. `ninja llvm-lit`)/</div></div></blockquote><div><br></div></div></div><div style="word-wrap:break-word"><div>Great, thanks!</div></div><div style="word-wrap:break-word"><div><br></div><div>vedant</div></div><div style="word-wrap:break-word"><div><br><blockquote type="cite"><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 13, 2017 at 11:42 AM Zachary Turner <<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">llvm-lit is already put into <output-tree>/bin by CMake.<div><br></div><div>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><div class="gmail_quote"><div dir="ltr">On Wed, Sep 13, 2017 at 11:39 AM Vedant Kumar <<a href="mailto:vsk@apple.com" target="_blank">vsk@apple.com</a>> wrote:<br></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">Thanks for working on this.<div><br></div><div>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><br></div><div><br><div></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div>On Sep 13, 2017, at 9:19 AM, Zachary Turner via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="m_-783839424469874869m_813577795380368818m_2725101164844892610Apple-interchange-newline"><div><div dir="ltr">Hi all, I've got <a href="https://reviews.llvm.org/D37756" target="_blank">https://reviews.llvm.org/D37756</a> up for review currently which simplifies a lot of the logic in our lit config files.<div><br></div><div>For most people, this will be completely transparent and "just work", but it breaks one workflow that people should be aware of.</div><div><br></div><div>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><br></div><div>Luckily, there's an easy fix:</div><div><br></div><div>Solution: Run <output-tree>/bin/llvm-lit.py <source-root>/<path-to-test-file></div></div></div></blockquote><div><br></div></div></div></div><div style="word-wrap:break-word"><div><div><div>Will llvm-lit.py be added to <output-tree>/bin, or is this supposed to be <output-tree>/bin/llvm-lit?</div><div><br></div><div>vedant</div><br><blockquote type="cite"><div></div></blockquote></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>Happy to answer any questions here or on the code review.</div></div></div></blockquote></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div>
_______________________________________________<br>LLVM Developers mailing list<br><a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br></div></blockquote></div><br></div></div></blockquote></div></blockquote></div>
</div></blockquote></div><br></div></blockquote></div>