I’m making much more progress on my embedded x86_64 gnuradio project.
I am now able to build and run my grc-created python app, but I get
this error. I’m using some counter/sliders from Qwt (Qt GUI Range
block) to be able to change some values interactively. However, I
don’t seem to have PyQt4.Qwt5, and furthermore, I can’t seem to figure
out how to build/install it. I have found the source, of course,
(sourceforge) but not any openembedded recipes for it. Furthermore,
it seems to be part of the PyQt4 package, and I don’t see any
reference to a Qwt module within the python-pyqt package.
./my_gui.py
Traceback (most recent call last):
File “./my_gui.py”, line 30, in
import PyQt4.Qwt5 as Qwt
Traceback (most recent call last):
File “./my_gui.py”, line 30, in
import PyQt4.Qwt5 as Qwt
ImportError: No module named Qwt5
Thanks in advance for any advice.
Make a recipe for PyQwt. Sadly this isn’t easy.
The PyQt4 recipe in dizzy isn’t 100%, but the one in master should be.
There is also a long term support issue with PyQwt and qt5, so it sounds
like we need to figure out how to replace Qwt eventually. Tom R. knows
the details.
The PyQt4 recipe in dizzy isn’t 100%, but the one in master should be.
There is also a long term support issue with PyQwt and qt5, so it sounds
like we need to figure out how to replace Qwt eventually. Tom R. knows
the details.
Philip
PyQWT has refused to move to QWT6, so it’s still stuck on QWT5’s API.
The
good thing is that this actually interacts fine with QWT6 for what
little
we use PyQWT for, but the installation process for PyQWT is awkward (at
best, most would say awful). We have this issue in OE and OS X macports
right now.
We’re talking about how to remove the dependency and replace it with
something more usable and less likely to fall apart.
For that, just look into gr-qtgui/grc/qtgui_range.xml and see about
converting that (maybe making a secondary block for it) that calls just
the
QT slider stuff directly.
it seems to be part of the PyQt4 package, and I don’t see any
Thanks in advance for any advice.
PyQWT has refused to move to QWT6, so it’s still stuck on QWT5’s API. The
good thing is that this actually interacts fine with QWT6 for what little we
use PyQWT for, but the installation process for PyQWT is awkward (at best,
most would say awful). We have this issue in OE and OS X macports right now.
We’re talking about how to remove the dependency and replace it with
something more usable and less likely to fall apart.
Then I think my best option is to find a way to not use it.
I did start hacking on a PyQwt recipe in the early morning hours, and
realized I was in over my head!
Thanks,
Chris
–
Life is like Linux - it never stands still.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.