After finding out I'm not the only one who stumbles over things when using gr-howto as a module template, I added some lines to the README file. I guess this could be useful.
MB -- Dipl.-Ing. Martin Braun Phone: +49-(0)721-608 3790 Institut fuer Nachrichtentechnik Fax: +49-(0)721-608 6071 Universitaet Karlsruhe (TH) http://www.int.uni-karlsruhe.de/
Index: gr-howto-write-a-block/README =================================================================== --- gr-howto-write-a-block/README (revision 10991) +++ gr-howto-write-a-block/README (working copy) @@ -48,3 +48,20 @@ build problems on systems that don't have xmlto installed. If you have xmlto and its dependencies installed, you can build the html version of the howto article by cd'ing to doc and invoking make. + + +If you want to create a new Python/C++ library using this as a template, +you must do the following: + +1) Change configure.ac to suit your needs. This will involve changing the + project name from 'gr-howto-write-a-block' to whatever it is you want + in AC_INIT, calling the autoconf macros to check for any library you + need (e.g. by uncommenting the AX_BOOST_* lines) and removing/adding + any files from AC_CONFIG_FILES (at first, you'll probably not need doc). +2) In src/lib, modify Makefile.swig.gen and Makefile.am by searching/replacing + all ocurrences of 'howto' with your new module name. +3) Makefile.am needs some adapting of its own, of course. Most likely, you will + want to adapt grinclude_HEADERS, yourmodulename_la_swig_sources and + TOP_SWIG_IFILES. + +
pgpalfElQ3EVa.pgp
Description: PGP signature
_______________________________________________ Patch-gnuradio mailing list Patch-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/patch-gnuradio
