need help on setup of qtvcp
- cmorley
- Offline
- Moderator
-
- Posts: 7869
- Thank you received: 2125
linuxcnc@linuxcnc99:/usr/lib/python2.7/dist-packages/qtvcp/designer/x86_64$ ll /usr/lib/x86_64-linux-gnu/qt5/plugins/designer/libpyqt5_py2.so
-rw-rw-r-- 1 linuxcnc linuxcnc 31648 Jul 8 2018 /usr/lib/x86_64-linux-gnu/qt5/plugins/designer/libpyqt5_py2.so
This says you have libpyqt5_py2.so in the right place but it doesn't tell me what version (they are all named the same)
I has to be the same version of QT on the system, which I believe for you is 5.7
Please Log in or Create an account to join the conversation.
- Reinhard
- Offline
- Platinum Member
-
- Posts: 508
- Thank you received: 94
I tried that like thisI see he sets the path for the library with:
export PYQTDESIGNERPATH='/path/to/plugin/directory/'
export PYQTDESIGNERPATH='/usr/lib/python2.7/dist-packages/qtvcp/plugins'
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
- Posts: 7869
- Thank you received: 2125
#from qtvcp.plugins.widgets_plugin import *
#from qtvcp.plugins.dialog_plugin import *
Then you shouldn't need the svg library (you'll be missing lots of widgets)
Please Log in or Create an account to join the conversation.
- Reinhard
- Offline
- Platinum Member
-
- Posts: 508
- Thank you received: 94
designer starts without linuxcnc widgets, but shows the plugin as loaded (empty).
Konsole logs different errors on startup of designer:
designer -qt=5
Error while reparenting!
Designer: Bei der Erzeugung von Widgets wurden widersprüchliche Klassennamen festgestellt: Die Factory für benutzerdefinierte Widgets der Klasse KDialog gab ein Widget der Klasse QDialog zurück.
QMetaProperty::read: Unable to handle unregistered datatype 'SelectionBehavior' for property 'QTabBar::selectionBehaviorOnRemove'
Next I gonna try a mint installation ...
Please Log in or Create an account to join the conversation.
- Reinhard
- Offline
- Platinum Member
-
- Posts: 508
- Thank you received: 94
I could follow the instructions until building of PyQt5, which failed (on a fresh debian install from virtualbox) with
In file included from sippyrcccmodule.cpp:24:0:
sipAPIpyrcc.h:24:0: error: unterminated #ifndef
#ifndef _pyrccAPI_H
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:80:6: error: ‘sipTypeDef_pyrcc_RCCResourceLibrary’ was not declared in this scope
&sipTypeDef_pyrcc_RCCResourceLibrary.ctd_base,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:140:1: error: ‘sip_qt_metaobject_func’ does not name a type
sip_qt_metaobject_func sip_pyrcc_qt_metaobject;
^~~~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:141:1: error: ‘sip_qt_metacall_func’ does not name a type
sip_qt_metacall_func sip_pyrcc_qt_metacall;
^~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:142:1: error: ‘sip_qt_metacast_func’ does not name a type
sip_qt_metacast_func sip_pyrcc_qt_metacast;
^~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp: In function ‘void initpyrcc()’:
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:240:80: error: ‘sipExportModule’ was not declared in this scope
if (sipExportModule(&sipModuleAPI_pyrcc,SIP_API_MAJOR_NR,SIP_API_MINOR_NR,0) < 0)
^
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:246:5: error: ‘sip_pyrcc_qt_metaobject’ was not declared in this scope
sip_pyrcc_qt_metaobject = (sip_qt_metaobject_func)sipImportSymbol("qtcore_qt_metaobject");
^~~~~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:246:32: error: ‘sip_qt_metaobject_func’ was not declared in this scope
sip_pyrcc_qt_metaobject = (sip_qt_metaobject_func)sipImportSymbol("qtcore_qt_metaobject");
^~~~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:247:5: error: ‘sip_pyrcc_qt_metacall’ was not declared in this scope
sip_pyrcc_qt_metacall = (sip_qt_metacall_func)sipImportSymbol("qtcore_qt_metacall");
^~~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:247:30: error: ‘sip_qt_metacall_func’ was not declared in this scope
sip_pyrcc_qt_metacall = (sip_qt_metacall_func)sipImportSymbol("qtcore_qt_metacall");
^~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:248:5: error: ‘sip_pyrcc_qt_metacast’ was not declared in this scope
sip_pyrcc_qt_metacast = (sip_qt_metacast_func)sipImportSymbol("qtcore_qt_metacast");
^~~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:248:30: error: ‘sip_qt_metacast_func’ was not declared in this scope
sip_pyrcc_qt_metacast = (sip_qt_metacast_func)sipImportSymbol("qtcore_qt_metacast");
^~~~~~~~~~~~~~~~~~~~
/usr/local/src/PyQt5_gpl-5.7.1/pyrcc/sippyrcccmodule.cpp:254:56: error: ‘sipInitModule’ was not declared in this scope
if (sipInitModule(&sipModuleAPI_pyrcc,sipModuleDict) < 0)
^
Makefile:464: die Regel für Ziel „sippyrcccmodule.o“ scheiterte
make[1]: *** [sippyrcccmodule.o] Fehler 1
make[1]: Verzeichnis „/usr/local/src/PyQt5_gpl-5.7.1/pyrcc“ wird verlassen
Makefile:748: die Regel für Ziel „sub-pyrcc-make_first-ordered“ scheiterte
make: *** [sub-pyrcc-make_first-ordered] Fehler 2
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
- Posts: 7869
- Thank you received: 2125
I am sorry you are having so much trouble - I don't know why.
I have this working with debian and mint - but always RIP - I don't see why that matters

Unfortunately I am off to work for 2 weeks so can't offer much more help.
Chris M
Please Log in or Create an account to join the conversation.
- Reinhard
- Offline
- Platinum Member
-
- Posts: 508
- Thank you received: 94
Well, the python development environments (configure.py i.e.) destroys debian security.I have this working with debian and mint - but always RIP - I don't see why that matters
When you look at old stuff packages with configure shell scripts, they always use a prefix parameter, which defaults to /usr/local - that way you can compile and test a package without any harm on your productive system (paths to /usr/local have preceedance to /usr and using a separate filesystem at /usr/local allows to switch off any testing stuff with a single reboot)
Therefore I tested installation with a virtualbox, where I saved a snapshot after system installation.
I followed Quick Start Tutorial, which leaded to the already well known situation: designer without linuxcnc widgets and/or crashing designer or crashing linuxcnc
Then I tried Development Install .
I have to confess, that I don't really understand, what are sequential steps and what are alternatives ...
First I thought, that "Installing from Debian package" might be an alternative - but performing this, nothing at all works. No sip, no qtpyvcp, no widgets in designer ...
So I tried the Development Install Instructions after the package installation ...
... and got the same result as before ...
Don't know, what am I doing wrong.
Please Log in or Create an account to join the conversation.
- Reinhard
- Offline
- Platinum Member
-
- Posts: 508
- Thank you received: 94
... and stepped over to Getting Started
First steps look promising, but when I try to edit template (editvcp ...), it tells, what the designer already showed:
Traceback (most recent call last):
File "/home/cncob/.local/bin/editvcp", line 11, in <module>
load_entry_point('qtpyvcp', 'console_scripts', 'editvcp')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 561, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2631, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2291, in load
return self.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2297, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/local/src/qtpyvcp/qtpyvcp/tools/editvcp.py", line 39, in <module>
from qtpy.QtWidgets import QApplication, QFileDialog
File "/home/cncob/.local/lib/python2.7/site-packages/qtpy/__init__.py", line 208, in <module>
raise PythonQtError('No Qt bindings could be found')
qtpy.PythonQtError: No Qt bindings could be found
I checked my system: Yes, its a 64bit debian and qt-designer is of version 5.7.1
I gave up the idea to try a mint installation. Download breaks too often and after all - its no system, I want to use ...
I run out of ideas

Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
- Posts: 7869
- Thank you received: 2125
I'm sorry you are having these problems - when i get home i will do an instal version of linuxcnc and see if I can duplicate the problem.
Chris M
Please Log in or Create an account to join the conversation.
- Reinhard
- Offline
- Platinum Member
-
- Posts: 508
- Thank you received: 94
thanks a lot for your attention and support!
I very appreciate that you take the time for stil answering!
I searched a lot and I came up in reading docs for the qt-designer - but then I had to stop myself. That's nothing I wonna do. So may be qt is not the right tool for me.
I tried a few steps with glade and after building an old gui-builder I already have the linuxcnc controls in the builder. At the moment I don't understand anything, but may be, that path is more appropriate for me.
At least I don't have trouble with the tools there.
And at the moment I don't care for stylish look - just wonna get something to work with

Cheers Reinhard
Please Log in or Create an account to join the conversation.