discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Edit GNU Radio Companion generated Python script


From: Murray Thomson
Subject: Re: [Discuss-gnuradio] Edit GNU Radio Companion generated Python script location
Date: Thu, 12 Feb 2015 08:19:54 +0000

Thanks for your answer Tom and sorry for the delay replying to you.

I tried setting the environment variable GRC_HIER_PATH but it didn't make any difference. I also tried setting
GRC_PREFS_PATH
GRC_BLOCKS_PATH
HIER_BLOCKS_LIB_DIR

But my grc companion 3.7.6.1 keeps compiling the blocks to ~/.grc_gnuradio
Can you think of anything else I could try? 
I've tried with Ubuntu 12.04 and Ubuntu 14.04.

Thanks,
Murray

On 30 December 2014 at 17:15, Tom Rondeau <address@hidden> wrote:
On Mon, Dec 29, 2014 at 8:21 AM, Murray Thomson <address@hidden> wrote:
Hi,

I have a couple of blocks and a flow graph that uses them. When I generate the flow graph of a block using GNU Radio Companion, the Python script is generated at ~/.grc_gnuradio/block1.py
The same thing happens with the flow graph but, in addition, the call to my blocks inside the generated Python script looks like this:

execfile("/home/myuser/.grc_gnuradio/block1.py")

Which means that when I copy these scripts to the target machine I need to edit that line to match the location of the block1.py in the target machine.

How can I edit the location where GNU Radio Companion puts the scripts? The Edit > Properties menu is disabled :(

Thanks,
Murray

The Properties menu item is there more for future use but doesn't yet do anything. In our current work to overhaul GRC to make it more user-friendly, I hope these are things we can more easily set and change.

In the meantime, you can control the location of the output of the hier_blocks by setting the environmental variable GRC_HIER_PATH. This will allow you to build and install the .py and .py.xml files into whatever path you want, and that execfile sring will similarly point there. One way to handle this is:

$ export GRC_HIER_PATH=/newpath
$ grcc hier_block_file.grc

Hope this helps.

Tom
 


reply via email to

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