Python-only blocks aren't available in C++ anyway, so GRC can't generate
code to include them. Most of our blocks are swigged though, so it's not
really a problem.
-- M
On 08/01/2017 04:11 AM, Håkon Vågsether wrote:
> Hi Kartik,
>
> Thanks for asking!
>
> What I've envisioned is that the user
Hi Kartik,
Thanks for asking!
What I've envisioned is that the user chooses whether he/she wants GRC to
generate C++ or Python code. Currently the blocks' YAML files only contain
data and snippets that work in Python, ("from x import y" doesn't work in
C++, of course :)) so I'll have to add the c
Hello Håkon,
Your project is pretty interesting. Finally, we are trying to give a
platform to "C++ only" programmers, too. :P
I have one query. Are you going to connect the Python blocks in the
generated C++ script? I am not sure if it is even possible, but may be SWIG
can help. If not, then will
Not yet, I'll do it today :)
Best regards,
Håkon Vågsether
On Mon, Jul 31, 2017 at 9:32 AM, Marcus Müller
wrote:
> Hi Håkon,
>
> thanks for the update :) And of course, thank for the python3 bugfix! Did
> you do a pull-request against the "mainline" gnuradio/python3 branch yet?
>
> Very much lo
Hi Håkon,
thanks for the update :) And of course, thank for the python3 bugfix!
Did you do a pull-request against the "mainline" gnuradio/python3 branch
yet?
Very much looking forward to the moment where we can get the first
compiling C++ flow graph out of GRC :)
Best regards,
Marcus
On 07/31
Hi all,
The focus for this week has been the header file template. I've just
updated my blog with some more details, you can check it out at:
http://grccpp.wordpress.com
If you have any questions or suggestions, please don't hesitate to ask :)
Best regards,
Håkon Vågsether
_
