[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Pybombs Prefix and Modtool

From: Ron Economos
Subject: Re: [Discuss-gnuradio] Pybombs Prefix and Modtool
Date: Mon, 07 Mar 2016 14:53:11 -0800
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

When you build your OOT module, you have to use the same prefix as your GNU Radio install. This is done in the cmake stage with -DCMAKE_INSTALL_PREFIX. For example.

cmake -DCMAKE_INSTALL_PREFIX=/opt/gnuradio-3.7.10git ../


On 03/07/2016 02:21 PM, Richard Bell wrote:

I think I've narrowed down what I and some colleagues of mine have been experiencing enough to explain it and hopefully get a solution.

When I installed gr using the new pybombs, I specified a custom prefix location (on several computers). It seems that later on, when I create an OOT module using modtool, GRC does not interact properly with these OOT modules, for some reason unknown to me that I'm assuming is related to this prefix. The only workaround I know to get OOT modules to show up in GRC now is to add each OOT module directory path to the GRC_BLOCKS_PATH env variable. This causes XML parser errors to be reported everytime I open GRC, and slows it down.

So my question is this:

With the old pybombs, I always used the default prefix and thereafter modtool always worked. After sudo make install and sudo ldconfig, my OOT blocks showed up in GRC. Since now I chose a custom prefix, is there an additional step I am supposed to take when making OOT blocks?

Summary: Installed GR using new Pybombs in custom prefix. Installing OOT module custom blocks does not work without editing GRC_BLOCKS_PATH variable for each OOT path.


Discuss-gnuradio mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]