Index: www/build.html =================================================================== --- www/build.html +++ www/build.html @@ -116,14 +116,14 @@ the PYTHONHOME environment variable if it is specified).
cmake -G Ninja -DLLDB_TEST_DEBUG_TEST_CRASHES=1 -DPYTHON_HOME=C:\Python35 -DLLDB_TEST_COMPILER=d:\src\llvmbuild\ninja_release\bin\clang.exe ..\..\llvm
+ cmake -G Ninja -DLLDB_TEST_DEBUG_TEST_CRASHES=1 -DPYTHON_HOME=C:\Python35 -DLLDB_TEST_C_COMPILER=d:\src\llvmbuild\ninja_release\bin\clang.exe ..\..\llvm
Compiling with ninja
is both faster and simpler than compiling with MSVC, but chances are you still want
Index: www/test.html
===================================================================
--- www/test.html
+++ www/test.html
@@ -39,8 +39,8 @@
The easiest way to run the LLDB test suite is to use the check-lldb build
target. By default, the check-lldb target builds the test programs with
the same compiler that was used to build LLDB. To build the tests with a different
- compiler, you can set the LLDB_TEST_COMPILER CMake variable. It is possible to
- customize the architecture of the test binaries and compiler used by appending -A
+ compiler, you can set the LLDB_TEST_C_COMPILER or the LLDB_TEST_CXX_COMPILER CMake variables.
+ It is possible to customize the architecture of the test binaries and compiler used by appending -A
and -C options respectively to the CMake variable LLDB_TEST_USER_ARGS. For
example, to test LLDB against 32-bit binaries
built with a custom version of clang, do: