https://github.com/poyaoc97 created https://github.com/llvm/llvm-project/pull/81310
LLDB_RELOCATABLE_PYTHON was removed in LLVM 11 (https://github.com/llvm/llvm-project/commit/3ec3f62f0a0b1ac13230922c91ffc988c1b1e8d5). >From 756cb44e6965f1a01b2f9512f8e60d02eee14e8c Mon Sep 17 00:00:00 2001 From: Po-yao Chang <poyao...@gmail.com> Date: Sat, 10 Feb 2024 03:43:19 +0800 Subject: [PATCH] [LLDB][Docs] Replace LLDB_RELOCATABLE_PYTHON with LLDB_EMBED_PYTHON_HOME LLDB_RELOCATABLE_PYTHON was removed in LLVM 11. --- lldb/docs/resources/build.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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). _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
