gnss-sdr | GNSS-SDR , an open-source software-defined GNSS receiver | Audio Utils library

This section describes how to set up the compilation environment in GNU/Linux or macOS / Mac OS X, and to build GNSS-SDR. See also our build and install page.
If you want to start building and running GNSS-SDR as quickly and easily as possible, the best option is to install all the required dependencies as binary packages.
This option is adequate if you are interested in development, in working with the most recent versions of software dependencies, want more fine-tuning on the installed versions, or simply in building everything from the scratch just for the fun of it. In such cases, we recommend using PyBOMBS (Python Build Overlay Managed Bundle System), GNU Radio's meta-package manager tool that installs software from source, or whatever the local package manager is, that automatically does all the work for you. Please take a look at the configuration options and general PyBOMBS usage at https://github.com/gnuradio/pybombs. Here we provide a quick step-by-step tutorial.
The full stop separated from cmake by a space is important. CMake will figure out what other libraries are currently installed and will modify Armadillo's configuration correspondingly. CMake will also generate a run-time armadillo library, which is a combined alias for all the relevant libraries present on your system (e.g., BLAS, LAPACK, and ATLAS).
Go to GNSS-SDR's build directory:.
Import project using Menu File -> Import.
Select General -> Existing projects into workspace.
Select your root directory: Browse and select your newly created eclipse/ directory. Keep "Copy projects into workspace" unchecked.
Click on "Finish" and you will get a fully functional Eclipse project.
For more information, check out our quick start guide.
After building the code, you will find the gnss-sdr executable file at gnss-sdr/install. You can make it available everywhere else by sudo make install. Run the profilers volk_profile and volk_gnsssdr_profile for testing all available VOLK kernels for each architecture supported by your processor. This only has to be done once.
In post-processing mode, you have to provide a captured GNSS signal file. 1. The signal file can be easily recorded using the GNU Radio file sink in gr_complex<float> mode. 2. You will need a GPS active antenna, a USRP and a suitable USRP daughter board to receive GPS L1 C/A signals. GNSS-SDR requires to have at least 2 MHz of bandwidth in 1.57542 GHz. (remember to enable the DC bias with the daughterboard jumper). We use a DBSRX2 to do the task, but you can try the newer Ettus' daughter boards as well. 3. The easiest way to capture a signal file is to use the GNU Radio Companion GUI. Only two blocks are needed: a USRP signal source connected to a complex float file sink. You need to tune the USRP central frequency and decimation factor using the USRP signal source properties box. We suggest using a decimation factor of 20 if you use the USRP2. This will give you 100/20 = 5 MSPS which will be enough to receive GPS L1 C/A signals. The front-end gain should also be configured. In our test with the DBSRX2 we obtained good results with G=50. 4. Capture at least 80 seconds of signal in open sky conditions. During the process, be aware of USRP driver buffer underruns messages. If your hard disk is not fast enough to write data at this speed you can capture it to a virtual RAM drive. 80 seconds of signal at 5 MSPS occupies less than 3 Gbytes using gr_complex<float>. If you have no access to an RF front-end, you can download a sample raw data file (that contains GPS and Galileo signals) from here.
You are ready to configure the receiver to use your captured file among other parameters: The default configuration file resides at /usr/local/share/gnss-sdr/conf/default.conf. You need to review/modify at least the following settings: SignalSource.filename= (absolute or relative route to your GNSS signal captured file) GNSS-SDR.internal_fs_sps= (captured file sampling rate in samples per second) SignalSource.sampling_frequency= (captured file sampling rate in samples per second) SignalConditioner.sample_freq_in= (captured file sampling rate in samples per second) SignalConditioner.sample_freq_out= (captured file sampling rate in samples per second) The configuration file has in-line documentation, you can try to tune the number of channels and several receiver parameters. Store your .conf file in some working directory of your choice.
Run the receiver invoking the configuration by $ gnss-sdr --config_file=/path/to/my_receiver.conf The program reports the current status in text mode, directly to the terminal window. If all goes well, and GNSS-SDR is able to successfully track and decode at least 4 satellites, you will get PVT fixes. The program will write .kml, .geojson and RINEX files in the folder from which gnss-sdr was run. In addition to the console output, GNSS-SDR also writes log files at /tmp/ (configurable with the commandline flag ./gnss-sdr --log_dir=/path/to/log).