Hi Ron, Hi Rick,
agreed, you probably need that development package. Problem: Without it, the GNU Radio
build infrastructure shouldn't even allow for enabling of the SoapySDR components.
So, Rick, could you tell us which operating system/distro this is on, and how you did that
local installat
Hi all,
GNU Radio's cmake scripts do check for this situation (SoapySDR not
found, GR_ENABLE_SOAPY force-enabled) and it should error out when
`cmake` is run:
https://github.com/gnuradio/gnuradio/blob/main/cmake/Modules/GrComponent.cmake#L71
The full CMake output would be useful to figuring
Hail,
Your feedback goes beyond my expectations. Before I follow this
further, here is a summary of my installation attempt as Marcus
requested. I hope that it is a good balance between detail and clutter.
First to clarify, by 'local' I mean under my home directory (no
superuser install). The O
Ryan,
Here is an excerpt of the CMake output:
--
-- Configuring gr-soapy support...
-- Dependency SoapySDR_FOUND = 1
-- Dependency ENABLE_GNURADIO_RUNTIME = ON
-- Enabling gr-soapy support.
-- Override with -DENABLE_GR_SOAPY=ON/OFF
-- SOAPY Version: 0.7.2-unknown
-- No C++ unit tests..
This is just a guess, but you could try adding:
-DCMAKE_PREFIX_PATH=~/.local
to your cmake invocation.
Ron
On 2/7/23 11:56, aardric wrote:
Ryan,
Here is an excerpt of the CMake output:
--
-- Configuring gr-soapy support...
-- Dependency SoapySDR_FOUND = 1
-- Dependency ENABLE_GNURADIO
That looked promising but produced the same result.
I found this line in the CMakeCache.txt:
//No help, variable specified on the command line.
CMAKE_PREFIX_PATH:UNINITIALIZED=~/.local
which I don't understand.
I certainly appreciate the suggestions and it encourages me to keep
plugging away. It
You can also try adding:
-DCMAKE_FIND_DEBUG_MODE=ON
to your cmake invocation. This will dump where cmake is trying to find
package files.
If you really get stuck, it may be useful to use a more common install
prefix. Cmake will default to /usr/local and /opt.
I'm a big fan of using /opt. I
