Changes between Version 10 and Version 11 of compiling

Timestamp:

Jul 2, 2012, 4:29:58 PM (13 years ago)

Author:

jweil

Comment:

static linking is default now

compiling

@@ -3 +3 @@
 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 [http://gibuu.physik.uni-giessen.de/Documentation/makefile_robodoc/masterindex.html Makefile Documentation]).
 
-Before compiling, make sure that all [wiki:tools prerequisites] are fulfilled.
+Before compiling, make sure that all [wiki:tools prerequisites] are fulfilled. Note that the whole compilation process is steared by GNU make.
 
-Note that the whole compilation process is steared by GNU make. GiBUU is always compiled statically, so that we get a monolithic executable which does not depend on system libraries (with the exception of Mac OS X where static linking is not supported).
 
 == Choosing a Compiler ==
@@ -38 +37 @@
 Currently this only works with ifort & gfortran, and produces an executable which is suitable for profiling with gprof.
 
+
 == Static vs. Dynamic Linking ==
 
-The GiBUU executable is usually linked statically, in order to be independent of the libraries present on a particular system (an exception is Mac OS, where static linking is not supported). Recently we added the possibility to switch to dynamic linking (e.g. for the case that static libraries are not available). This can be done via:
+Up to release 1.4, the GiBUU executable was always linked statically. Starting with 1.5, dynamic linking is the default, but the old behavior can be recovered via:
 
 {{{
-make STATIC=0
+make STATIC=1
 }}}
 
-Unfortunately this option is not available in the 1.4.x release yet, but will be supported in a future release.
 
 == Floating Point Exceptions ==
@@ -69 +68 @@
 This can potentially be up to four times faster than the standard single-threaded make ("-j1"), since four files can be compiled in parallel.
 
+
 == Rebuilding from scratch ==