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

Hi Håkon, Thanks for the info. I will try your code under that distro. Regarding what I've shown - I compiled everything according to your description and gnuradio-companion failed on my machine (Ubuntu 16.04) to load because it couldn't import gr from gnuradio. This is why I've shown what happen

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

Hello Piotr, hmm, that certainly doesn't look like code I have touched, and I can't say I have seen that error before either. I'm running Arch Linux (Python 3.6.2), hope that helps! :) Best regards, Håkon Vågsether On Sun, Sep 24, 2017 at 4:27 PM, Piotr Krysik wrote: > W dniu 18.09.2017 o 11:1

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

W dniu 18.09.2017 o 11:10, Håkon Vågsether pisze: > Hi all, > > The focus for this week has been the QT blocks. You can read more at: > > https://grccpp.wordpress.com > > Best regards, > Håkon Vågsether Hi Håkon, I'm trying to compile and run according to the description but I got an error when tr

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

Hey, thanks for the extensive answer! So, yeah, I think finding a way to come up with a graphical way to program C++ is a bigger problem than fixing the GNU Radio scheduler :) you're certainly invited to help on enabling loopbacks; there's no "real" reason it's forbidden by the scheduler. Essentia

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

Hi, so your idea is to use GNU Radio Companion to design blocks that internally > has a loopback? > Actually, my idea was to use the companion to design blocks in c++. They may have loops or not. > That would kind of break the semantics of GRC being a tool for designing > GNU Raio flow graphs > Y

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

Hi Federico, so your idea is to use GNU Radio Companion to design blocks that internally has a loopback? That would kind of break the semantics of GRC being a tool for designing GNU Raio flow graphs, but I'd still be open to that idea, if you could explain in which way that would differ from it s

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

Hi Marcus, Me and my team would be glad to help. I am aware that block interconnection depends on the scheduler, which forbids loops. However, my idea was not as ambitious as modifying the whole scheduler, but customizing the companion to generate the c++ code of a block, and thus my question (a so

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

Hi Federico, Loops in the Flowgraph are currently forbidden by GNU Radio itself, not by the GRC designer. So, no, this is not scope of Hakon's project. If you want to contribute to having that feature in a generally useful manner, we can certainly chat about how you can improve the scheduler to m

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

Hi, Outputting c++ from the companion would be a great addition to GNU Radio. A small question: the possibility of having loops on the flowgraph is contemplated on this project? We've been using GNU Radio for teaching for some years now (highschool, undergraduate and graduate students), and such fe

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

Hi all, The focus for this week has been the QT blocks. You can read more at: https://grccpp.wordpress.com Best regards, Håkon Vågsether ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio