[llvm-dev] Different ways of running lit

[Jonathan Roelofs via llvm-dev]

On 9/11/17 10:48 AM, David Blaikie via llvm-dev wrote:
> I often run, from my build tree: "./bin/llvm-lit -v 
> test/DebugInfo/whatever.ll" (where the "test/DebugInfo/whatever.ll" only 
> exists in the source tree, not in the build tree where I'm running the 
> command from)

I do this a lot too.

@zturner: this is what I was trying to explain on IRC the other day. For 
whatever reason, this setup is the easier one to get working for a new 
testsuite, and the `./bin/llvm-lit /abs/path/to/test.ll` one is harder 
(it can't find the site.cfg for the cases where I've done it).


Jon

> 
> On Sun, Sep 10, 2017 at 10:33 PM Zachary Turner via llvm-dev 
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> 
>     What are all the different ways people run lit?  I'm doing some
>     refactoring and want to make sure I have all the based covered. 
>     Obviously you can use check-llvm.  And you can also run llvm-lit.py
>     in your bin directory and point it to your source tree.
> 
>     What else?  Both of the aforementioned methods require running cmake
>     first, is there any use case where someone runs lit without having
>     run cmake first?  Or anything else I'm not thinking of?
>     _______________________________________________
>     LLVM Developers mailing list
>     llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>     http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
> 
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 

-- 
Jon Roelofs
jonathan at codesourcery.com
CodeSourcery / Mentor Embedded / Siemens