diff options
author | Friedemann Kleint <Friedemann.Kleint@qt.io> | 2022-12-09 08:46:57 +0100 |
---|---|---|
committer | Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> | 2022-12-12 13:25:25 +0000 |
commit | 67a76b0a772d92c802836377e059a7e98a780947 (patch) | |
tree | 0f3b8f09743f5ea0f410a4dc25ea116ce3f6c10b | |
parent | 9fc6f33fd5024056d45825836ac037b736f5531e (diff) |
Documentation: Add some hints for debug builds on Windows
Change-Id: Ice4a0915cc5d53bf62d25f082318cff95c782856
Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
(cherry picked from commit e5f205b7272bcaa81b86d92e716cfa57a73bcb58)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
-rw-r--r-- | sources/pyside6/doc/gettingstarted/windows.rst | 15 | ||||
-rw-r--r-- | sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst | 2 |
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 |