Hello Christoph,
On 3/27/20 7:06 PM, ic...@gmx.net wrote:
Hi,
I'm seeing you are tagging the linux binary release with the manylinux1
tag. However, when importing PySide2 on the manylinux1 docker container,
it fails saying GLIBCXX_3.4.18 not found. So I assume you are
pragmatically advertising the manylinux1 tag to be able to upload binary
releases to pypi. I appreciate this - having to build PySide2 before
installing would limit the usability a lot.
You are right, it's not 100% a manylinux1,
you can find some comments about it here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/build_scripts/wheel_override.py#n130
However, this imposes a problem when trying to release python extensions
depending on the PySide2 extension. May I ask, which system you are
actually using to build PySide2 - I assume it is the same system which
is used to build the qt libraries itself?
I totally understand,
and hopefully we can work on this, even adopt a new scheme like
manylinux2014, but at the moment it's still in our backlog.
We are generating the wheels in Qt's CI, and particularly on RHEL7,
which is the minimum requirement to build Qt.
If you have more questions,
let us know.
Cheers
--
Dr. Cristian Maureira-Fredes
R&D Manager
The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
_______________________________________________
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside
