discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] GRCC No GUI?


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] GRCC No GUI?
Date: Tue, 18 Jun 2013 12:12:39 -0400

On Fri, Jun 14, 2013 at 11:15 PM, Dan CaJacob <address@hidden> wrote:
> Is it possible to modify the GRCC tool to work on a system without a
> display, or over SSH without X-forwarding?
>
> I recently found that the GRCC tool which allows you to boil a GRC file down
> to a Python file, only works on computers with a graphical display, like a
> desktop.  On servers with no GUI or over an SSH session with X-forwarding,
> the command fails.  I think Josh commented on a thread that made mention of
> this recently, but I wanted to bring it up again.
>
> I deploy gnuradio to lots of remote machines and some of those systems
> depend on hierarchical blocks.  GRCC is awesome because it generates the
> Hier block Py file and can be commanded to put a copy of the file in the
> user's .grc_gnuradio folder, and also allows you to generate the higher
> level flow graphs that use the Hier blocks.
>
> I am actually deploying the FGs and Her blocks to a desktop machine, but
> over SSH without X-forwarding, since the configuration management tool I am
> using (ansible) doesn't support X-forwarding yet.  If you try to run GRCC
> over SSH with X-forwarding, everything is peachy.
>
> Following up on a comment Josh made in the earlier discussion about GRCC, I
> tried to pull out all of the GUI references that the GRCC tool depends on,
> but I still ended up with an enigmatic error in the end.  Unfortunately,
> this was done two weeks ago and I don't have any good info on where I left
> it.


Hi Dan,

As you said, this was discussed a bit ago, and the conclusion at that
time sounded like it wasn't going to be a straight-forward fix. Your
experience seems to confirm that. I'm not sure there's been much
activity on this, otherwise. If you manage to get it to work, I'd
really like to pull in your solution.

Tom



reply via email to

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