[llvm-dev] Is ist a good idea to use lit and other test tools for non llvm projects? (original) (raw)
whitequark via llvm-dev llvm-dev at lists.llvm.org
Thu Jan 24 12:20:38 PST 2019
- Previous message: [llvm-dev] Is ist a good idea to use lit and other test tools for non llvm projects?
- Next message: [llvm-dev] Is ist a good idea to use lit and other test tools for non llvm projects?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
-- whitequark
- Previous message: [llvm-dev] Is ist a good idea to use lit and other test tools for non llvm projects?
- Next message: [llvm-dev] Is ist a good idea to use lit and other test tools for non llvm projects?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]