Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
public:user_software:lofar [2015-04-20 09:38] – [Prerequisites] Arno Schoenmakers | public:user_software:lofar [2017-04-21 06:07] – [Getting Started] Arno Schoenmakers | ||
---|---|---|---|
Line 3: | Line 3: | ||
This page describes how to obtain and build LOFAR the software. | This page describes how to obtain and build LOFAR the software. | ||
- | :!: Please take note that ASTRON only thoroughly builds and tests the LOFAR software on their production systems that contain | + | :!: Please take note that ASTRON only thoroughly builds and tests the LOFAR software on their production systems that contain |
===== Prerequisites ===== | ===== Prerequisites ===== | ||
- | Mind that to be able to build LOFAR, first you need to have various other custom packages available on your system, among which (this is not a complete list): | + | Mind that to be able to build LOFAR, first you need to have various other custom packages available on your system. below is a list of packages and versions that have been confiormed to work (other versions may work, but we have not tested that). Note that this is not a complete list. If there is no URL provided, the package can usually be installed as part of the OS distribution of from the Distributor' |
* boost 1.40 or larger | * boost 1.40 or larger | ||
* cfitsio 3.23 or larger | * cfitsio 3.23 or larger | ||
- | * wcslib 4.25 or larger | + | * wcslib 4.8 or larger |
- | * cmake 2.6.2 or larger | + | * cmake 2.8 or larger |
* hdf5 1.8.4 or larger | * hdf5 1.8.4 or larger | ||
- | * casacore | + | * casacore |
- | * pyrap latest | + | * casacore-python 2.0.1 or latest version (see https://github.com/casacore) |
- | * casarest latest development version (see https:// | + | * casarest latest development version (see https:// |
* log4cplus 1.0.4 or larger | * log4cplus 1.0.4 or larger | ||
- | | + | * AOFlagger 2.7.1 or larger (http:// |
+ | * Note: use the -DBUILD_SHARED_LIBS=ON flag! See http:// | ||
+ | * If you want to use the graph tools of the AOFlagger, in the lofar build you need to provide '' | ||
+ | | ||
Some Linux distributions may have ready to install packages available for some of these, for other distros you may need to build these from code or search hard for binary installations. You may require your system managers help to set all these up properly. | Some Linux distributions may have ready to install packages available for some of these, for other distros you may need to build these from code or search hard for binary installations. You may require your system managers help to set all these up properly. | ||
Line 24: | Line 27: | ||
LOFAR uses [[http:// | LOFAR uses [[http:// | ||
- | You will need CMake 2.6 or later in order to build the LOFAR software. Most development was done using CMake 2.6.2. Most Linux distributions contain CMake as a binary package. If yours doesn' | + | You will need CMake 2.8 or later in order to build the LOFAR software. Most Linux distributions contain CMake as a binary package. If yours doesn' |
===== Getting Started ===== | ===== Getting Started ===== | ||
Line 44: | Line 47: | ||
</ | </ | ||
- | Please refer to [[engineering:software: | + | This requires an account on the SVN server. There is also a guest read-only account; mail Arno Schoenmakers or Marcel Loose for details if you need this. |
+ | |||
+ | Please refer to [[public:user_software: | ||
=== Step 2 === | === Step 2 === | ||
- | Create a build directory, preferably outside of the source tree. The name of the directory must adhere to the naming conventions described in section 3.6 of {{engineering: | + | Create a build directory, preferably outside of the source tree. The name of the directory must adhere to the naming conventions described in section 3.6 of {{engineering: |
< | < | ||
Line 77: | Line 82: | ||
< | < | ||
- | $ make | + | $ make [-j n] [-k] |
</ | </ | ||
+ | Where the '' | ||
If you want the build to continue even when encountering errors in the build process, you can add the '' | If you want the build to continue even when encountering errors in the build process, you can add the '' | ||
- | < | + | |
- | $ make -k | + | If you want the build products |
- | </ | + | |
- | If you want the the build executables | + | |
< | < | ||
$ make install | $ make install | ||
</ | </ | ||
- | Note that the install option only works when the make has completed without errors. | + | Note that the install option only works when the previous |
== Note == | == Note == | ||
Line 97: | Line 101: | ||
===== Build Options ===== | ===== Build Options ===== | ||
Build options can be specified in two ways. The preferred, " | Build options can be specified in two ways. The preferred, " | ||
+ | |||
+ | ==== Packages ==== | ||
+ | |||
+ | To find external packages (like casacore, aoflagger, etc) one can add directory pointers to the CMake command line like these:< | ||
+ | -DCASACORE_ROOT_DIR=/ | ||
+ | -DAOFLAGGER_ROOT_DIR=/ | ||
+ | </ | ||
+ | etc. | ||
+ | |||
==== Available Options ==== | ==== Available Options ==== |