On Wed, Apr 20, 2011 at 07:13:15PM +0200, Josh Blum wrote: > I think I see why: > > > //! Complex floating point (64-bit floats) range [-1.0, +1.0] > > COMPLEX_FLOAT64 = 'd', > > //! Complex floating point (32-bit floats) range [-1.0, +1.0] > > COMPLEX_FLOAT32 = 'f', > > //! Complex signed integer (16-bit integers) range [-32768, +32767] > > COMPLEX_INT16 = 's', > > //! Complex signed integer (8-bit integers) range [-128, 127] > > COMPLEX_INT8 = 'b' > > Swig 2 is interpreting that as a string. Which in kind of nice, except > that things that use those enums in python expect type int. Swig seems to me like black magic ... on the other hand ... the whole gnuradio build process sometimes does ...
> I dont know the magical swig switch to turn that off. Does this diff > make it work for you? If you didn't know it, you pushed it by accident or good guess ;-) It's working just fine now :-) Thanks again for your quick fix! All the best, Moritz
pgpAFB9PgBL7g.pgp
Description: PGP signature
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
