Building PySide6 with development install
-
I am currently building PySide6 version 6.6.2. My build script is
#!/bin/bash
rm -rf ./build
rm -rf ./install
conda activate $HOME/conda_deps_lin64
export LLVM_INSTALL_DIR=/usr/lib/llvm-18
python setup.py install
--qtpaths=$HOME/conda_deps_lin64/lib/qt6/bin/qtpaths
--parallel=80
--prefix $HOME/pyside-setup/install
--limited-api=yes
--no-qt-toolsI'm building on a big Linux Ubuntu machine. I'm building from source because I need to wrap some custom tools and I need a build with headers and .cmake files. I have not found a wheel in any version of PySide6 > 6.1 that includes the development environment.
Even when I build from source the install process is not including the cmake files. Any suggestions on what I'm missing to get a full development install?
Thanks,
Karl -
Hi,
AFAIK, it's not a supported use case (meaning having a full development setup of Qt provided as a wheel).
What exactly are you trying to wrap ?
How are you trying to wrap it ? -
Hi,
AFAIK, it's not a supported use case (meaning having a full development setup of Qt provided as a wheel).
What exactly are you trying to wrap ?
How are you trying to wrap it ?@SGaist To be clear, I'm trying to build PySide6. I have a C++ Qt application that embeds Python. I have a couple of custom C++widgets that I want to wrap with PySide6 and expose to users.
Also, with PyQt5, the global qApp from the C++ application was returned was returned from QApplication.instance(). Now both PySide6 and PyQt6 create a separate new instance. I would like a method to return the QApplication instance from the C++ application. This should allow parenting of PySide widgets in the C++ application.
If there is an alternative way to do this, I'm open to suggestions. I want to support both Linux and Windows
Karl
-
It looks like build/qfpa-py3.12-qt6.6.2-64bit-release/install contains the include, cmake, and share directories. I will do some testing with these files and maybe I can build my local conda recipe to copy the files to where they ought to be and do the wrapping in my build pipeline.