About limesuite-feedstock
Feedstock license: BSD-3-Clause
About limesuite
Home: http://wiki.myriadrf.org/Lime_Suite
Package license: Apache-2.0 AND MIT AND BSD-3-Clause
Summary: Driver and GUI for LMS7002M-based (Lime) SDR platforms
Development: https://github.com/myriadrf/LimeSuite
Documentation: https://wiki.myriadrf.org/Lime_Suite
Lime Suite is a collection of software supporting several hardware platforms including the LimeSDR, drivers for the LMS7002M transceiver RFIC, and other tools for developing with LMS7-based hardware. Installing the Lime Suite enables many SDR applications such as GQRX to work with supported hardware through the bundled SoapySDR support module.
The liblimesuite
package contains the main library that other
packages should develop against. The soapysdr-module-lms7
package
contains the Soapy SDR module that supports Lime devices. The
limesuite
package provides the entire software suite, depending
on the previous packages and also providing GUI tools.
For Windows users of liblimesuite
with a LimeSDR (not mini!) device,
this package uses libusb to communicate over USB instead of the standard
CyUSB library which is not open source. If you have used your LimeSDR
with another software package, you will have to switch USB drivers to
one compatible with WinUSB/libusb by installing the WinUSB driver with
Zadig (https://zadig.akeo.ie/) and selecting your Lime device.
For Linux users of liblimesuite
, you will likely want to link the
provided udev rule into your system installation in order for the
hardware to have the correct permissions:
sudo ln -s $CONDA_PREFIX/lib/udev/rules.d/64-limesuite.rules /etc/udev/rules.d/
sudo udevadm control --reload
sudo udevadm trigger
About liblimesuite
Home: http://wiki.myriadrf.org/Lime_Suite
Package license: Apache-2.0 AND MIT AND BSD-3-Clause
Summary: Driver and GUI for LMS7002M-based (Lime) SDR platforms
Development: https://github.com/myriadrf/LimeSuite
Documentation: https://wiki.myriadrf.org/Lime_Suite
Lime Suite is a collection of software supporting several hardware platforms including the LimeSDR, drivers for the LMS7002M transceiver RFIC, and other tools for developing with LMS7-based hardware. Installing the Lime Suite enables many SDR applications such as GQRX to work with supported hardware through the bundled SoapySDR support module.
The liblimesuite
package contains the main library that other
packages should develop against. The soapysdr-module-lms7
package
contains the Soapy SDR module that supports Lime devices. The
limesuite
package provides the entire software suite, depending
on the previous packages and also providing GUI tools.
For Windows users of liblimesuite
with a LimeSDR (not mini!) device,
this package uses libusb to communicate over USB instead of the standard
CyUSB library which is not open source. If you have used your LimeSDR
with another software package, you will have to switch USB drivers to
one compatible with WinUSB/libusb by installing the WinUSB driver with
Zadig (https://zadig.akeo.ie/) and selecting your Lime device.
For Linux users of liblimesuite
, you will likely want to link the
provided udev rule into your system installation in order for the
hardware to have the correct permissions:
sudo ln -s $CONDA_PREFIX/lib/udev/rules.d/64-limesuite.rules /etc/udev/rules.d/
sudo udevadm control --reload
sudo udevadm trigger
About soapysdr-module-lms7
Home: http://wiki.myriadrf.org/Lime_Suite
Package license: Apache-2.0 AND MIT AND BSD-3-Clause
Summary: Driver and GUI for LMS7002M-based (Lime) SDR platforms
Development: https://github.com/myriadrf/LimeSuite
Documentation: https://wiki.myriadrf.org/Lime_Suite
Lime Suite is a collection of software supporting several hardware platforms including the LimeSDR, drivers for the LMS7002M transceiver RFIC, and other tools for developing with LMS7-based hardware. Installing the Lime Suite enables many SDR applications such as GQRX to work with supported hardware through the bundled SoapySDR support module.
The liblimesuite
package contains the main library that other
packages should develop against. The soapysdr-module-lms7
package
contains the Soapy SDR module that supports Lime devices. The
limesuite
package provides the entire software suite, depending
on the previous packages and also providing GUI tools.
For Windows users of liblimesuite
with a LimeSDR (not mini!) device,
this package uses libusb to communicate over USB instead of the standard
CyUSB library which is not open source. If you have used your LimeSDR
with another software package, you will have to switch USB drivers to
one compatible with WinUSB/libusb by installing the WinUSB driver with
Zadig (https://zadig.akeo.ie/) and selecting your Lime device.
For Linux users of liblimesuite
, you will likely want to link the
provided udev rule into your system installation in order for the
hardware to have the correct permissions:
sudo ln -s $CONDA_PREFIX/lib/udev/rules.d/64-limesuite.rules /etc/udev/rules.d/
sudo udevadm control --reload
sudo udevadm trigger
About limesuite
Home: http://wiki.myriadrf.org/Lime_Suite
Package license: Apache-2.0 AND MIT AND BSD-3-Clause
Summary: Driver and GUI for LMS7002M-based (Lime) SDR platforms
Development: https://github.com/myriadrf/LimeSuite
Documentation: https://wiki.myriadrf.org/Lime_Suite
Lime Suite is a collection of software supporting several hardware platforms including the LimeSDR, drivers for the LMS7002M transceiver RFIC, and other tools for developing with LMS7-based hardware. Installing the Lime Suite enables many SDR applications such as GQRX to work with supported hardware through the bundled SoapySDR support module.
The liblimesuite
package contains the main library that other
packages should develop against. The soapysdr-module-lms7
package
contains the Soapy SDR module that supports Lime devices. The
limesuite
package provides the entire software suite, depending
on the previous packages and also providing GUI tools.
For Windows users of liblimesuite
with a LimeSDR (not mini!) device,
this package uses libusb to communicate over USB instead of the standard
CyUSB library which is not open source. If you have used your LimeSDR
with another software package, you will have to switch USB drivers to
one compatible with WinUSB/libusb by installing the WinUSB driver with
Zadig (https://zadig.akeo.ie/) and selecting your Lime device.
For Linux users of liblimesuite
, you will likely want to link the
provided udev rule into your system installation in order for the
hardware to have the correct permissions:
sudo ln -s $CONDA_PREFIX/lib/udev/rules.d/64-limesuite.rules /etc/udev/rules.d/
sudo udevadm control --reload
sudo udevadm trigger
Current build status
Azure |
Current release info
Name | Downloads | Version | Platforms |
---|---|---|---|
Installing limesuite
Installing limesuite
from the conda-forge
channel can be achieved by adding conda-forge
to your channels with:
conda config --add channels conda-forge
conda config --set channel_priority strict
Once the conda-forge
channel has been enabled, liblimesuite, limesuite, soapysdr-module-lms7
can be installed with conda
:
conda install liblimesuite limesuite soapysdr-module-lms7
or with mamba
:
mamba install liblimesuite limesuite soapysdr-module-lms7
It is possible to list all of the versions of liblimesuite
available on your platform with conda
:
conda search liblimesuite --channel conda-forge
or with mamba
:
mamba search liblimesuite --channel conda-forge
Alternatively, mamba repoquery
may provide more information:
# Search all versions available on your platform:
mamba repoquery search liblimesuite --channel conda-forge
# List packages depending on `liblimesuite`:
mamba repoquery whoneeds liblimesuite --channel conda-forge
# List dependencies of `liblimesuite`:
mamba repoquery depends liblimesuite --channel conda-forge
About conda-forge
conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.
A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.
To manage the continuous integration and simplify feedstock maintenance
conda-smithy has been developed.
Using the conda-forge.yml
within this repository, it is possible to re-render all of
this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender
.
For more information please check the conda-forge documentation.
Terminology
feedstock - the conda recipe (raw material), supporting scripts and CI configuration.
conda-smithy - the tool which helps orchestrate the feedstock.
Its primary use is in the construction of the CI .yml
files
and simplify the management of many feedstocks.
conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)
Updating limesuite-feedstock
If you would like to improve the limesuite recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
conda-forge
channel, whereupon the built conda packages will be available for
everybody to install and use from the conda-forge
channel.
Note that all branches in the conda-forge/limesuite-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
- If the version of a package is not being increased, please add or increase
the
build/number
. - If the version of a package is being increased, please remember to return
the
build/number
back to 0.