On Thu, Mar 03, 2005 at 10:34:15AM -0500, Charles Clancy wrote: > > >Did you follow the examples in gr-howto-write-a-block? > > http://www.gnu.org/software/gnuradio/doc/howto-write-a-block.html > > ftp://ftp.gnu.org/gnu/gnuradio/gr-howto-write-a-block-0.2.tar.gz > > The massive automake/autoconf structure made adapting the tar.gz > version very difficult to work with. I reverse engineered the > post-configured makefiles and figured out exactly what commands I > needed, and went from there. I copied the code structure from the > howto_square module, and double-checked against some of the > gnuradio-core modules.
Surrender to the autotools... Most of it is boilerplate. You can use it as is. The relevant files are configure.ac and the Makefile.am's. All the rest are generated from them. Now back to your immediate concern: Try this, only use your new block instead of howto.square_ff. How does it print? Note that this prints <gr_block square_ff (0)> Yours should print something very similar. If it doesn't, there's probably something wrong with your .i file. [EMAIL PROTECTED] gr-howto-write-a-block]$ python Python 2.3.4 (#2, Aug 19 2004, 15:49:40) [GCC 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from gnuradio import howto >>> howto.square_ff() <gr_block square_ff (0)> >>> Eric _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
