discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] [SOCIS '17] GRC C++ Output: Week 1


From: Martin Braun
Subject: Re: [Discuss-gnuradio] [SOCIS '17] GRC C++ Output: Week 1
Date: Fri, 4 Aug 2017 16:55:49 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

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 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 corresponding
> C++ data to the blocks. 
> 
> This way, GRC will know whether to use the Python or C++ "parts" of the
> block when generating. Hope this cleared things up! :) 
> 
> Best regards, 
> Håkon Vågsether 
> 
> 
> 31. jul. 2017 1.47 p.m. skrev "Kartik Patel" <address@hidden
> <mailto:address@hidden>>:
> 
>     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 you be looking for some
>     parameters in the blocks XML whether the block is Python? In other
>     words, how are you going to detect if it's Python block?
> 
>     Thanks!
> 
>     Regards,
>     Kartik Patel
> 
> 
>     On Mon, Jul 31, 2017 at 2:27 PM, Håkon Vågsether <address@hidden
>     <mailto:address@hidden>> wrote:
> 
>         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
>         <address@hidden <mailto:address@hidden>> 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 looking forward to the moment where we can get the
>             first compiling C++ flow graph out of GRC :)
> 
>             Best regards,
> 
>             Marcus
> 
> 
>             On 07/31/2017 12:19 AM, Håkon Vågsether wrote:
>>             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 
>>
>>
>>             _______________________________________________
>>             Discuss-gnuradio mailing list
>>             address@hidden <mailto:address@hidden>
>>             https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>             <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
> 
> 
>             _______________________________________________
>             Discuss-gnuradio mailing list
>             address@hidden <mailto:address@hidden>
>             https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>             <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
> 
> 
> 
>         _______________________________________________
>         Discuss-gnuradio mailing list
>         address@hidden <mailto:address@hidden>
>         https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>         <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
> 
> 
> 
> 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 




reply via email to

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