Well now I'm back where I started. If I enable QwtDesigner in qwtconfig.pri then the make file crashes. If I don't enable it then I end up with an incompatible plugin that won't load. Is there no escape from this infinite loop of frustration?
Well now I'm back where I started. If I enable QwtDesigner in qwtconfig.pri then the make file crashes. If I don't enable it then I end up with an incompatible plugin that won't load. Is there no escape from this infinite loop of frustration?
Again, you need to have 2 different builds of Qwt: cross compiled for the Beaglebone + another build for the desktop. Those builds have to be done with different Qt versions - the first one is the one that you have cross compiled for the Beaglebone ( here the designer API was disabled as you probably never run the designer/creator on the target ) and the second one is a Qt version that has been compiled for the desktop ( where you run the creator ). The Qt version for the desktop is usually always build with support for designer plugins.
Maybe it helps to read: http://qwt.sourceforge.net/qwtinstall.html#USEPLUGIN
But in your case it should be enough to do the cross compilation with having QwtDesigner disabled. For the Qt creator simply install an official Qwt 6.1 Debiam package, without doing any compilation. This combination should usually match and if you still don't see the Qwt widgets it should be a problem of configuring the Creator ( see link above ).
Then the only problem you need to take care of is, that your build and the Debian package are installed into different directories. Check the options in qwtconfig.pri.
Uwe
Actually I am using Qt Creator on the BBB. Compile time is slow but it runs at an acceptable speed when developing. I tried to set up cross compilation but progress was slow and frustrating. Also my application takes place in the wilderness where even a laptop would be inconvenient.
Bookmarks