[PySide] pyside build using pyenv-installed local Python fails, using system-installed Shiboken2 config/cmake file ?

[PGNet Dev]

On 2/27/20 8:02 AM, PGNet Dev wrote:
> fix bad /lib assumption (borrowing distro's lib64 patch, @ https://build.opensuse.org/package/show/KDE:Qt5/python3-pyside2),

apparently, that's NOT sufficient.  :-/

the install results in

tree /usr/local/lib/cmake/
	/usr/local/lib/cmake/
	├── [root            4096]  PySide2-5.14.1
	│   ├── [root             263]  PySide2Config.cmake
	│   ├── [root            1649]  PySide2Config.cpython-38-x86_64-linux-gnu.cmake
	│   ├── [root             479]  PySide2ConfigVersion.cmake
	│   ├── [root            3323]  PySide2Targets.cmake
	│   └── [root            1028]  PySide2Targets-release.cmake
	└── [root            4096]  Shiboken2-5.14.1
	    ├── [root             269]  Shiboken2Config.cmake
	    ├── [root            2846]  Shiboken2Config.cpython-38-x86_64-linux-gnu.cmake
	    ├── [root             479]  Shiboken2ConfigVersion.cmake
	    ├── [root            3261]  Shiboken2Targets.cmake
	    ├── [root            1391]  Shiboken2Targets-release.cmake
	    └── [root           20220]  shiboken_helpers.cmake


the goal/intent is that those should end up in 

	/usr/local/lib64/cmake/

for an install to PREFIX /usr/local

the Pyside config/build is a bit of a mess when it comes to proper/correct libdir=lib64 support; it appears to hardcode the =lib assumption in multiple locations ...