-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Soapy Remote on Windows #1397
Comments
As noted in the release notes, only RTL-SDR and AirSpy devices are supported in the experimental Windows release. Soapy Remote is not available. |
Thanks. Will all of the devices be included in the future? |
Gqrx is maintained by volunteers. Additional device support will be added to the Windows build if and when someone contributes it. In the meantime, if you'd like support for many more devices on Windows, I'd suggest installing Gqrx using Radioconda: https://github.com/ryanvolz/radioconda |
Thanks! good idea. I tried it and it works. |
Gqrx Windows binaries are built using MSYS2. The build steps can be seen here: https://github.com/gqrx-sdr/gqrx/blob/master/.github/workflows/build.yml#L217-L387 If you're able to add support for more hardware, contributions are welcome. |
I am having trouble installing on MSYS2.
|
Gqrx does not need Python support, so you can build without it. Add |
I tried compiling gqrx with -DENABLE_PYTHON=OFF in the cmake command, but it failed with this error The reason is that in my previous message, gr-osmosdr failed with a vague error about a pybind11 Python config failure. I was able to compile NRSC5 on this system, though. By the way, there is no gqrx compile instructions in the build steps page that you sent the link to earlier. |
Sorry, I meant that gr-osmosdr should be built with |
I finally got gr-osmosdr to build and install by adding -DENABLE_PYTHON=OFF. Building gqrx This is the procedure that I used. Is it valid?
I have attached the cmake and build (cmake --build build) terminal output. |
The build steps I linked to above are used to produce automated builds, so I expect they will work if you use them on your machine. |
I looked into what I have to do to run the yml script that you linked. Is there another way to run the yml script? I was able to compile and install gqrx on MSYS2 MINGW64 with python support disabled. Sorry for my rambling, but I'm not used to Docker or SDRs on Windows. I mostly use my Raspberry Pi. |
Actually, it's a workflow configuration for GitHub Actions: https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions
It can't be executed directly. It provides a set of steps that GitHub Actions should execute. But you can copy & paste individual commands from the Windows portion into an MSYS2 terminal to get the same result.
SoapySDR doesn't come with any drivers built in. Each one (e.g. SoapyRemote, SoapyHackRF, etc. needs to be individually built and installed. |
The latest Windows version of gqrx (2.17.5) does not work with Soapy Remote.
When I enter the device string:
driver=remote,remote=tcp://192.168.1.220:55132,remote:driver=sdrplay,soapy=0
I get the message SoapySDR::Device::make() no match
Please select another device.
That device string does work on gqrx 2.14.4 that comes with the PothosSDR Windows development environment.
It also works on the Linux version 2.17.5 that I compiled.
Is Soapy Remote included in the Windows release?
----Steve
The text was updated successfully, but these errors were encountered: