aboutsummaryrefslogtreecommitdiffstats
path: root/sources/pyside6
diff options
context:
space:
mode:
Diffstat (limited to 'sources/pyside6')
-rw-r--r--sources/pyside6/doc/gettingstarted/windows.rst15
-rw-r--r--sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst2
2 files changed, 17 insertions, 0 deletions
diff --git a/sources/pyside6/doc/gettingstarted/windows.rst b/sources/pyside6/doc/gettingstarted/windows.rst
index 5fec92bca..c80d0176c 100644
--- a/sources/pyside6/doc/gettingstarted/windows.rst
+++ b/sources/pyside6/doc/gettingstarted/windows.rst
@@ -75,6 +75,21 @@ Build can take a few minutes, so it is recommended to use more than one CPU core
python setup.py build --qtpaths=c:\path\to\qtpaths.exe --openssl=c:\path\to\openssl\bin --build-tests --ignore-git --parallel=8
+.. _creating_windows_debug_builds:
+
+Creating Debug Builds
+~~~~~~~~~~~~~~~~~~~~~
+
+* Choose *Custom Installation* when installing Python and tick the options for
+ debug binaries and libraries
+
+* Use ``venv`` to create a virtual environment and pass the debug binary:
+
+ python_d.exe -m venv testenv_d
+
+* Use ``python_d.exe`` to invoke ``setup.py``
+
+
Installing PySide
~~~~~~~~~~~~~~~~~
diff --git a/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst b/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst
index bb91b5b99..806035299 100644
--- a/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst
+++ b/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst
@@ -9,6 +9,8 @@ in a single session. With VSCode you would be able to do the following:
* Put breakpoints in both the Python and the C++ code.
* Step from Python to C++ code and vice versa.
+For Windows, see :ref:`creating_windows_debug_builds`.
+
Let's get started with setting up everything and debugging a Python process.
Setting the Python interpreter