Hi all,
I’m working on a OOT module and created a hierarchical block in GRC. I
wonder if there is a nice way to include it in the installation process.
Currently, the user would have to open the hier block in GRC, build it,
restart GRC and open the actual flow graph that is utilizing the hier
block.
Should I somehow compile it with grcc during installation?
Best,
Bastian
–
Dipl.-Inform. Bastian B.
Institute of Computer Science
University of Innsbruck, Austria
Phone: +43 512 507-53288 / Fax: -53079
http://ccs.uibk.ac.at/~bloessl/
On Tue, Jun 4, 2013 at 1:45 AM, Bastian B.
[email protected] wrote:
Best,
Bastian
Basian,
Yes, you should be able to make a Cmake rule to run grcc on the .grc
file to build the Python file. That could be done either during cmake
time or compile time (depends on how you want to go with it; possibly
whichever you find easier to add to the cmake files). By the end of
cmake/make, you’d have a .py file. So you would also just have a rule
to install this .py file like you would any other Python file.
Tom
Hi,
On 06/11/2013 04:50 PM, Tom R. wrote:
Yes, you should be able to make a Cmake rule to run grcc on the .grc
file to build the Python file.
Building hierarchical blocks with grcc needed a small tweak, as
convert_hier.py expects the flow graph to have grc_file_path set (in
order to add a reference to the file in the doc section of the XML block
definition).
Adding the file path during initialization of grcc fixed it for me:
https://github.com/bastibl/gnuradio/commit/515e9ac51837aa8f89de0ec3c95f6f185339c48e
Best,
Bastian
On Tue, Jun 11, 2013 at 10:52 AM, Bastian B. <
[email protected]> wrote:
Adding the file path during initialization of grcc fixed it for me:
https://github.com/bastibl/gnuradio/commit/515e9ac51837aa8f89de0ec3c95f6f185339c48e
This was recently merged for the pending 3.6.5.1 and 3.7.0 releases.