gnuradio / pybombs-docker Goto Github PK

• Make sure PyQt5 (including QtSvg and QtWebEngine) is installed.
• pip install QDarkStyle qtpy
• pip install pytest-qt pyautogui (only required for testing)
• build and install as usual
• Run gnuradio-companion --qt

GNU Radio is a free & open-source software development toolkit that provides signal processing blocks to implement software radios. It can be used with readily-available, low-cost external RF hardware to create software-defined radios, or without hardware in a simulation-like environment. It is widely used in hobbyist, academic, and commercial environments to support both wireless communications research and real-world radio systems.

Please visit the GNU Radio website at https://www.gnuradio.org/ and the wiki at https://wiki.gnuradio.org/. Bugs and feature requests are tracked on GitHub's Issue Tracker. If you have questions about GNU Radio, please search the discuss-gnuradio mailing list archive, as many questions have already been asked and answered. Please also subscribe to the mailing list and post your new questions there.

The recommended way to install GNU Radio on most platforms is using available binary package distributions.

The following command is for Debian, Ubuntu, and derivatives. Consult your distribution information to obtain the version of GNU Radio which is included.

sudo apt install gnuradio

For other operating systems and versions, see Quick Start

For Ubuntu, the latest builds (both released and pulled from master branch) are maintained as PPAs (Personal Package Archives) on launchpad.net. Be sure to uninstall any previously installed versions of gnuradio first. See UnInstallGR.

Platform-specific guides and Cross-platform guides are described in Other Installation Methods.

Complete instructions for building GNU Radio from source code are detailed in Installing From Source.

We are no longer recommending PyBOMBS to install modern versions of GNU Radio.

Some files have been changed many times throughout the years. Copyright notices at the top of source files list which years changes have been made. For some files, changes have occurred in many consecutive years. These files may often have the format of a year range (e.g., "2006 - 2011"), which indicates that these files have had copyrightable changes made during each year in the range, inclusive.