[PySide] Packaging PySide2 for Fedora
hobbes1069 at gmail.com
Mon Mar 25 14:18:16 CET 2019
On Mon, Mar 25, 2019 at 4:46 AM Alexandru Croitor <alexandru.croitor at qt.io>
> I assume you're still trying to use the setup.py route, and not the cmake
I made a copy my RPM spec file and started changing things over to CMake...
Maybe I missed it but I see cmake and pkgconf config files installed for
shiboken that I don't remember seeing using the setuptools method...
shiboken2 binary is not needed at runtime, just while building, or for
> end-users that want to create their own bindings.
Ok maybe I need to restate... The python files installed: Are they only
used by the shiboken binary? Or are there other consumers? The reason this
is important is that I can either bundle the shiboken2 binary with the
python files in one package "shiboken2" or if there are other consumers of
the python library/module I need to package it in "python3-shiboken2".
> support folder is needed for runtime.
For shiboken2, correct? So it would be part of the -devel package. What I
mean by "runtime" is other applications running (not building) such as
> To try and make the --root option work for you, i'd suggest invoking
> setup.py multiple times manually, for each project respectively.
> setup.py build --internal-build-type=shiboken2 --reuse-build .....
> setup.py install --root .... --internal-build-type=shiboken2 --reuse-build
> setup.py build --internal-build-type=shiboken2-generator --reuse-build
> setup.py install --root .... --internal-build-type=shiboken2-generator
> --reuse-build ....
> setup.py build --internal-build-type=pyside2 --reuse-build .........
> setup.py install --root .... --internal-build-type=pyside2 --reuse-build
I may try that but right now I'm thinking the cmake option may be easiest.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the PySide