[PATCH] D34587: developer_guide: Tests need lnt in $PATH
Phabricator via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Mon Jun 26 19:49:47 PDT 2017
This revision was automatically updated to reflect the committed changes.
Closed by commit rL306356: developer_guide: Tests need lnt in $PATH (authored by matze).
Changed prior to commit:
https://reviews.llvm.org/D34587?vs=103813&id=104080#toc
Repository:
rL LLVM
https://reviews.llvm.org/D34587
Files:
lnt/trunk/docs/developer_guide.rst
Index: lnt/trunk/docs/developer_guide.rst
===================================================================
--- lnt/trunk/docs/developer_guide.rst
+++ lnt/trunk/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.104080.patch
Type: text/x-patch
Size: 893 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170627/f42ba1e2/attachment.bin>
More information about the llvm-commits
mailing list