Differences

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

--- public:user_software:lofar [2017-04-21 06:04] – [LOFAR build instructions] Arno Schoenmakers
+++ public:user_software:lofar [2017-04-21 06:08] – [Getting Started] Arno Schoenmakers
@@ Line 52: / Line 52: @@
 === 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 84: @@
 $ 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:
+When you want the build products to be installed as well, add ''install'' to the make command:
-If you want the build products to be installed as well, add ''install'' to the make command:
 <code>
 $ make install