Re: [Discuss-gnuradio] passing USRP source block shared pointer through SWIG

2015-03-24 Thread Martin Braun
...@ettus.com] Sent: Monday, March 23, 2015 12:58 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] passing USRP source block shared pointer through SWIG You should easily be able to pass a basic_block sptr and then dynamic-cast it in your block. What you're trying to do

Re: [Discuss-gnuradio] passing USRP source block shared pointer through SWIG

2015-03-24 Thread Anderson, Douglas J.
[discuss-gnuradio-bounces+danderson=its.bldrdoc@gnu.org] on behalf of Martin Braun [martin.br...@ettus.com] Sent: Monday, March 23, 2015 12:58 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] passing USRP source block shared pointer through SWIG You should easily be able

Re: [Discuss-gnuradio] passing USRP source block shared pointer through SWIG

2015-03-24 Thread Anderson, Douglas J.
-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] passing USRP source block shared pointer through SWIG On 24.03.2015 12:10, Anderson, Douglas J. wrote: [...] I actually considered implementing the lo_offset message code myself and then doing a pull request, but I just couldn't think of a good way

[Discuss-gnuradio] passing USRP source block shared pointer through SWIG

2015-03-23 Thread Anderson, Douglas J.
Hi all, I'm looking into the possibility of passing the gr_block gr uhd usrp source (0) object from Python into a C++ out of tree module. In my module, I have: controller_cc_impl::controller_cc_impl(gr::uhd::usrp_source::sptr usrp, [...]) I get a TypeError when I instantiate the block. It

Re: [Discuss-gnuradio] passing USRP source block shared pointer through SWIG

2015-03-23 Thread Martin Braun
You should easily be able to pass a basic_block sptr and then dynamic-cast it in your block. What you're trying to do is not recommended procedure, although I can see how it's necessary at times. Can you tell us what you're trying to do? We've been working on making the message ports more