Details
-
Bug
-
Resolution: Fixed
-
P3: Somewhat important
-
6.5.1
-
None
-
Windows
-
3412285e6 (dev), 716b9c643 (6.5)
Description
When following the instructions for building a debug version of PySide6 for Windows, the instructions fail to mention that the python setup.py build command line requires passing --debug to properly make a debug build. If you use a debug Python build and build without --debug, you get shiboken crashing without much information as to why the crash occurred:
-- Build files have been written to: C:/sources/hacking/pyside-setup/build/testenv_dvp/build/shiboken6
[INFO]: -- Compiling module shiboken6...
[87/89] Running generator for 'Shiboken'...
FAILED: shibokenmodule/mjb_rejected_classes.log shibokenmodule/Shiboken/shiboken_module_wrapper.cpp
cmd.exe /C "cd /D C:\sources\hacking\pyside-setup\sources\shiboken6\shibokenmodule && C:\sources\hacking\pyside-setup\build\testenv_dvp\build\shiboken6\.qfp\bin\shiboken_wrapper.bat C:/sources/hacking/pyside-setup/build/testenv_dvp/build/shiboken6/generator/shiboken6.exe --project-file=C:/sources/hacking/pyside-setup/build/testenv_dvp/build/shiboken6/shibokenmodule/shibokenmodule.txt"
ninja: build stopped: subcommand failed.
error: Error compiling shiboken6
Traceback (most recent call last):
File "c:\sources\hacking\pyside-setup\\setup.py", line 42, in <module>
setup_runner.run_setup()
File "c:\sources\hacking\pyside-setup\build_scripts\setup_runner.py", line 263, in run_setup
raise RuntimeError(msg)
RuntimeError:
setup.py invocation failed with exit code: 1.
This is fixed simply by adding --debug to the setup.py command line.