Re: [Discuss-gnuradio] SWIG update

[Eric Blossom]

On Wed, Feb 02, 2005 at 12:40:14AM +1030, Berndt Josef Wulf wrote:
> On Monday 31 January 2005 11:00, Eric Blossom wrote:
> > I'm please to announce that CVS HEAD now builds and works great with
> > SWIG 1.3.23 and 1.3.24 (current and current-1).
> >
> > This required a change in how we build our extension modules.
> > If you're tracking CVS, you'll need to update and rebuild everything.
> >
> > In addition, dependency tracking is now working for all the .i files
> > that go into the gnuradio-core swig library.
> >
> > As a result of all of this, the lowest version of SWIG that we work
> > with is 1.3.23.  We were requiring 1.3.22.  Sorry about that, but they
> > made a non-compatible change in how they were handling dependencies.
> 
> 
> G'day,
> 
> building GnuRadio from the latest CVS sources I noticed the warning message 
> included below. These may be present in previous builds als but never caught 
> my attention then.
> 
> I also noticed that the fftsink.py doesn't execute correctly as the graph is 
> now shifted in the x/y-axis. I haven't looked any closer into this,  as I 
> only tested a few applications to confirm GnuRadio operational after the swig 
> update.

We have turned off the y-axis autoscaling until we get a better
solution.  It was driving Matt & I crazy.  It's now fixed at [-20,100]

When plotting complex data the x-axis should have moved a single bin
from it's previous location.  The DC bin was off by one.

I'll reconfirm.  Thanks the heads up.

> -------------------------------------- 8< ------------------------------------
> Searching for member function documentation...
> /usr/src/gnuradio/gr-build/gnuradio-core/src/lib/io/gr_oscope_sink_c.cc:28: 
> Warning: no matching class member found for
>   gr_oscope_sink_c::gr_oscope_sink_c(int file_descriptor)
> Possible candidates:
>   gr_oscope_sink_c::gr_oscope_sink_c(double sampling_rate, int 
> file_descriptor)
> /usr/src/gnuradio/gr-build/gnuradio-core/src/lib/io/gr_oscope_sink_c.cc:38: 

These are warnings from doxygen, the documentation extractor.
They're not critical, but should be fixed.

Eric