Re: Porting gr-osmosdr to gr-3.9 without swig.
Hi Volker Did you succeeded in porting gr-osmosdr to GR3.9 ? Do you have some repository for this ? Regards, Christophe On 14/09/2020 17:10, Volker Schroer wrote: Hi Chris, I started gr-osmosdr some month ago, but I had to interrupt due to other coding needs. What gr-osmosdr repository did you start with ? I forked https://github.com/argilo/gr-osmosdr.git which had some preparations for 3.9, but at that time gr3.9 still used swig. First I ported successfully some of my oot modules to 3.9 the way described in the porting guide. But for more complex modules I tried another way. I removed the swig part and looked at my ported modules, how to add the pybind part. At the moment I'm at the point af generating the bindings. -- Volker
Re: Porting gr-osmosdr to gr-3.9 without swig.
Hi Chris, I started gr-osmosdr some month ago, but I had to interrupt due to other coding needs. What gr-osmosdr repository did you start with ? I forked https://github.com/argilo/gr-osmosdr.git which had some preparations for 3.9, but at that time gr3.9 still used swig. First I ported successfully some of my oot modules to 3.9 the way described in the porting guide. But for more complex modules I tried another way. I removed the swig part and looked at my ported modules, how to add the pybind part. At the moment I'm at the point af generating the bindings. -- Volker
Porting gr-osmosdr to gr-3.9 without swig.
Hello All, I was wondering if anyone had successfully built gr-osmosdr against gnuradio-3.9 now that we don't use swig? I have looked at https://wiki.gnuradio.org/index.php/GNU_Radio_3.9_OOT_Module_Porting_Guide and haven't figured out how to port gr-osmosdr. I've gotten to '4. (in 3.8 OOT) Call gr_modtool bind for each block in your OOT' and don't know where to go from there. I have tried various combinations of gr_modtool bind block arguments with no success. Continuing without adding bind blocks. I run my cmake build command and get... chris [ ~/src/gnuradio/gr-osmosdr/build ]$ cmake ../ CMake Warning (dev) at /usr/share/cmake-3.18/Modules/GNUInstallDirs.cmake:225 (message): Unable to determine default CMAKE_INSTALL_LIBDIR directory because no target architecture is known. Please enable at least one language before including GNUInstallDirs. Call Stack (most recent call first): CMakeLists.txt:24 (include) This warning is for project developers. Use -Wno-dev to suppress it. -- Build type not specified: defaulting to release. CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): The package name passed to `find_package_handle_standard_args` (PkgConfig) does not match the name of the calling package (GMP). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /usr/share/cmake-3.18/Modules/FindPkgConfig.cmake:59 (find_package_handle_standard_args) /opt/gnuradio/lib/cmake/gnuradio/FindGMP.cmake:1 (include) /opt/gnuradio/lib/cmake/gnuradio/FindMPLIB.cmake:1 (find_package) /usr/share/cmake-3.18/Modules/CMakeFindDependencyMacro.cmake:47 (find_package) /opt/gnuradio/lib/cmake/gnuradio/GnuradioConfig.cmake:14 (find_dependency) CMakeLists.txt:45 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): The package name passed to `find_package_handle_standard_args` (PkgConfig) does not match the name of the calling package (MPIR). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /usr/share/cmake-3.18/Modules/FindPkgConfig.cmake:59 (find_package_handle_standard_args) /opt/gnuradio/lib/cmake/gnuradio/FindMPIR.cmake:1 (include) /opt/gnuradio/lib/cmake/gnuradio/FindMPLIB.cmake:2 (find_package) /usr/share/cmake-3.18/Modules/CMakeFindDependencyMacro.cmake:47 (find_package) /opt/gnuradio/lib/cmake/gnuradio/GnuradioConfig.cmake:14 (find_dependency) CMakeLists.txt:45 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Checking for module 'mpir >= 3.0' -- No package 'mpir' found -- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR) -- Found Boost: /usr/lib/cmake/Boost-1.74.0/BoostConfig.cmake (found suitable version "1.74.0", minimum required is "1.74.0") found components: date_time program_options filesystem system regex thread unit_test_framework CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): The package name passed to `find_package_handle_standard_args` (VOLK) does not match the name of the calling package (Volk). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /usr/lib/cmake/volk/VolkConfig.cmake:32 (find_package_handle_standard_args) /usr/share/cmake-3.18/Modules/CMakeFindDependencyMacro.cmake:47 (find_package) /opt/gnuradio/lib/cmake/gnuradio/GnuradioConfig.cmake:34 (find_dependency) CMakeLists.txt:45 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- User set python executable /usr/bin/python3 -- Found PythonLibs: /usr/lib/libpython3.8.so (found suitable exact version "3.8.5") -- Found ALSA 1.2.3.2 -- Extracting version information from git describe... -- Found Boost: /usr/lib/cmake/Boost-1.74.0/BoostConfig.cmake (found suitable version "1.74.0", minimum required is "1.65") found components: chrono thread system -- -- The build system will automatically enable all components. -- Use -DENABLE_DEFAULT=OFF to disable components by default. -- Searching for GNURadio-Blocks... -- Found GNURadio-Blocks: 1 -- Searching for IQ Balance... -- Could NOT find gnuradio-iqbalance (missing: gnuradio-iqbalance_DIR) -- Found IQ Balance: 0 -- Searching for UHD Drivers... CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): The package name passed to `find_package_handle_standard_args` (PkgConfig) does not match the name of the calling package (UHD). This can lead to problems in calling code that expects
