Add usage example of specifying the full path to the compiler used while building the debuggees for running the test suite.
llvm-svn: 148273
This commit is contained in:
parent
6ccbdcda36
commit
2e275c9e6a
|
@ -181,6 +181,7 @@ where options:
|
||||||
-A x86_64^i386 => launch inferior with x86_64 and i386 architectures
|
-A x86_64^i386 => launch inferior with x86_64 and i386 architectures
|
||||||
-C : specify the compiler(s) used to build the inferior executable
|
-C : specify the compiler(s) used to build the inferior executable
|
||||||
-C clang => build debuggee using clang compiler
|
-C clang => build debuggee using clang compiler
|
||||||
|
-C /my/full/path/to/clang => specify a full path to the clang binary
|
||||||
-C clang^gcc => build debuggee using clang and gcc compilers
|
-C clang^gcc => build debuggee using clang and gcc compilers
|
||||||
-D : dump the Python sys.path variable
|
-D : dump the Python sys.path variable
|
||||||
-a : don't do lldb Python API tests
|
-a : don't do lldb Python API tests
|
||||||
|
|
Loading…
Reference in New Issue