I think it may be more insidious. The ~/.gnuradio/config.conf file doesn't necessarily exist, and the default config.conf is in <install_dir>/etc/gnuradio/conf.d
But if the install prefix is /usr, then there's some trickery in the top level CMakeLists.txt file. See:
https://github.com/gnuradio/gnuradio/blob/master/CMakeLists.txt#L244
I wonder if gr_modtool works correctly when config.conf is in /etc/gnuradio/conf.d?
Ron
On 5/5/21 03:31, Josh Morman wrote:
Check your ~/.gnuradio/config.conf file. In there is a section [modtool] and a "newmod_path=..."Verify that matches the value of your installed path.On mine it says:[modtool]
newmod_path = /share/gnuradio/gr39/share/gnuradio/modtool/templates/gr-newmodFor 3.9, there was a slight change in the behavior how GR finds the newmod path:
in that it will look wherever the currently installed prefix is, which can be seen with
gnuradio-config-info --prefixMake sure your environment variables are sourced correctly - PATH, PYTHONPATH, LD_LIBRARY_PATH, and LIBRARY_PATH
On Tue, May 4, 2021 at 5:50 PM Ralf Gorholt <ralf.gorholt@gmx.de> wrote:
Dear all,
on my Linux Mint (Ubuntu) box, I have installed and compiled GNU Radio
3.9 from source (master branch) as described here:
https://wiki.gnuradio.org/index.php/UbuntuInstall#Focal_Fossa_.2820.04.29
and here:
https://wiki.gnuradio.org/index.php/InstallingGR#From_Source
CMAKE_INSTALL_PREFIX is /usr.
GNU Radio compiles (without UHD and soapy support) and the tests are ok.
gnuradio-companion starts and everything seems ok. However, when I try
to create a new module with "gr_modtool newmod dl5eu", I get the error
message: ModToolException: Could not find gr-newmod source dir.
I have also tried what was necessary for Ubuntu 18:
$ cd /usr/share/gnuradio/modtool/templates/gr-newmod
$ sudo py3clean .
but this did not solve the problem.
With version 3.8 compiled from the maint-3.8 branch I don't have this
problem. Do you have an idea what I am doing wrong here?
Thank you very much.
Kind regards,
Ralf
No comments:
Post a Comment