public:user_software:lofar

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:user_software:lofar [2013-03-12 13:41] – Marcel Loosepublic:user_software:lofar [2017-06-06 20:19] (current) – [Prerequisites] 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 RHEL5 32-bit and Ubuntu 10.04 64-bit Linux distros. For other distros and/or versions we cannot guarantee that a build will create a fully and correctly working package.+:!: Please take note that ASTRON only thoroughly builds and tests the LOFAR software on their production systems that contain CentOs 7.2 and Ubuntu 12.04 LTS 64-bit Linux distros. For other distros and/or versions we cannot guarantee that a build will create a fully and correctly working package. Support for this is not provided.
  
 ===== 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's package repository.
   * boost 1.40 or larger   * boost 1.40 or larger
   * cfitsio 3.23 or larger   * cfitsio 3.23 or larger
-  * wcslib 4.3 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 1.4 or larger, and its dependencies (lapack, blas, fftw, etc.); see http://code.google.com/p/casacore/ +  * casacore 2.0.3 or latest version and its dependencies (lapack, blas, fftw, etc.); see https://github.com/casacore 
-  * pyrap (see http://code.google.com/p/pyrap ) +  * casacore-python 2.0.1 or latest version (see https://github.com/casacore) 
-  * casarest (see https://github.com/pkgw/casarest )+  * casarest latest development version (see https://github.com/pkgw/casarest or its local mirror https://svn.astron.nl/casarest/)
   * log4cplus 1.0.4 or larger   * log4cplus 1.0.4 or larger
-  +  * AOFlagger 2.7.1 or larger (http://sourceforge.net/projects/aoflagger/)  
 +    * Note: use the -DBUILD_SHARED_LIBS=ON flag! See http://sourceforge.net/p/aoflagger/wiki/installation_instructions/ 
 +    * If you want to use the graph tools of the AOFlagger, in the lofar build you need to provide ''-DMAKE_AOFlagger=OFF'' to Cmake. Otherwise, the LOFAR build will built the (older) graph tools. 
 +  * PyBDSF 1.8.11 or larger (https://github.com/lofar-astron/PyBDSF) as of LOFAR Release 2.21 (June 2017). 
 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 28:
 LOFAR uses [[http://www.cmake.org|CMake]] as build tool. For general information on CMake, please refer to the [[http://www.cmake.org/cmake/help/documentation.html|CMake documentation pages]].  LOFAR uses [[http://www.cmake.org|CMake]] as build tool. For general information on CMake, please refer to the [[http://www.cmake.org/cmake/help/documentation.html|CMake documentation pages]]. 
  
-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't, or if it's too old, you can [[http://www.cmake.org/cmake/resources/software.html|download the CMake sources]] and build CMake yourself.+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't, or if it's too old, you can [[http://www.cmake.org/cmake/resources/software.html|download the CMake sources]] and build CMake yourself.
  
 ===== Getting Started ===== ===== Getting Started =====
Line 44: Line 48:
 </code> </code>
  
-Please refer to [[engineering:software:lofarsvn|The LOFAR Subversion Repository]] page for more information on how to check out LOFAR 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:documentation:lofarsvn|The LOFAR Subversion Repository]] page (password protected) for more information on how to check out LOFAR 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:software:development:lofar_buildenv_manual.pdf|LOFAR Build Environment}}. So, for example, when using the ''GNU'' compiler suite to build a ''debug'' version of the software, you'd have to create a build directory named ''gnu_debug''.+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:software:development:lofar_buildenv_manual.pdf|LOFAR Build Environment}}. So, for example, when using the ''GNU'' compiler suite to build a ''debug'' version of the software, you'd have to create a build directory named ''gnu_debug''. Other options are ''gnu_opt'' for optimized build without debug symbols, or ''gnucxx11-opt'' if your system supports ''cxx11''.
  
 <code> <code>
Line 69: Line 75:
 </code> </code>
  
-FIXME Add package list!+Most users probaly need the Offline programs (NDP3, BBS, Imager) and/or the pipeline framework. To build all these, you can provide as package ''Offline''.  
 + 
 +A complete package list, useful for those who are familiar with the code organization, can be found in the file ''CMake/LofarPackageList.cmake''.
  
 === Step 4 === === Step 4 ===
Line 75: Line 83:
  
 <code> <code>
-$ make+$ make [-j n] [-k]
 </code> </code>
 +Where the ''-j n'' option denotes parallel build using ''n'' cores of your system (much faster). If you want the build to continue even when encountering errors in the build process, you can add the ''-k'' flag to the make command. 
  
-If you want the build to continue even when encountering errors in the build process, you can add the ''-k'' flag to the make command. For instance: +When you want the build products to be installed as well, add ''install'' to the make command:
-<code> +
-$ make -k  +
-</code> +
-If you want the the build executables to be installed as well, add ''install'' to the make command as well:+
 <code> <code>
 $ make install  $ make install 
 </code> </code>
  
-Note that the install option only works when the make has completed without errors.+Note that the install option only works when the previous make step has completed without errors.
  
 == Note == == Note ==
Line 95: Line 100:
 ===== Build Options ===== ===== Build Options =====
 Build options can be specified in two ways. The preferred, "static" way of doing this is through the different variants files. These settings can be overridden by the user, either by setting options on the command-line when invoking ''cmake'', or by edit them by using the semi-graphical environment ''ccmake''. Build options can be specified in two ways. The preferred, "static" way of doing this is through the different variants files. These settings can be overridden by the user, either by setting options on the command-line when invoking ''cmake'', or by edit them by using the semi-graphical environment ''ccmake''.
 +
 +==== Packages ====
 +
 +To find external packages (like casacore, aoflagger, etc) one can add directory pointers to the CMake command line like these:<code>
 +-DCASACORE_ROOT_DIR=/opt/cep/casacore/current
 +-DAOFLAGGER_ROOT_DIR=/opt/cep/aoflagger/current
 +</code>
 +etc.
 +
  
 ==== Available Options ==== ==== Available Options ====
  • Last modified: 2013-03-12 13:41
  • by Marcel Loose