With this commit, we build without warnings on Arch Linux; CentOS 7; Debian 8 and 9; latest Fedora; Ubuntu 14.04, 16.04, 17.10, and 18.04; Visual Studio 2017; and macOS 10.13.3 w/ Homebrew. * host: libbladeRF: compile AD9361 srcs with -std=gnu11 Fixes compile errors involving ‘for’ loop initial declarations only allowed in C99 or C11 mode, on older GCCs. * host: libbladeRF/adi: remove stdbool workaround This is not necessary now that we're building to -std=gnu11, and in fact, it seems to create a conflict. * host: libbladeRF: pre-declare loop variables Some compilers are not happy with declaring the loop variable in the for statement. Begrudgingly placate them. * host: libbladeRF_test: pre-declare loop variables Some compilers are not happy with declaring the loop variable in the for statement. Begrudgingly placate them. * host: bladeRF-cli: pre-declare loop variables Some compilers are not happy with declaring the loop variable in the for statement. Begrudgingly placate them. * host: libbladeRF: remove refs to strings.h Windows doesn't have strings.h, but string.h seems to do just fine. * host: libbladeRF: fix windows compile errors (WIP) * host: libbladeRF/ad9361: fix windows compile error "IGNORE" is #define'd in the Windows environment, creating a conflict. Renaming this to solve the conflict. * host: common: add setenv implementation for Windows * host: libbladeRF: build setenv.c stub on Windows * host: bladeRF-cli: use setenv stub on Windows * host: common: fixup spacing consistency in setenv * host: libbladeRF: cast channel macros to bladerf_channel Visual Studio is picky about this, and throws warnings. * host: libbladeRF: bladerf2.c: undo workaround for bladerf_channel * host: libbladeRF: bladerf_get_gain_stages count type is now size_t This fixes a Windows compile error, and is also generally more sensible. * host: bladeRF-cli: fix windows compile errors * host: ad9361: fix variadic macro syntax Fixes Windows build errors * host: ad9361: rename _DEBUG to AD9361_DEBUG Visual Studio automagically sets _DEBUG if the /MDd option is set. Turns out that a lot of the debugging sections don't build in Visual Studio, so this accounts for a large number of the build errors... * host: libbladeRF: fixes for Visual Studio builds * host: common: fixes for Visual Studio builds * host: libbladeRF/ad9361: fixes for Visual Studio builds * host: libbladeRF_test: fixes for Visual Studio builds * host: bladeRF-cli: fixes for Visual Studio builds * host: bladeRF-cli: fix static analysis warnings Fixes potential memory leak in main Fixes unused values in set_adf_refclk, set_samplerate * host: common: fix static analysis warnings fixes: unread variable in perform_rx_cal memory leaks in add_arg, add_opt * host: libbladeRF: fix static analysis warnings fixes unused variables in bladerf2_set_gain and xb100_enable |
||
|---|---|---|
| .. | ||
| doc | ||
| include | ||
| src | ||
| bladerf.rc.in | ||
| CHANGELOG | ||
| CMakeLists.txt | ||
| libbladeRF.pc.in | ||
| README.md | ||
bladeRF Library (libbladeRF)
This is the source for the library which interacts with the bladeRF device.
It is meant to be used as a simple and intuitive way to think about not just the bladeRF device itself, but most any radio hardware. Fundamental operations such as setting the tuning frequency, manipulating switches on the board for different paths, and changing the different transmit and receive gains are all parts of a radio system which need to be exposed at a library level.
Functionality provided by this library includes:
- Opening/closing devices and querying information about them
- Tuning to various frequencies
- Configuring the sample rate
- Configuring the bandwidth and gain of the RF chain
- Configuring RF gains
- Transmitting and receiving complex baseband samples
- Updating the device's firmware and FPGA
- Low-level access to on-board devices, for testing and debugging
Please see the CHANGELOG file for a summary of changes across libbladeRF versions.
Documentation
For more information, one can generate and view the API documentation. From your host/build directory, run:
cmake -DBUILD_DOCUMENTATION=ON ../
make libbladeRF-doxygen
The HTML documentation will be placed in <build dir>/libraries/libbladerf/doc/doxygen/html. The index.html file is the "main" documentation page.
This API documentation is available online at: https://nuand.com/libbladeRF-doc
Build Variables
Below is a list of useful and project-specific CMake options. Please see the CMake [variable list] in CMake's documentation for more information.
| Option | Description |
|---|---|
| -DBUILD_LIBBLADERF_DOCUMENTATION=<ON/OFF> | Builds API documentation using Doxygen. Default: equal to BUILD_DOCUMENTATION |
| -DENABLE_BACKEND_USB=<ON/OFF> | Enables USB backends in libbladeRF. Default: ON |
| -DENABLE_BACKEND_LIBUSB=<ON/OFF> | Enables libusb backend. Default: ON if libusb is available, OFF otherwise. |
| -DENABLE_BACKEND_CYAPI=<ON/OFF>a | Enables (Windows-only) Cypress driver/library based backend. Default: ON if the FX3 SDK is available, OFF otherwise. |
| -DENABLE_BACKEND_DUMMY=<ON/OFF> | Enables dummy backend support. Only useful for some developers. Default: OFF |
| -DENABLE_LIBBLADERF_LOGGING=<ON/OFF> | Enable log messages. Default: ON |
| -DENABLE_LIBBLADERF_SYSLOG=<ON/OFF> | Enable log messages to syslog (Linux/OSX) if ENABLE_LIBBLADERF_LOGGING is enabled. Default: OFF |
| -DENABLE_LIBBLADERF_SYNC_LOG_VERBOSE=<ON/OFF> | Enable log_verbose() calls in the sync interface's data path. Note that this may harm performance. Default: OFF |
| -DENABLE_LOCK_CHECKS=<ON/OFF> | Enable checks for lock acquistion failures (e.g., deadlock). Default: OFF |
| -DENABLE_USB_DEV_RESET_ON_OPEN=<ON/OFF> | Enable USB port reset when opening a device. Defaults to ON for Linux, OFF otherwise. |
| -DLIBUSB_PATH=</path/to/libusb> | Path to libusb files. This is generally only needed for Windows users who downloaded binary distributions. |
| -DLIBBLADERF_SEARCH_PREFIX_OVERRIDE=<path> | Override path prefix used by libbladeRF to search for files (e.g., FPGA bitstreams). If not specified, ${CMAKE_INSTALL_PREFIX} is used as the default search prefix. This may be required when cross-compiling. |