diff options
| author | K900 <me@0upti.me> | 2024-01-17 11:26:21 +0300 |
|---|---|---|
| committer | K900 <me@0upti.me> | 2024-01-17 11:32:40 +0300 |
| commit | ee7012951002d6570e34e792497b29e40d75aba3 (patch) | |
| tree | 3aae57be50889d1239e8deab8157f356a2c95ba8 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | e73431e32fd87c693486c734cdb68bfb99a412bb (diff) | |
qt5, qt6: use versioned QML import paths in wrappers
Qt is smart enough to figure out the target Qt version for native plugins.
However, Qt is _not_ smart enough to figure out the target Qt version for
QML imports, which causes all kinds of funny breakage when you start running
Qt 5 applications from Qt 6 ones and vice versa.
So, do some minimally invasive surgery to make different Qt versions pick up
different QML import path variables, so they don't mess with each other.
This is kind of very cursed, but what can you do.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions