On Thu, Apr 26, 2012 at 11:31:40AM -0400, Getz, Robin wrote: > On Thu 26 Apr 2012 10:58, Johnathan Corgan pondered: > > On Thu, Apr 26, 2012 at 07:38, Getz, Robin <robin.g...@analog.com> wrote: > > > Is there a "golden" reference to look at? (I assume > > > gr-howto-write-a-block-3.6.0.tar.gz > > > should have everything we need?) > > > > This will give you the "canonical" format for writing your own > > out-of-tree installable GNU Radio blocks. > > And what is preferred? I always think in-tree is better - but that's just me.
Just adding to what Johnathan said: out-of-tree is easier to start with. You can use gr_modtool[1] to create all the skeleton code, chuck in your driver hooks and be running within the hour. Just do something like (change this to whatever you need) $ gr_modtool.py create fmccomms $ cd gr-fmccomms/ $ gr_modtool.py add -t sink sink_c $ gr_modtool.py add -t source source_c Then, fill in the blanks (i.e. edit lib/fmccomms_sink_c.cc and so on). MB [1] https://cgran.org/wiki/devtools -- Karlsruhe Institute of Technology (KIT) Communications Engineering Lab (CEL) Dipl.-Ing. Martin Braun Research Associate Kaiserstraße 12 Building 05.01 76131 Karlsruhe Phone: +49 721 608-43790 Fax: +49 721 608-46071 www.cel.kit.edu KIT -- University of the State of Baden-Württemberg and National Laboratory of the Helmholtz Association
pgpYaLpZkNQ3i.pgp
Description: PGP signature
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio