From: Christopher Howard <christopher@librehacker.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 40952@debbugs.gnu.org
Subject: bug#40952: gnuradio-osmosdr: no hook into gnuradio block directory?
Date: Wed, 29 Apr 2020 06:56:53 -0800 [thread overview]
Message-ID: <f9c92e216f9fa9d4516da32041e5e9482571ca4f.camel@librehacker.com> (raw)
In-Reply-To: <874kt2heju.fsf@yamatai>
The osmosdr sink and source blocks are showing up now after updating to
the specified commit. I have to leave for work now, but was planning to
try using the source block this evening with my HackRF SDR.
--
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)
On Wed, 2020-04-29 at 10:38 +0200, Guillaume Le Vaillant wrote:
> 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?
next prev parent reply other threads:[~2020-04-29 14:58 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
2020-04-29 14:56 ` Christopher Howard [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9c92e216f9fa9d4516da32041e5e9482571ca4f.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=40952@debbugs.gnu.org \
--cc=glv@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).