![]() libusb >= v1.0.16 is recommended.įor some distributions, it may be possible to simply pull in a package from an upstream source for a later distro version. If you receive a message similar to the following when running CMake, you'll need to obtain a more recent version of libusb:Ī newer libusb version is needed by libbladeRF. Windows users should use the LIBUSB_PATH CMake variable to specify the location of a the libusb(x) binary distribution. Users that are in a *nix environment and have installed libusb via a package manager, should double check that both the library and development packages for libusb-1.0 (sometimes packaged as libusbx-1.0) are installed. (This will certainly be the case for Windows.) Check your PKG_CONFIG_PATH variable, and ensure that libusb is installed to a location in your system's library search path. If the libusb is reported to not be found, it may be the case that pkgconfig was not able to locate libusb. If you suspect a build is broken due to a warning being treated as an error, please report it via IRC or the issue tracker, and run the following from your build directory as a temporary workaround:Ĭmake -DTREAT_WARNINGS_AS_ERRORS=No. Occasionally, we've seen different compiler versions throw errors that were not seen on developers' machines, breaking master for users. Could not write to si5338 (-5): File or device I/O failureĬonfiguration and Compilation Issues Build fails due to a warning being treated as an errorīy default, builds use -Werror or /WX to treat warnings as errors, with the intent of forcing developers to address any warnings.Linux: Failure to find libbladeRF.so or libbladeRF.so.0.bladeRF-cli detects device in bootloader mode.Device may only be opened by one program.Failing to see or connect to the device.Cannot build libtecla under Mac OSX 10.9 due to missing libgcc.a.Build fails due to a warning being treated as an error. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |