- be appear mangled to the debugers).
-
- @li <b>enable_debug</b> (ON/OFF): disable this if simulation speed
- really matters to you. All log messages of gravity debug or
- below will be discarded at compilation time. Since there is
- quite a bunch of such log messages in SimGrid itself, this can
- reveal faster than discarding them at runtime as usually. But of
- course, it is then impossible to get any debug message from
- SimGrid if something goes wrong.
-
- @li <b>enable_msg_deprecated</b> (ON/OFF): enable this option if
- your code used a feature of Simgrid that was droped or modified
- in recent releases of SimGrid. You should update your code if
- possible, but with this option, SimGrid will try to emulate its
- old behavior.
-
- @li <b>enable_model-checking</b> (ON/OFF): Only enable this if you
- actually plan to use the model-checking aspect of SimGrid. This
- mode of execution is still under heavy work, but it should be
- rather usable now. Be <b>warned</b> that this option will hinder
- your simulation speed even if you simulate without activating
- the model-checker. We are working on improving this situation.
-
- @li <b>enable_supernovae</b> (ON/OFF): If you use an ancient
- compiler (such as gcc prior to 4.6), you want to enable this
- option to ensure that the whole SimGrid library is presented to
- the compiler as a unique compilation unit to allow cross-units
- optimizations. This is useless on modern compilers (and will
- soon be droped).
-
- @li <b>enable_compile_warnings</b> (ON/OFF): request the compiler to
- issue error message whenever the source code is not perfectly
- clean. If you develop SimGrid itself, you must activate it to
- ensure the code quality, but as a user, that option will only
- bring you issues.
-
- @li <b>enable_lib_static</b> (ON/OFF): enable this if you want to
- compile the static library (but you should consider enjoying
- this new century instead).
-
- @li <b>enable_maintainer_mode</b> (ON/OFF): you only need to set
- this option if you modify very specific parts of SimGrid itself
- (the XML parsers and other related elements). Adds an extra
- dependency on flex and flexml.
-
- @li <b>enable_tracing</b> (ON/OFF): disable this if you have issues
- with the tracing module. But this module is now very stable and
- you really should try to enjoy this beauty.
-
- @li <b>enable_smpi</b> (ON/OFF): disable this if you have issues
- with the module allowing to run MPI code on top of SimGrid. This
- module very stable, but if you really don't need it, you can
- disable it.
-
- @li <b>enable_mallocators</b> (ON/OFF): disable this when tracking
- memory issues within SimGrid, or the caching mechanism used
- internally will fool the debugers.
-
- @li <b>enable_jedule</b> (ON/OFF): enable this to get SimDag
- producing traces that can then be vizualized with the Jedule
- external tool.
-
- @li <b>enable_lua</b> (ON/OFF): enable this if you want to enjoy the
- lua bindings of SimGrid. Adds an extra dependency on lua library
- and developper header files.
-
-
- @li <b>enable_gtnets</b> (ON/OFF): whether you want to use gtnets.
- See section @ref pls_simgrid_configuration_gtnets.
- @li <b>gtnets_path</b> (path): GTNetS installation directory
- (eg /usr or /opt).
- @li <b>enable_ns3</b> (ON/OFF): whether you want to use ns3.
- See section @ref pls_simgrid_configuration_ns3.
- @li <b>ns3_path</b> (path): NS3 installation directory (eg /usr or /opt).
- @li <b>enable_latency_bound_tracking</b> (ON/OFF): enable it if you
- want to be warned when communications are limited by round trip
- time while doing packet-level simulation.
+ be appear mangled to the debuggers).
+
+ @li <b>enable_compile_warnings</b> (ON/OFF): request the compiler to issue error messages whenever the source code is
+ not perfectly clean. If you are a SimGrid developer, you have to activate this option to enforce the code quality.
+ As a regular user, this option is likely to bring you issues only.
+
+ @li <b>enable_debug</b> (ON/OFF): disable this if simulation speed really matters to you. All log messages of
+ gravity debug or below will be discarded at compilation time. As there is quite a bunch of such log messages in
+ SimGrid internals, this can reveal faster than discarding them at runtime as usual. However, it thus obviously
+ becomes impossible to get any debug message from SimGrid if something goes wrong.
+
+ @li <b>enable_documentation</b> (ON/OFF) : whether the documentation should be generated during the compilation.
+
+ @li <b>enable_jedule</b> (ON/OFF): enable this to get SimDag producing execution traces that can then be visualized
+ with the Jedule external tool.
+
+ @li <b>enable_lua</b> (ON/OFF): enable this if you want to enjoy the lua bindings of SimGrid. Adds an extra dependency
+ on the lua library and developer header files.
+
+ @li <b>enable_maintainer_mode</b> (ON/OFF): you only need to set this option if you modify very specific parts of
+ SimGrid itself (e.g., the XML parsers and other related elements). Moreover, this adds an extra dependency on
+ flex and flexml.
+
+ @li <b>enable_mallocators</b> (ON/OFF): disable this when tracking memory issues within SimGrid, or the caching
+ mechanism used internally will fool the debuggers.
+
+ @li <b>enable_model-checking</b> (ON/OFF): Only enable this if you actually plan to use the model-checking feature of
+ SimGrid. This execution mode is still under heavy work, but should be rather usable now. Be <b>warned</b> that
+ this option will hinder simulation speed even if you simulate without activating the model-checker. We are
+ working on improving this situation.
+
+ @li <b>enable_ns3</b> (ON/OFF): whether you want to use ns-3. See section @ref pls_simgrid_configuration_ns3.
+
+ @li <b>enable_smpi</b> (ON/OFF): disable this if you have issues with the module allowing to run MPI code on top of
+ SimGrid. This module is very stable, but if you don't really need it, you can disable it safely.