Hi,

I have been developing a number of direct spread spectrum OOT blocks as part of 
a research project.

Working blocks were originally developed using GRC 3.7.11, however I wish to 
move forward and have installed and persevered so far with GRC 3.9 from the 
master branch.

The GRC, UHD, CMAKE (3.16) pybind11 (2.4.3) and other dependencies have been 
installed and build correctly.  

I have chosen to migrate the (3.7.11) C++ blocks and for completeness of the 
build process checking, have included a simple python OOT.
The C++ to python code binding, make and install under Ubuntu 20.04 all work 
and the new blocks import correctly to flow-graph using modified .yml 
descriptors.

1). GRC 9.0 works standalone from git-master install and with the UHD, in my 
case a B210.
2). OOT blocks including the aforementioned python OOT block all fail at 
import. In my case ModuleNotFoundError: No module named ‘development’
i.e. failure of ‘import development’ in the flow-graph python script

3). I have tried and retained the library workarounds with PYTHONPATH and 
LD_LIBRARY_PATH, but these now seem irrelevant as the GRC basically loads and 
runs.

4). I have looked at the gr_modtool  __init_.py file for indicators as to why 
both python and C++ blocks (using python bindings) both fail.
The inability of python 3.8.2 in my case to resolve the import is clearly at 
its core.

5). The OOT GRC blocks themselves import correctly into the flow-graph produce 
error free python script and all have relatively primitive interfaces.

Many thanks,

David Taylor

Reply via email to