ModtoolArchitecture

From GNU Radio
Revision as of 11:32, 29 May 2018 by Swap-nil7 (talk | contribs) (Created page with "This article explains the current architecture of gr_modtool in the python3 branch. = What is gr_modtool? = While developing an Out Of Tree module, ther...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This article explains the current architecture of gr_modtool in the python3 branch.

What is gr_modtool?

While developing an Out Of Tree module, there's a lot of boring, monotonous work involved: boilerplate code, makefile editing, etc. gr_modtool is a script which aims to help with all these things by automatically editing makefiles, using templates, and doing as much work as possible for the developer such that you can jump straight into the DSP coding.

Note that gr_modtool makes a lot of assumptions on what the code looks like. The more your module is custom and has specific changes, the less useful gr_modtool will be, but it is probably the best place to start with any new module or block. You can go through the block coding guide for getting an insight of the tool.

gr_modtool is available in the GNU Radio source tree and is installed by default.

Plug-in Architecture

gr-modtool uses the click python library for its command line interface.