need help building SoapySDR with VS2022

[JellyImages]

I tried the build guide instructions, which seem quite dated, and although something built, it does not work. When running soapysdrutil --info, I get a flurry of dll load failures. If finds the modules for all the various devices, but for each one the LoadLibrary call fails due to dll initialization failure.

I'd like to use soapy to replace my own hand-coded dongle interface code, and I'd greatly prefer not to have to do the binary install of all the rest of the pothos stuff. FYI, I did this, and soapy works as expected with the full install, but I would very much like to build just the soapysdr dll and the modules to make installing my SDR application on other machines much simpler.

Also, I note that the VS build is debug x64. Wouldn't it be better to build release x64? I know that with my own code (all C++), it simply won't run in real-time in a debug build due to the massive amounts of computation required (I run a 96-channel polyphase channelizer with 96 separate FM demodulators on the output). Thanks for whatever help anyone can provide with building soapy on Windows using the latest free Visual Studio.

[righthal...@gmail.com]

Which build guide instructions are you following ?

If the system variable "path" includes the path to your dlls, you should not be having any problems.

I and most other users of SoapySDR use the  pothos stuff on windows and build the separate soapySDR libraries everywhere else.

If you are not processing the data in real time, you could use a program like SdrGlut to capture the I/Q data to a file for later processing.

https://github.com/righthalfplane/SdrGlut/releases/tag/v1.31

https://www.youtube.com/watch?v=N_384vv7IWY

[JellyImages]

I'm using the instructions in the wiki here:

https://github.com/pothosware/SoapySDR/wiki/BuildGuide

I'm using VS2022 Community Version on Win11

As I said, it builds fine, but doesn't run correctly due to the module dlls failing to load even though it finds them.

[righthal...@gmail.com]

Show the output of the failed sequence - I have seen several types of load failures -  may be you are getting a familiar one.