[PATCH] D34587: developer_guide: Tests need lnt in $PATH

Matthias Braun via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Fri Jun 23 17:20:41 PDT 2017


MatzeB created this revision.
Herald added a subscriber: mcrosier.

Did I do something wrong or should we mention this bit in the docu?

Document the requirement that lnt needs to be in the $PATH to run the unit tests.


Repository:
  rL LLVM

https://reviews.llvm.org/D34587

Files:
  docs/developer_guide.rst


Index: docs/developer_guide.rst
===================================================================
--- docs/developer_guide.rst
+++ docs/developer_guide.rst
@@ -33,9 +33,10 @@
 The LNT regression tests make use of lit and other tools like FileCheck. At
 the moment, probably the easiest way to get them installed is to compile LLVM
 and use the binaries that are generated there. Assuming you've build LLVM
-into $LLVMBUILD, you can run the regression tests using the following command::
+into $LLVMBUILD, and installed lnt in $LNTINSTALL you can run the regression
+tests using the following command::
 
-     PATH=$LLVMBUILD/bin:$PATH llvm-lit -sv ./tests
+     PATH=$LLVMBUILD/bin:$LNTINSTALL/bin:$PATH llvm-lit -sv ./tests
 
 If you don't like temporary files being created in your LNT source directory,
 you can run the tests in a different directory too::


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D34587.103813.patch
Type: text/x-patch
Size: 863 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170624/725f7f79/attachment.bin>


More information about the llvm-commits mailing list