Change Details

The correct install directory is distro and arch specific, and should match the configuration of the python installation the binding is generated for. The directories can be queried using pythons distutils.sysconfig. In the unlikely case this does not match expectations, the directory can be overridden using -DGPB_PYTHON{2,3}_SITEARCH="<dir>".

The correct install directory is distro and arch specific, and should match the configuration of the python installation the binding is generated for. These directories can be queried using pythons distutils.sysconfig. When determining the install directory, it mimics the logic from KDE_INSTALL_USE_QT_SYS_PATHS. When the python PREFIX is the same as CMAKE_INSTALL_PREFIX, it defaults to using the path from distutils.sysconfig, otherwise it keeps the current scheme, installing below CMAKE_INSTALL_PREFIX. The default behaviour can be changed by setting KDE_INSTALL_PYTHON{2,3}DIR or by switching KDE_INSTALL_USE_PYTHON{2,3}_SYS_PATH ON or OFF.

The correct install directory is distro and arch specific, and should match the configuration of the python installation the binding is generated for. These directories can be queried using pythons distutils.sysconfig. When determining the install directory, it mimics the logic from KDE_INSTALL_USE_QT_SYS_PATHS. When the python PREFIX is the same as CMAKE_INSTALL_PREFIX, it defaults to using the path from The directories can be queried using pythons distutils.sysconfig.distutils.sysconfig, otherwise it keeps the current scheme, installing In the unlikely case this does not match expectations, the directory canbelow CMAKE_INSTALL_PREFIX. The default behaviour can be changed by setting KDE_INSTALL_PYTHON{2,3}DIR be overridden using -DGPBor by switching KDE_INSTALL_USE_PYTHON{2,3}_SITEARCH="<dir>"YS_PATH ON or OFF.