diff options
| -rwxr-xr-x | lldb/www/build.html | 5 | ||||
| -rw-r--r-- | lldb/www/test.html | 2 |
2 files changed, 5 insertions, 2 deletions
diff --git a/lldb/www/build.html b/lldb/www/build.html index 2965bb2ed2a..fd35b5116ba 100755 --- a/lldb/www/build.html +++ b/lldb/www/build.html @@ -119,11 +119,12 @@ <b>LLDB_TEST_C_COMPILER</b> or <b>LLDB_TEST_CXX_COMPILER</b>: The test suite needs to be able to find a copy of clang.exe that it can use to compile inferior programs. Note that MSVC is not supported here, it <strong>must</strong> be a path to a clang executable. Note that using a release clang.exe is strongly recommended here, as it will make the test suite run much faster. - This can be a path to any recent clang.exe, including one you built yourself. + This can be a path to any recent clang.exe, including one you built yourself. These variables are ignored unless the respective + <strong>LLDB_TEST_USE_CUSTOM_C_COMPILER</strong> and <strong>LLDB_TEST_USE_CUSTOM_CXX_COMPILER</strong> are set to ON. </li> </ul> Sample command line:<br/> - <code>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</code> + <code>cmake -G Ninja -DLLDB_TEST_DEBUG_TEST_CRASHES=1 -DPYTHON_HOME=C:\Python35 -DLLDB_TEST_USE_CUSTOM_C_COMPILER=ON -DLLDB_TEST_C_COMPILER=d:\src\llvmbuild\ninja_release\bin\clang.exe ..\..\llvm</code> <h2>Working with both Ninja and MSVC</h2> <p> Compiling with <code>ninja</code> is both faster and simpler than compiling with MSVC, but chances are you still want diff --git a/lldb/www/test.html b/lldb/www/test.html index 3d814c6ca29..5a771fd179d 100644 --- a/lldb/www/test.html +++ b/lldb/www/test.html @@ -40,6 +40,8 @@ target. By default, the <tt>check-lldb</tt> 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 <strong>LLDB_TEST_C_COMPILER</strong> or the <strong>LLDB_TEST_CXX_COMPILER</strong> CMake variables. + These variables are ignored unless the respective <strong>LLDB_TEST_USE_CUSTOM_C_COMPILER</strong> and + <strong>LLDB_TEST_USE_CUSTOM_CXX_COMPILER</strong> are set to ON. 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 <strong>LLDB_TEST_USER_ARGS</strong>. For example, to test LLDB against 32-bit binaries |
