Re: [Discuss-gnuradio] Pybombs Prefix and Modtool

[Martin Braun]

Yeah I think that should be fine. You could also use PyBOMBS to build
your own OOT :)

M

On 03/08/2016 10:44 AM, Richard Bell wrote:
> The OOT is not installed by Pybombs, because its my own custom OOT that
> I made after using Pybombs. With this understanding Martin, would you
> agree I need to do what Ron said to make custom OOTs work?
> 
> Rich
> 
> On Tue, Mar 8, 2016 at 10:18 AM, Martin Braun <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     If you're using PyBOMBS to install both GNU Radio and the OOT into the
>     same prefix, this is already happening. Also, once you've sourced
>     setup_env.sh, GRC_BLOCKS_PATH is also set. Are you mixing prefixes? I'm
>     not sure I fully understand your setup.
> 
>     Cheers,
>     Martin
> 
>     On 03/07/2016 10:32 PM, Richard Bell wrote:
>     > Thanks Ron, I will test it later tomorrow.
>     >
>     > Rich
>     >
>     > On Mon, Mar 7, 2016 at 2:53 PM, Ron Economos <address@hidden 
> <mailto:address@hidden>
>     > <mailto:address@hidden <mailto:address@hidden>>> wrote:
>     >
>     >     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 ../
>     >
>     >     Ron
>     >
>     >
>     >     On 03/07/2016 02:21 PM, Richard Bell wrote:
>     >>     Hi,
>     >>
>     >>     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.
>     >>
>     >>     Thanks,
>     >>     Rich
>     >>
>     >>
>     >>     _______________________________________________
>     >>     Discuss-gnuradio mailing list
>     >>     address@hidden <mailto:address@hidden>
>     <mailto:address@hidden <mailto:address@hidden>>
>     >>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     >
>     >
>     >     _______________________________________________
>     >     Discuss-gnuradio mailing list
>     >     address@hidden <mailto:address@hidden>
>     <mailto:address@hidden <mailto:address@hidden>>
>     >     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     >
>     >
>     >
>     >
>     > _______________________________________________
>     > Discuss-gnuradio mailing list
>     > address@hidden <mailto:address@hidden>
>     > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     >
> 
> 
>     _______________________________________________
>     Discuss-gnuradio mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
>