yep, that is why I posted the bit of the call stack and cmake saying it was using python 2.7. ( I've seen cmake produce erroneous output so not sure it that is really happening ). There is no PySide2 in Fedora, there are py2 and py3 versions of it , I have both installed. It is possible that cmake is not picking the right one.Look at your call stack. You have a mix-up of Py2 and Py3 which is not going to work. Apparently the problem is the existence of PySide which is built for Py2. You have to un-install it completely and instead install PySide2.
Code: Select all
dnf search pyside Last metadata expiration check: 0:02:49 ago on Tue 08 Oct 2019 13:25:29 BST. ================================================= Name & Summary Matched: pyside ================================================== pyside-tools.x86_64 : Development tools for PySide pyside-tools.x86_64 : Development tools for PySide python2-pyudev-pyside.noarch : PySide integration for pyudev python-pyside-devel.x86_64 : Development files for python-pyside python-pyside-devel.i686 : Development files for python-pyside python-pyside-devel.x86_64 : Development files for python-pyside ====================================================== Name Matched: pyside ======================================================= python2-pyside.x86_64 : Python bindings for Qt4 python3-pyside.x86_64 : Python bindings for Qt4 python2-pyside.i686 : Python bindings for Qt4 python2-pyside.x86_64 : Python bindings for Qt4 python3-pyside.i686 : Python bindings for Qt4 python3-pyside.x86_64 : Python bindings for Qt4 ===================================================== Summary Matched: pyside ===================================================== python2-QtAwesome.noarch : FontAwesome icons in PyQt and PySide applications python3-QtAwesome.noarch : FontAwesome icons in PyQt and PySide applications bash-4.4#dnf install python3-pyside python2-pyside python-pyside-devel Last metadata expiration check: 0:04:15 ago on Tue 08 Oct 2019 13:25:29 BST. Package python3-pyside-1.2.4-7.fc29.x86_64 is already installed. Package python2-pyside-1.2.4-7.fc29.x86_64 is already installed. Package python-pyside-devel-1.2.4-7.fc29.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete!
dub has done some nice work on adding coolant stuff. How hard would it be to make this read and write the tooltables without causing serious breakage? It seems to be mostly basic UI changes, this probably should not present much of a problem to work on py2.Nevertheless, if someone runs into a Py2 or Qt4 problem that can be easily fixed I am still open to make a fix for it.
I'm not sure what you are suggesting here, but if it is that I start messing with the carefully crafted parallel installation of py2 and py3 libs that Fedora devs have put together, that's a no-no. I don't mind having an experimental dev version of FC, but I'm not allowed to undermine the stability of the system as a whole just to make it build.The problem is that the executable "python" on most systems still points to python2. You have to manually change this entry to python3.
If the manual change means the cmake option, I did that but it does not seem to be picking up this one instance where it is still pulling in py 2.7 code.
I need to understand exactly why the python 2.7 stuff is getting linked when the relevant py3 versions are in place. I suspect cmake has not been set up properly or is assuming a Debian* specific configuration which does not work on other distros.
Code: Select all
I didyou could always ask in the install / compile part of the forum: https://forum.freecadweb.org/viewforum.php?f=4