[Lldb-commits] [lldb] [lldb][docs] Fix the Windows Python build options (PR #225465)

[Jonas Devlieghere via lldb-commits]

================
@@ -275,16 +275,25 @@ test execution.
 
 LLDB's script interpreter plugins (for Python and  Lua) can be built as static
 or dynamic libraries. This is controlled by
-`LLDB_ENABLE_DYNAMIC_SCRIPTINTERPRETERS`, which defaults to `ON` on masOS and
+`LLDB_ENABLE_DYNAMIC_SCRIPTINTERPRETERS`, which defaults to `ON` on macOS and
 FreeBSD, and `OFF` everywhere else.
 
 `LLDB_ENABLE_PYTHON_LIMITED_API` makes LLDB use the Python
 [Limited API](https://docs.python.org/3/c-api/stable.html). It defaults to `ON`
-when using SWIG 4.2 or later.
+when using SWIG 4.2 or later, except in the following cases, where it defaults
+to `OFF`:
+
+- `LLDB_EMBED_PYTHON_HOME` is `ON`, which is the default on Windows. The two
+  options are mutually exclusive and setting both is a configure error.
+- SWIG is exactly 4.4.0 and Python is 3.13 or later, due to
+  [swig#3283](https://github.com/swig/swig/issues/3283). This combination is
+  also a configure error if `LLDB_ENABLE_PYTHON_LIMITED_API` is requested
+  explicitly.
 
 When both of these options are enabled, LLDB can use, and be used from, a
----------------
JDevlieghere wrote:

'When both of these options are enabled' is now ambiguous. The bullets just before it introduce LLDB_EMBED_PYTHON_HOME and say 'setting both is a configure error'.

https://github.com/llvm/llvm-project/pull/225465