| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
The root of the repo should stay clean,
at the moment we have too many things around.
It makes more sense to move these scripts to the tools
directories.
Change-Id: Ieca26107dafddfffa2a8dc5b9bb41e9942e0ebfa
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
| |
Copying wrapped lines in terminals is challenging on older Windows.
Change-Id: Ic756c20ecdce9767900d5a99a58afd3da81034c2
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
|
|
|
|
|
|
| |
"Debugging Tools" were once shipped as separate packages
and might still be installed on older machines.
Change-Id: Ice2cee4e9f995f6020502990bccf6f66721cb51e
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
This script can be used to find out why PySide2 modules
fail to load with various DLL errors like:
- Missing DLL
- Missing symbol in DLL
You can think of it as a Windows version of ldd / LD_DEBUG.
Underneath it uses the cdb.exe command line debugger, and the
gflags.exe tool, both installed with the latest Windows Kit.
The aim is to ask users to run this script when they encounter
PySide2 imports not working on Windows.
The user should then provide the generated log file.
Incindentally it can also be used for any Windows executables,
not just Python.
Consider adapting it to work on Linux and macOS as well
(using LD_DEBUG and something similar on macOS).
Change-Id: Ic7ef37ffd0565495e0774e4db3fc509090607af2
Reviewed-by: Christian Tismer <tismer@stackless.com>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
