Changes between Version 13 and Version 14 of compiling

Timestamp:

Jan 4, 2017, 8:52:12 PM (8 years ago)

Author:

gallmei

Comment:

cosmetics

compiling

@@ -1 @@
-= Compiling GiBUU =
+ = Compiling GiBUU =
 
 Compiling GiBUU usually is as easy as typing '''make''' in the GiBUU base directory. However, a couple of options are available for special situations (see also [//Documentation/makefile_robodoc/masterindex.html Makefile Documentation]).
 
-Before compiling, make sure that all [wiki:tools prerequisites] are fulfilled. Note that the whole compilation process is steared by GNU make.
+Before compiling, make sure that all [wiki:tools prerequisites] are fulfilled.
+
+
+You may compile your code via
+   make [VAR=val | ...]
+with VAR = ...
+
+ * FORT:
+  * FORT = ifort,gfortran,...
+  * FORT = /path/to/intel/compiler/ifort
+
+ * MODE:
+  * MODE = opt0,opt1,opt2,opt3
+  * MODE = opt4
+  * MODE = opt5
+  * MODE = lto
+  * MODE = prof
+  * MODE = callGraph
+
+ * STATIC:
+  * STATIC = 0|1
+ 
+ * FPE:
+  * FPE = 0|1|2|3
+ 
+ * ARCH:
+  * ARCH = 32
+
+ * ARGS:
+  * ARGS = "..."
 
 
@@ -23 +52 @@
 == Choosing an Optimization Level ==
 
-By default GiBUU is compiled with debugging flags, which is good for development and bug tracking, but the produced executable may be quite slow. If you want an optimized executable, you should compile with
+By default GiBUU is compiled with optimizing flags switched on, corresponding to compiler flags '-O3'. You may change the optimization level by calling e.g.
+{{{
+make MODE=opt1
+}}}
+This works with all compilers and lets you specify the optimization level (0-3). 
 
-{{{
-make MODE=opt3
-}}}
+ 1) Full debugging code for development and bug tracking is generated with
+ {{{
+ make MODE=opt0
+ }}}
 
-This works with all compilers and lets you specify the optimization level (0-3). Another option is to use profiling flags:
 
-{{{
-make MODE=prof
-}}}
+ 2) Another option is to use profiling flags:
+ {{{
+ make MODE=prof
+ }}}
+  Currently this only works with ifort & gfortran, and produces an executable which is suitable for profiling with gprof.
 
-Currently this only works with ifort & gfortran, and produces an executable which is suitable for profiling with gprof.
-
+ 3) In order to get the most optimized code, you may use e.g.
+ {{{
+ make MODE=lto ARGS="-fopenmp -march=native"
+ }}}
 
 == Static vs. Dynamic Linking ==