Sylvain solved it in a sec ;) There is no need to get the classes with
the qt stuff through swig. Solution is including the additional qt
classes only in cmake and wrap them with QT4_WRAP_CPP cause of the
Q_OBJECT macro but dont care about them in the *_swig.i file.
Am 19.06.2014 23:31, schrieb St
Hi,
> Do I need to add more to get swig running with the QT slots and signals?
> I am correct with the assumption that cmake and swig accepts the
> Q_OBJECT macro?
Why do you even need to get those through swig ?
Last time I did a Qt block, all the Qt stuff was hidden from swig,
there was only
Hi!
I try to add a QT GUI to my OOT module (gr-radar). I have some issues
with including the QT stuff in cmake and swig.
The problem is this error:
## /gr-radar/swig/../lib/range_velocity_diagram.h:45: Error: Syntax
error in input(3).
## make[2]: *** [swig/radar_swigPYTHON_wrap.cxx] Error 1
## m
