[Top][All Lists]

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

Re: [Discuss-gnuradio] huge SWIG generated <module>.cc and <module>.py f

From: Joshua Lackey
Subject: Re: [Discuss-gnuradio] huge SWIG generated <module>.cc and <module>.py files?
Date: Thu, 5 Jan 2006 23:33:48 -0800
User-agent: Mutt/

Haha.  Nevermind.

I had: '%include "gnuradio.i"' rather than '%import "gnuradio.i"' in my
<module>.i file...

Makes a big difference.  :)

Quoting Joshua Lackey (address@hidden):
> I'm not sure if this is common but I'm trying to track this down so I
> thought I would ask to see if anyone else has seen this.
> I'm constructing my own module and I patterned it after the howto.  When
> my SWIG <module>.cc file is created it is about 3.5MB and the <module>.py
> file is 600KB.  The howto module, on the other hand, has howto.cc about
> 210KB and the howto.py file under 8KB.
> Also, when you look in my <module>.py file you find things like:
> class gr_oscope_sink_f_sptr(object):
>     """Proxy of C++ gr_oscope_sink_f_sptr class"""
> I find it rather strange to have oscope things in my module.  (Moreover
> these things do not appear in howto.py.)
> It won't be much work for me to re-construct my project to (try and) fix
> this, but I'm hoping that it is just some obvious argument somewhere
> that I'm missing.
> Thanks!
> -- 
> Joshua Lackey, PhD. -- address@hidden
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Joshua Lackey, PhD. -- address@hidden

reply via email to

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