# Fwd: modtool noblock and xml files and grc

**URL:** <https://www.ruby-forum.com/t/fwd-modtool-noblock-and-xml-files-and-grc/242116>\
**Category:** GNU Radio\
**Created:** [May 28, 2015, 5:47pm UTC](https://www.ruby-forum.com/t/fwd-modtool-noblock-and-xml-files-and-grc/242116 "2015-05-28T17:47:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [May 28, 2015, 5:47pm UTC](https://www.ruby-forum.com/t/fwd-modtool-noblock-and-xml-files-and-grc/242116/1 "2015-05-28T17:47:02Z")

</div>

On Thu, May 28, 2015 at 8:26 AM, John M. \<  
removed\_email\_address@domain.invalid\> wrote:

> Anyhow, it unexpectedly generated an xml file to import the non-block into  
> GRC.  
> Is there a best way to just remove that xml file without causing other  
> issues?

First, do a ‘make uninstall’ from your build directory, to remove the  
file  
from where GRC finds it.

Then, edit grc/CMakeLists.txt and remove the line that has the XML  
filename  
in it.

Finally, rerun the build (cmake, make, sudo make install, etc.).

Also when I tried to drag and drop the non-block into GRC, presumably  
from

> the default created xml file with no edits (curiosity always gets one in  
> trouble?) GRC went to a blank screen. Of course I was able to close and  
> restart and pick up at the last save which was fine. Okay none of that is  
> really unexpected.

In general, gr\_modtool creates XML files that need further editing  
before  
being usable in GRC; in this case, GRC didn’t handle the mis-parse very  
well.

> I guess there must be a reason you would have a noblock that can be added  
> to a flowgraph?

You can create generic functions with parameters that you can set up as  
variables in GRC. They aren’t blocks added to the flowgraph but are  
still  
“GRC blocks”.