|
From: | David Taylor (manx.net) |
Subject: | Re: GRC version 3.9.0.0 git master (python 3.8.2) + OOT blocks |
Date: | Fri, 21 Aug 2020 17:23:15 +0100 |
Josh,
Sorry to go over old ground yet again.
In order to remove any additional problems caused by the use of external
libraries, I have created a separate OOT branch that is void of external
libraries.
Stripped to the bone python and C++ blocks have been created using
gr_modtool. Test codes validate the blocks code content as functional and they
import correctly into the GRC with simple .yml.
The top level CMakeLists.txt and others are unmodified from a clean new
module.
The current issue has been traced so far to the __init__.py file and its
inability to resolve ‘__path__’
Consequently the pybind11 link fails to find my ‘test’ directory and the
subsequent imported python block fails with no known parent package.
I am unclear how and where this is initialised under python3? I have
attended to the usual library and path ~./bashrc changes to no avail.
The GRC outputs the AttributeError: message for the python and C++ OOT
block.
Once resolved, I can move forward again with the external library
inclusion.
Many thanks,
David GD4FMB
From: Josh
Sent: Monday, August 17, 2020 11:45 AM
Subject: Re: GRC version 3.9.0.0 git master (python 3.8.2) + OOT
blocks David,
I've found most of the time I get the "No module named ..." error it is due
to C++ linkage issues in setting up the CMake. There was a big jump in
CMake modernization from GR 3.7 to 3.8, so be sure to use gr_modtool (from 3.9)
to create a new module and copy your blocks in from there is usually the easiest
way. Porting guide is here: https://wiki.gnuradio.org/index.php/GNU_Radio_3.8_OOT_Module_Porting_Guide
and here: https://wiki.gnuradio.org/index.php/GNU_Radio_3.9_OOT_Module_Porting_Guide
the one that usually gets me and causes the ModuleNotFoundError is
this
Does your library reference any GR modules, or any other external
libraries?
Josh
|
[Prev in Thread] | Current Thread | [Next in Thread] |