[llvm-dev] Is ist a good idea to use lit and other test tools for non llvm projects?

Danila Malyutin via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 29 02:33:18 PST 2019

It would be great if FileCheck could be decoupled from llvm and bundled with lit. Currently it causes friction for llvm-related projects that use lit for testing but don't actually require/depend on LLVM.

-----Original Message-----
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of whitequark via llvm-dev
Sent: Thursday, January 24, 2019 23:21
To: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Is ist a good idea to use lit and other test tools for non llvm projects?

On 2019-01-24 20:17, David Greene via llvm-dev wrote:
> alexp via llvm-dev <llvm-dev at lists.llvm.org> writes:
>> I have a project which uses llvm, but is (at least not yet) a 
>> contribution / not in the source tree of llvm.
>> Is it a good idea (e.g. instead of using boost test framework) to use 
>> the llvm testsuite related tools in this case?
> That probably depends on the project, but I've long wished LLVM's 
> testing tools were available outside of LLVM, packaged up separately 
> so they could be more widely used.  They're great tools!

lit is, in fact, packaged separately--it is available on PyPI.
FileCheck isn't; there is a similar tool on PyPI, called OutputCheck, which I have used extensively for similar jobs (matching compiler IR) but I like it much less than FileCheck.

LLVM Developers mailing list
llvm-dev at lists.llvm.org

More information about the llvm-dev mailing list