Re: [Discuss-gnuradio] modtool noblock and xml files and grc

[John Murphy]

Nevermind, figured out (by looking at another module, fortunately had one handy although one could probably find such on git somewhere now that I think about it instead of hitting the panic button)

for posterity, you just have to add the following to the end of the line listing the last xml file
 DESTINATION share/gnuradio/grc/blocks

Thanks,

all that worked great now.

On Thu, May 28, 2015 at 12:17 PM, John Murphy <address@hidden> wrote:
>
> Okay.
> Tried this, then deleted the xml file before attempting to make again without it.
> Got the following error when re-making (the line with the xml file had a destination which I had thought was just for that file)
> What do I need to do to fix this?
> Thanks,
> - John
>
>
> CMake Error at grc/CMakeLists.txt:19 (install):
>   install FILES given no DESTINATION!
>
>
> -- Configuring incomplete, errors occurred!
> See also "/usr/local/share/gnuradio-OutOfTree-modules/gr-comso/build/CMakeFiles/CMakeOutput.log".
> See also "/usr/local/share/gnuradio-OutOfTree-modules/gr-comso/build/CMakeFiles/CMakeError.log".
> make: *** [cmake_check_build_system] Error 1
>
>
> From: Johnathan Corgan <address@hidden>
> >
> >
> > On Thu, May 28, 2015 at 8:26 AM, John Murphy <
> > address@hidden> 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".