discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Ubuntu 11.10


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Ubuntu 11.10
Date: Mon, 17 Oct 2011 22:55:52 -0700

On Mon, Oct 17, 2011 at 10:03 PM, Josh Blum <address@hidden> wrote:


On 10/16/2011 07:17 PM, Tom Rondeau wrote:
> The maint, master, and next branches in git have all been fixed to work
> under Ubuntu 11.10 (new autotools and Qwt 6 were the main culprits). A bit
> more information can be found here:
> http://gnuradio.squarespace.com/home/2011/10/16/ubuntu-1110-troubles.html
>

I tried to switch to qwt6. So, I cant find python-qwt6 in the repos
(this is for some of the grc qt widgets). So I guess that is a minor
disappointment.

And I got this compilation error. Any idea?

> /home/jblum/src/gnuradio/gr-qtgui/lib/WaterfallDisplayPlot.cc: In constructor ‘WaterfallDisplayPlot::WaterfallDisplayPlot(QWidget*)’:
> /home/jblum/src/gnuradio/gr-qtgui/lib/WaterfallDisplayPlot.cc:321:33: error: no matching function for call to ‘QwtPlotSpectrogram::setData(WaterfallData&)’
> /home/jblum/src/gnuradio/gr-qtgui/lib/WaterfallDisplayPlot.cc:321:33: note: candidate is:
> /usr/include/qwt/qwt_plot_spectrogram.h:63:10: note: void QwtPlotSpectrogram::setData(QwtRasterData*)
> /usr/include/qwt/qwt_plot_spectrogram.h:63:10: note:   no known conversion for argument 1 from ‘WaterfallData’ to ‘QwtRasterData*’

-Josh

Yeah, I know exactly what the problem is. I just found it myself. It arose after I fixed some edits to be compatible with 5.2, but didn't do it right to keep it working with qwt 6. I must not have properly updated my 11.10 box afterwards to check it.

I just pushed what I believe are fixes to maint/master/next. Let me know if anyone has problems with either Qwt versions 5.2 or 6.0. 

The push to next also includes a bunch of updates to gr-digital where I've moved all of the OFDM work into gr-digital and reworked all of the examples to use UHD. Again, let me know if people experience more than the usual issues :)

Tom


reply via email to

[Prev in Thread] Current Thread [Next in Thread]