mirror of
https://github.com/f4exb/sdrangel.git
synced 2026-06-05 15:34:57 -04:00
cmake files cleanup and build simplification
This commit is contained in:
f4exb
@@ -29,11 +29,7 @@ if(LIBUSB_FOUND AND LIBBLADERF_FOUND)
|
||||
add_subdirectory(bladerf2input)
|
||||
endif(LIBUSB_FOUND AND LIBBLADERF_FOUND)
|
||||
|
||||
if(LIBUSB_FOUND AND UNIX)
|
||||
FIND_PATH (ASOUNDH alsa/asoundlib.h)
|
||||
FIND_LIBRARY (LIBASOUND asound)
|
||||
endif()
|
||||
if(LIBASOUND AND ASOUNDH)
|
||||
if(LIBUSB_FOUND)
|
||||
add_subdirectory(fcdpro)
|
||||
add_subdirectory(fcdproplus)
|
||||
endif()
|
||||
|
||||
@@ -8,7 +8,7 @@ This input sample source plugin gets its samples from a [Airspy HF+ device](http
|
||||
|
||||
The plugin will be built only if the [Airspy HF library](https://github.com/airspy/airspyhf) is installed in your system.
|
||||
|
||||
If you build it from source and install it in a custom location say: `/opt/install/libairspyhf` you will have to add `-DLIBRTLSDR_INCLUDE_DIR=/opt/install/libairspyhf/include -DLIBRTLSDR_LIBRARIES=/opt/install/libairspyhf/lib/libairspyhf.so` to the cmake command line.
|
||||
If you build it from source and install it in a custom location say: `/opt/install/libairspyhf` you will have to add `-DAIRSPYHF_DIR=/opt/install/libairspyhf` to the cmake command line.
|
||||
|
||||
Note: if you use binary distributions this is included in the bundle.
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ This input sample source plugin gets its samples from a [BladeRF1 device](https:
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
The plugin will be built only if the [BladeRF host library](https://github.com/Nuand/bladeRF) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/libbladeRF` you will have to add `-DLIBBLADERF_INCLUDE_DIR=/opt/install/libbladeRF/include -DLIBBLADERF_LIBRARIES=/opt/install/libbladeRF/lib/libbladeRF.so` to the cmake command line.
|
||||
The plugin will be built only if the [BladeRF host library](https://github.com/Nuand/bladeRF) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/libbladeRF` you will have to add `-DBLADERF_INCLUDE_DIR=/opt/install/libbladeRF` to the cmake command line.
|
||||
|
||||
Note that libbladeRF v2 with git tag 2018.08 should be used (official release). The FPGA image v0.7.3 should be used accordingly. The FPGA .rbf file should be copied to the folder where the `sdrangel` binary resides. You can download FPGA images from [here](https://www.nuand.com/fpga_images/)
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ This input sample source plugin gets its samples from a [BladeRF 2.0 micro devic
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
The plugin will be built only if the [BladeRF host library](https://github.com/Nuand/bladeRF) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/libbladeRF` you will have to add `-DLIBBLADERF_INCLUDE_DIR=/opt/install/libbladeRF/include -DLIBBLADERF_LIBRARIES=/opt/install/libbladeRF/lib/libbladeRF.so` to the cmake command line.
|
||||
The plugin will be built only if the [BladeRF host library](https://github.com/Nuand/bladeRF) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/libbladeRF` you will have to add `-DBLADERF_INCLUDE_DIR=/opt/install/libbladeRF` to the cmake command line.
|
||||
|
||||
Note that libbladeRF v2 with git tag 2018.08 should be used (official release). The FPGA image v0.7.3 should be used accordingly. The FPGA .rbf file should be copied to the folder where the `sdrangel` binary resides. You can download FPGA images from [here](https://www.nuand.com/fpga_images/)
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ This input sample source plugin gets its samples from a [HackRF device](https://
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
The plugin will be built only if the [HackRF host library](https://github.com/mossmann/hackrf) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/libhackrf` you will have to add `-DLIBHACKRF_INCLUDE_DIR=/opt/install/libhackrf/include -DLIBHACKRF_LIBRARIES=/opt/install/libhackrf/lib/libhackrf.so` to the cmake command line.
|
||||
The plugin will be built only if the [HackRF host library](https://github.com/mossmann/hackrf) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/libhackrf` you will have to add `-DHACKRF_DIR=/opt/install/libhackrf` to the cmake command line.
|
||||
|
||||
The HackRF Host library is also provided by many Linux distributions and is built in the SDRangel binary releases.
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ The plugin will be built only if LimeSuite is installed in your system. To build
|
||||
|
||||
Then add the following defines on `cmake` command line:
|
||||
|
||||
`-DLIMESUITE_INCLUDE_DIR=/opt/install/LimeSuite/include -DLIMESUITE_LIBRARY=/opt/install/LimeSuite/lib/libLimeSuite.so`
|
||||
`-DLIMESUITE_DIR=/opt/install/LimeSuite`
|
||||
|
||||
<h2>Installation from binary packages</h2>
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ This plugin will be built only if the following conditions are met:
|
||||
- [My fork of libperseus-sdr library](https://github.com/f4exb/libperseus-sdr.git) is installed in your system. You will have to checkout the `fixes` branch which however is the default. There are a few fixes from the original mainly to make it work in a multi-device context.
|
||||
- The 24 bit Rx DSP chain is activated in the compilation with the `-DRX_SAMPLE_24BIT=ON` option on the cmake command line.
|
||||
|
||||
If you build it from source and install it in a custom location say: `/opt/install/libperseus` you will have to add `-DLIBPERSEUS_INCLUDE_DIR=/opt/install/libperseus/include -DLIBPERSEUS_LIBRARIES=/opt/install/libperseus/lib/libperseus-sdr.so` to the cmake command line.
|
||||
If you build it from source and install it in a custom location say: `/opt/install/libperseus` you will have to add `-DPERSEUS_DIR=/opt/install/libperseus` to the cmake command line.
|
||||
|
||||
☞ From version 3.12.0 the Linux binaries are built with the 24 bit Rx option and Perseus input plugin.
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ The plugin will be built only if libiio is installed in your system. To build an
|
||||
|
||||
Then add the following defines on `cmake` command line when compiling SDRangel:
|
||||
|
||||
`-DLIBIIO_INCLUDE_DIR=/opt/install/libiio/include -DLIBIIO_LIBRARY=/opt/install/libiio/lib/libiio.so`
|
||||
`-DIIO_DIR=/opt/install/libiio`
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ This input sample source plugin gets its samples from a [RTLSDR device](http://w
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
The plugin will be built only if the [RTLSDR host library](https://github.com/f4exb/librtlsdr) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/librtlsdr` you will have to add `-DLIBRTLSDR_INCLUDE_DIR=/opt/install/librtlsdr/include -DLIBRTLSDR_LIBRARIES=/opt/install/librtlsdr/lib/librtlsdr.so` to the cmake command line.
|
||||
The plugin will be built only if the [RTLSDR host library](https://github.com/f4exb/librtlsdr) is installed in your system. If you build it from source and install it in a custom location say: `/opt/install/librtlsdr` you will have to add `-DRTLSDR_DIR=/opt/install/librtlsdr` to the cmake command line.
|
||||
|
||||
If you want to benefit from the direct sampling you will have to compile and install this library else the RTLSDR library is also provided by many Linux distributions. The SDRangel binary releases are compiled with the direct sampling option.
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ It is present only in Linux binary releases.
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
The plugin will be built only if the [CM256cc library](https://github.com/f4exb/cm256cc) is installed in your system. For CM256cc library you will have to specify the include and library paths on the cmake command line. Say if you install cm256cc in `/opt/install/cm256cc` you will have to add `-DCM256CC_INCLUDE_DIR=/opt/install/cm256cc/include/cm256cc -DCM256CC_LIBRARIES=/opt/install/cm256cc/lib/libcm256cc.so` to the cmake commands.
|
||||
The plugin will be built only if the [CM256cc library](https://github.com/f4exb/cm256cc) is installed in your system. For CM256cc library you will have to specify the include and library paths on the cmake command line. Say if you install cm256cc in `/opt/install/cm256cc` you will have to add `-DCM256CC_DIR=/opt/install/cm256cc` to the cmake commands.
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ Driver is too unstable in Windows randomly stopping the application and causing
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
As mentioned already the plugin depends on libmirisdr-4. You will have to compile it and install it in your system. When installed in non standard folders the include and library paths have to be specified on the cmake command line. Say if you install `libmirisdr-4` in `/opt/install/libmirisdr` you will have to add `-DLIBMIRISDR_INCLUDE_DIR=/opt/install/libmirisdr/include -DLIBMIRISDR_LIBRARIES=/opt/install/libmirisdr/lib/libmirisdr.so` on the cmake command line.
|
||||
As mentioned already the plugin depends on libmirisdr-4. You will have to compile it and install it in your system. When installed in non standard folders the include and library paths have to be specified on the cmake command line. Say if you install `libmirisdr-4` in `/opt/install/libmirisdr` you will have to add `-DMIRISDR_DIR=/opt/install/libmirisdr` on the cmake command line.
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ The plugin will be built only if XTRX support libraries are installed in your sy
|
||||
|
||||
If libraries are installed in a custom place like `/opt/install/xtrx-images` add the following defines on `cmake` command line:
|
||||
|
||||
`-DLIMESUITE_INCLUDE_DIR=/opt/install/xtrx-images/include -DLIMESUITE_LIBRARY=/opt/install/xtrx-images/lib/libxtrx.so`
|
||||
`-DXTRX_DIR=/opt/install/xtrx-images`
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user