diff options
Diffstat (limited to 'sources/pyside6/doc/tutorials/debugging/mixed_debugging.rst')
| -rw-r--r-- | sources/pyside6/doc/tutorials/debugging/mixed_debugging.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/sources/pyside6/doc/tutorials/debugging/mixed_debugging.rst b/sources/pyside6/doc/tutorials/debugging/mixed_debugging.rst index 82b34d919..85c326347 100644 --- a/sources/pyside6/doc/tutorials/debugging/mixed_debugging.rst +++ b/sources/pyside6/doc/tutorials/debugging/mixed_debugging.rst @@ -5,10 +5,10 @@ When debugging PySide code, very often you would also like to debug the corresponding C++ extension of the PySide module. This is done by attaching your debugger to the Python interpreter. In this tutorial, we are going to take you through a comprehensive guide in building Qt 6, using the built Qt 6 to build -PySide6, and then starting a debugging process in either Qt Creator or VSCode. +PySide6, and then starting a debugging process in either *Qt Creator* or VSCode. With VSCode, you should be able to see the combined call stacks for both C++ and -Python together. With Qt Creator, unfortunately you would only be able to +Python together. With *Qt Creator*, unfortunately you would only be able to debug the native C++ code of the PySide module; that is you won't be able to set breakpoints inside the Python code. @@ -74,7 +74,7 @@ Find the build system information `Qt 6 Build System .. code-block:: bash - cmake -GNinja -DMCAKE_BUILD_TYPE=Debug \ + cmake -GNinja -DCMAKE_BUILD_TYPE=Debug \ -DCMAKE_INSTALL_PREFIX=/path/to/install/Qt -DBUILD_qtwebengine=OFF .. cmake --build . --parallel cmake --install . @@ -101,7 +101,7 @@ Build PySide6 using the Qt 6 that you built earlier ---------------------------------------------------- Follow the steps mentioned `Getting Started - Qt for Python -<https://doc.qt.io/qtforpython/gettingstarted.html>`_ +<https://doc.qt.io/qtforpython/gettingstarted/index.html>`_ You may manually select the modules to install using the ``--module-subset`` cli argument for `setup.py`. This was my installation script @@ -116,7 +116,7 @@ It is recommended to use a Python virtual environment rather than installing in Debugging the process using your preferred IDE ---------------------------------------------- -The following sections guide you through the setup for Qt Creator or VSCode. +The following sections guide you through the setup for *Qt Creator* or VSCode. .. toctree:: :glob: |