Are you sure GRC is looking for the files in /usr/local/share/gnurado/grc/blocks, and not elsewhere (e.g. /usr/share/gnurado/grc/blocks) ?
M On 02/25/2016 01:03 PM, Richard Bell wrote: > Oh yes that's what I was trying to explain. This is an OOT module, with > a properly configured .xml file that I gave a category. This xml file > was installed to the gnuradio blocks tree directory as described in my > first email. I checked and it is there > (/usr/local/share/gnurado/grc/blocks). However, I do not see the > category or the block in the grc library list. The OOT is only > recognized when I use the export GRC_BLOCKS_PATH variable to point to my > OOT folder. This causes other xml related errors to occur everytime I > start grc, but I ignore them becaues it's the only way I can use the OOT > blocks at the moment. > > Rich > > On Thu, Feb 25, 2016 at 12:41 PM, Martin Braun <martin.br...@ettus.com > <mailto:martin.br...@ettus.com>> wrote: > > The block tree is the data structure that holds the blocks and what GRC > uses to sort them on the right-hand panel. Is this an OOT? Then you > typically put them into the block tree by having a <category> tag in > your XML. > The other option is a block tree file, which is what the in-tree > components use. You can use the block tree files in OOTs, too. > > Then make sure you run gnuradio-companion in a terminal. It'll print out > warning if it can't find stuff. > > M > > > > On 02/25/2016 12:37 PM, Richard Bell wrote: > > I think I'm misunderstanding you. I thought you were just asking me if I > > could find the blocks in the grc library, either manually or using > > Ctrl-F. That I cannot do. > > > > If they are not there, I don't know how to manually place them in the > > block tree, as it seems your saying I should do. How do I add them to > > the block tree as you say? > > > > Thanks, > > Rich > > > > On Thu, Feb 25, 2016 at 12:31 PM, Martin Braun <martin.br...@ettus.com > <mailto:martin.br...@ettus.com> > > <mailto:martin.br...@ettus.com <mailto:martin.br...@ettus.com>>> wrote: > > > > So if you put them in the block tree, do they show up? > > > > M > > > > On 02/25/2016 12:19 PM, Richard Bell wrote: > > > No they are not in the block tree. > > > > > > Rich > > > > > > On Thu, Feb 25, 2016 at 11:44 AM, Martin Braun > <martin.br...@ettus.com <mailto:martin.br...@ettus.com> > <mailto:martin.br...@ettus.com <mailto:martin.br...@ettus.com>> > > > <mailto:martin.br...@ettus.com > <mailto:martin.br...@ettus.com> <mailto:martin.br...@ettus.com > <mailto:martin.br...@ettus.com>>>> > > wrote: > > > > > > Are the blocks in the block tree? Can you see them by doing > > Ctrl-F + > > > search? > > > > > > M > > > > > > On 02/25/2016 11:40 AM, Richard Bell wrote: > > > > I've noticed lately that I can't just compile and > install custom > > > blocks > > > > and have them show up in grc. I've had to add a > GRC_BLOCKS_PATH > > > > environment variable that points to the location of my > > custom blocks > > > > folder to make them discoverable. > > > > > > > > Isn't the sudo make install process supposed to copy the > > required > > > files > > > > to known places that gnuradio can find them so I don't > have > > to worry > > > > about this? For example, I do see the custom blocks > .xmls in the > > > > /usr/local/share/gnurado/grc/blocks directory after > installing. > > > > > > > > To make sure I'm not being silly and forgetting something, > > here is my > > > > process: > > > > > > > > 1) Create a new block in a random directory with > gr_modtool > > and get > > > > ready to compile and install > > > > > > > > 2) Create a build directory and do the following from > within > > build: > > > > > > > > cmake .. > > > > sudo make install > > > > sudo ldconfig > > > > > > > > 3) Re-open grc and see your new blocks in the library > > > > > > > > Is this a bug or am I overlooking something? Could it be > > related to > > > > using the new pybombs? > > > > > > > > Rich > > > > > > > > > > > > _______________________________________________ > > > > Discuss-gnuradio mailing list > > > > Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>>> > > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > > > > > > > > _______________________________________________ > > > Discuss-gnuradio mailing list > > > Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> > <mailto:Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>>> > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> > <mailto:Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
