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 out why that didn't
happen. As far as I can tell, CMake should not "find" SoapySDR if its
headers are missing, but maybe that's where it is going wrong.
Cheers,
Ryan
On 2/7/23 5:14 AM, Marcus Müller wrote:
> 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 installation of SoapySDR, precisely?
>
> Best regards,
> Marcus
>
> On 07.02.23 06:19, Ron Economos wrote:
>> You probably need the development package.
>>
>> sudo apt-get install libsoapysdr-dev
>>
>> Ron
>>
>> On 2/6/23 18:37, aardric wrote:
>>> I executed the following steps which I think are consistent with
>>> documentation on the wiki.
>>>
>>> (1) local installation of SoapySDR 0.7.2 appears to work.
>>> (2) build and local install of gnuradio 3.10.5.1 works as expected with
>>> -DENABLE_GR_SOAPY=OFF
>>> (3) delete the gnuradio/build folder and run cmake with
>>> -DENABLE_GR_SOAPY=ON configures without an obvious problem.
>>> (4) however, make fails with:
>>> include/gnuradio/soapy/soapy_types.h:15:10: fatal error:
>>> SoapySDR/Types.hpp: No such file or directory
>>> 15 | #include <SoapySDR/Types.hpp>
>>>
>>> I'm hoping to get advice on whether the above procedure was reasonable
>>> before I (as a non developer) attempts to reverse engineer and debug the
>>> above process. I hesitate to raise an issue for something which may be
>>> obvious or a problem with my particular installation.
>>>
>>> Rick
>>>
>>>
>>>
>>
>
No comments:
Post a Comment