Differences

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

--- public:user_software:lofar [2017-03-08 15:27] – external edit 127.0.0.1
+++ public: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.
-:!: 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 LTS/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.
+:!: 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 =====
@@ Line 20: / Line 20: @@
     * 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.
@@ Line 52: / Line 53: @@
 === 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>
@@ Line 84: / Line 85: @@
 $ make [-j n] [-k]
 </code>
-Where the ''-j n'' option denotes parallel build using ''n'' cores of your system (much faster).
+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:
-If you want the build products to be installed as well, add ''install'' to the make command:
+When you want the build products to be installed as well, add ''install'' to the make command:
 <code>
 $ make install