llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-lldb Author: Po-yao Chang (poyaoc97) <details> <summary>Changes</summary> LLDB_RELOCATABLE_PYTHON was removed in LLVM 11 (https://github.com/llvm/llvm-project/commit/3ec3f62f0a0b1ac13230922c91ffc988c1b1e8d5). --- Full diff: https://github.com/llvm/llvm-project/pull/81310.diff 1 Files Affected: - (modified) lldb/docs/resources/build.rst (+2-2) ``````````diff diff --git a/lldb/docs/resources/build.rst b/lldb/docs/resources/build.rst index 0ccfef32a601e1..55fe73c52f61aa 100644 --- a/lldb/docs/resources/build.rst +++ b/lldb/docs/resources/build.rst @@ -278,12 +278,12 @@ are commonly used on Windows. crash, rather than having to reproduce a failure or use a crash dump. * ``PYTHON_HOME`` (Required): Path to the folder where the Python distribution is installed. For example, ``C:\Python35``. -* ``LLDB_RELOCATABLE_PYTHON`` (Default=0): When this is 0, LLDB will bind +* ``LLDB_EMBED_PYTHON_HOME`` (Default=1 on Windows): When this is 1, LLDB will bind statically to the location specified in the ``PYTHON_HOME`` CMake variable, ignoring any value of ``PYTHONHOME`` set in the environment. This is most useful for developers who simply want to run LLDB after they build it. If you wish to move a build of LLDB to a different machine where Python will be in a - different location, setting ``LLDB_RELOCATABLE_PYTHON`` to 1 will cause + different location, setting ``LLDB_EMBED_PYTHON_HOME`` to 0 will cause Python to use its default mechanism for finding the python installation at runtime (looking for installed Pythons, or using the ``PYTHONHOME`` environment variable if it is specified). `````````` </details> https://github.com/llvm/llvm-project/pull/81310 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
