You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The swig/python directory should operate as its own CMake project
So once soapysdr the c++ library is built and installed, you can invoke swig/python/ in parallel to build against as many different python installations as needed
That what I had done for other build systems at least
While working on reproducible builds for openSUSE, I found that
our
soapy-sdr
0.8.1 build output can vary, unless we run non-parallel builds.There is some race condition in the build-system about how the python and python3 files are created.
Is there a way to always generate the python3 variant after the python one?
The text was updated successfully, but these errors were encountered: