Author: asmith Date: Wed Feb 7 21:11:17 2018 New Revision: 324564 URL: http://llvm.org/viewvc/llvm-project?rev=324564&view=rev Log: [docs] Update docs for cmake options LLDB_TEST_C_COMPILER and LLDB_TEST_CXX_COMPILER
Summary: LLDB_TEST_COMPILER is not a valid option for CMake for LLDB. There are instead two properties LLDB_TEST_C_COMPILER and LLDB_TEST_CXX_COMPILER. Update the documents accordingly to reflect the correct information. Reviewers: zturner, lldb-commits Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D43061 Modified: lldb/trunk/www/build.html lldb/trunk/www/test.html Modified: lldb/trunk/www/build.html URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/www/build.html?rev=324564&r1=324563&r2=324564&view=diff ============================================================================== --- lldb/trunk/www/build.html (original) +++ lldb/trunk/www/build.html Wed Feb 7 21:11:17 2018 @@ -116,14 +116,14 @@ the PYTHONHOME environment variable if it is specified). </li> <li> - <b>LLDB_TEST_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. + <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. </li> </ul> Sample command line:<br/> - <code>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</code> + <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> <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 Modified: lldb/trunk/www/test.html URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/www/test.html?rev=324564&r1=324563&r2=324564&view=diff ============================================================================== --- lldb/trunk/www/test.html (original) +++ lldb/trunk/www/test.html Wed Feb 7 21:11:17 2018 @@ -39,8 +39,8 @@ The easiest way to run the LLDB test suite is to use the <tt>check-lldb</tt> build 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_COMPILER</strong> CMake variable. It is possible to - customize the architecture of the test binaries and compiler used by appending -A + compiler, you can set the <strong>LLDB_TEST_C_COMPILER</strong> or the <strong>LLDB_TEST_CXX_COMPILER</strong> 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 <strong>LLDB_TEST_USER_ARGS</strong>. For example, to test LLDB against 32-bit binaries built with a custom version of clang, do: _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
