From: Guillaume Le Vaillant <glv@posteo.net>
To: christopher@librehacker.com
Cc: 40952@debbugs.gnu.org
Subject: bug#40952: gnuradio-osmosdr: no hook into gnuradio block directory?
Date: Wed, 29 Apr 2020 10:38:45 +0200 [thread overview]
Message-ID: <874kt2heju.fsf@yamatai> (raw)
In-Reply-To: <2daa37de70a83d3ffad747710e95e429eeeea6aa.camel@qlfiles.net>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
Christopher Howard <christopher.howard@qlfiles.net> skribis:
> Hi, I installed gnuradio and gnuradio-osmosdr, but when I open
> gnuradio, none of the osmosdr blocks are available from gnuradio blocks
> list. Specifically, I was looking for osmosdr source block, which I am
> familiar with from using gnuradio under Debian. I believe the problem
> is that the osmosdr blocks are not in the directory where gnuradio-
> companion is looking for blocks.
>
> When starting up gnuradio-companion, stdout indicates grc is looking for blocks here:
>
> /gnu/store/h2igg2gcbx6ds8wbvlkqz0dkplvwjxbd-gnuradio-3.8.0.0/share/gnuradio/grc/blocks
>
> But osmosdr blocks are in
>
> /gnu/store/ppb504vizb32f4w2s5f0yd6i4xpy41nz-gnuradio-osmosdr-0.2.0/share/gnuradio/grc/blocks/
>
> Evidentally gnuradio package needs to be enhanced to create a per-
> profile merged directory from all gnuradio- block packages that are
> installed. Unless there is some way to extend the gnuradio search path
> through environment variables.
Hi Christopher,
I pushed a fix (commit cf480830e22e7725b8607b5b895e49f74d4e1525) that
should put the paths to installed third-party blocks in GRC_BLOCKS_PATH,
and allow gnuradio-companion to see them. Could you check if it works
for you?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-04-29 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 4:20 bug#40952: gnuradio-osmosdr: no hook into gnuradio block directory? Christopher Howard
2020-04-29 8:38 ` Guillaume Le Vaillant [this message]
2020-04-29 14:56 ` Christopher Howard
2020-04-30 1:11 ` Christopher Howard
2020-04-30 9:03 ` Guillaume Le Vaillant
2020-04-30 14:07 ` Christopher Howard
2020-04-30 14:16 ` Guillaume Le Vaillant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kt2heju.fsf@yamatai \
--to=glv@posteo.net \
--cc=40952@debbugs.gnu.org \
--cc=christopher@librehacker.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.