Linux-Build

How to install LROSE source on Linux?

For most common LINUX systems, you can install lrose from the packages on this page.

For some of the versions of LINUX, we are still having problems with the Qt5-based applications. These problems include both compile errors, and run-time errors related to problems with dynamically-linked libraries. We are working to identify the cause of the problems. In the meantime, we have documented which applications are available on each OS version.

OS-version	fractl	vortrac	samurai	HawkEye	CIDD available?
CENTOS 6	No	No	No	Yes	No
CENTOS 7	Yes	Yes	Yes	Yes	Yes
CENTOS 8	Yes	Yes	Yes	Yes	Yes
Fedora 29	Yes	No	Yes	No	Yes
Fedora 30	Yes	No	Yes	No	Yes
Fedora 31	Yes	No	Yes	No	Yes
Debian 9	Yes	Yes	Yes	No	Yes
Debian 10	Yes	Yes	Yes	No	Yes
Ubuntu 16.04	Yes	Yes	Yes	Yes	Yes
Ubuntu 18.04	Yes	Yes	Yes	Yes	Yes
Suse leap	Yes	Yes	Yes	Yes	Yes
Suse latest	Yes	Yes	Yes	Yes	Yes

1. Prepare: Most good, up-to-date LINUX distributions should work.

Recommended distributions are:

• Debian
• Ubuntu (based on Debian)
• RedHat
• Centos (based on RedHat)
• Fedora (based on RedHat)

First, you will need to install the required packages.

See: LROSE package dependencies

2. Download the source tar file for Linux from: Release A typical source release would be:

lrose-core-20200609.src.tgz

• Create a working directory for building the distribution:

mkdir ~/lrose_build cd ~/lrose_build

• Untar

tar xvfz lrose-core-20200609.src.tgz The distribution will be unpacked into a subdirectory:

cd ~/lrose_build/lrose-core-20200609.src

3. Build

• Run the build script:

To see the usage:

./build_src_release.py --help

To build and install into the default directory: /usr/local/lrose

./build_src_release.py

Or set an install directory:

./build_src_release.py --prefix /my/install/dir

4. Verify

• Look in ~/lrose or /my/install/dir for

include lib bin

• Try the commands:

/usr/local/lrose/bin/RadxPrint -h /usr/local/lrose/bin/RadxConvert -h /usr/local/lrose/bin/Radx2Grid -h /usr/local/lrose/bin/HawkEye

5. Handling build errors

If the build does not complete successfully, you will need to track down the errors.

The very first errors in the build are the most important.

If you get errors, go into the directory giving problems, and run the make as follows:

make |& less and scroll down searching for error.

Alternatively, run

make >& make.log

and then inspect the make.log file, searching for error.

6. Update

To update, just repeat the procedure in sections 2, 3 and 4 above.

The new version will be installed over the previous version.