Priority: P2: Important
Affects Version/s: 5.15.3, dev, 6.0.4
Fix Version/s: None
Commits:e641c225d2954cfc5c85e00eda83f5319c84b3c8 (pyside/pyside-setup/dev) bff7791ce35c2da1c56f5a73ffb85c0778ec50cb (pyside/pyside-setup/6.0) 6cc3c07431ede5cb2487b09d4725b54f014a64d2 (pyside/tqtc-pyside-setup/5.15)
The option --reuse-build is used very often to save time.
When Python files of a PySide source tree are changed, this change will show up in the produced package, but when PySide is executed, it is hard to predict, if your Python
changes have an effect or not.
Reason: The Python files which are living in Shiboken are not only living in the source tree.
In order to have them available even in unfortunate directory layouts,
they are also embedded in a .zip file, which is embedded into the libshiboken module.
Recently, I saw some worried developers which use PySide in other products, who could
not find the effect of their debug changes to some Python file. This is not only an
annoyance, but can seriously distort the success of development. I was hit quite much
by this effect, recently.
Embedding is a nice thing, but it can turn into a nightmare, when you always need
to re-build a lot in order to test a small change to a Python script.
By adding the right dependencies, this old error source is finally evicted.
|For Gerrit Dashboard: PYSIDE-1536|
|341821,9||cmake: add dependencies to rebuild libshiboken embedded files||dev||pyside/pyside-setup||Status: MERGED||+2||0|
|342077,3||cmake: add dependencies to rebuild libshiboken embedded files||6.0||pyside/pyside-setup||Status: MERGED||+2||0|
|342081,5||cmake: add dependencies to rebuild libshiboken embedded files||tqtc/lts-5.15||pyside/tqtc-pyside-setup||Status: MERGED||+2||0|
|344495,2||cmake: add dependencies to rebuild libshiboken embedded files, addendum||6.0||pyside/pyside-setup||Status: MERGED||+2||0|
|344628,2||cmake: add dependencies to rebuild libshiboken embedded files, addendum||dev||pyside/pyside-setup||Status: MERGED||+2||0|