|
From: | Patrick Sathyanathan |
Subject: | Re: [Discuss-gnuradio] OOT Module Attribute Error module object has no attribute 'blockname' |
Date: | Wed, 19 Aug 2015 15:06:04 -0700 |
Hi Logan, I have faced the same error twice recently in my OOT module and finally tracked it down to two causes. The basic reason for the 'object has no attribute' error is that Python's import of your module failed. In the two cases that I saw it was due to undefined symbols in the shared library for my module. My module was called 'tutorial' so the corresponding library is libgnuradio-tutorial.so and you can find it in the .../build/lib directory. To find out the undefined symbols do the following: nm -C -u libgnuradio-<modulename>.so and search for method names in your class. So if your class is 'MyClass' you could do: nm -C -u libgnuradio-<modulename>.so | grep MyClass The two cases that I ran into were: 1. A non-virtual method in my implementation class was undefined because I had forgotten to prefix the method definition with the class name. So the .cc file had "void foo(...)" instead of "void MyClass_impl::foo(...)" and foo was compiled as a ordinary function. Then the command above will report "MyClass_impl::foo" as undefined. 2. The second case I ran into was with defining callbacks in the XML file. If you do then you will need to add matching virtual function declarations in the header file. This is needed for SWIG to work correctly. For my case the callback "foo" needed a virtual function declaration "virtual <sometype> foo(...) = 0;" in the actual class declaration (not the ..._impl version) in the header file. Do you have callbacks ? If this is the issue then you should do a "make clean" before running make again to force SWIG to run. Hope this helps. --Patrick Date: Wed, 19 Aug 2015 14:51:27 -0400 From: address@hidden To: address@hidden CC: address@hidden Subject: Re: [Discuss-gnuradio] OOT Module Attribute Error module object has no attribute 'blockname' My gut is telling me this is a swig problem. I don't know that it's frowned upon, but it's not easy to read without some kind of highlighting that we'd get from github or a gist with files. If I'm correct we'd also need to see swig/ACK.i (probably missing an include and/or gr swig block magic. compare to tutorial swig for sanity check) On Wed, Aug 19, 2015 at 10:38 AM, Washbourne, Logan <address@hidden> wrote:
_______________________________________________ Discuss-gnuradio mailing list address@hidden https://lists.gnu.org/mailman/listinfo/discuss-gnuradio |
[Prev in Thread] | Current Thread | [Next in Thread] |