+@image html win_install_01.png Step 1: Accept the license.
+@image html win_install_02.png Step 2: Select packets to install.
+@image html win_install_03.png Step 3: Choice where to install packets previously selected. Please don't use spaces in path.
+@image html win_install_04.png Step 4: Add CLASSPATH to environment variables.
+@image html win_install_05.png Step 5: Add PATH to environment variables.
+@image html win_install_06.png Step 6: Restart your computer to take in consideration environment variables.
+
+@subsection install_binary_java Using the binary jar file
+
+The easiest way to install the Java bindings of SimGrid is to grab the
+jar file from the
+<a href="https://gforge.inria.fr/frs/?group_id=12">Download page</a>,
+and copy it in your classpath (typically, in the same directory than
+your source code). If you go for that version, there is no need to
+install the C library as it is bundled within the jar file. Actually,
+only a bunch of architectures are supported this way to keep the
+jarfile size under control and because we don't have access to every
+exotic architectures ourselves.
+
+If the jarfile fails on you, complaining that your architecture is not
+supported, drop us an email: we may extend the jarfile for you, if we
+have access to your architecture to build SimGrid on it.
+
+@section install_src Installing from source
+
+@subsection install_src_deps Resolving the dependencies
+
+SimGrid only uses very standard tools:
+ @li C compiler, C++ compiler, make and friends.
+ @li perl (but you may try to go without it)
+ @li We use cmake to configure our compilation
+ (<a href="http://www.cmake.org/cmake/resources/software.html">download page</a>).
+ You need cmake version 2.8 or higher. You may want to use ccmake
+ for a graphical interface over cmake.
+
+On MacOSX, it is advised to use the clang compiler (version 3.0 or
+higher), from either MacPort or XCode. If you insist on using gcc on
+this system, you still need a recent version of this compiler, so you
+need an unofficial gcc47 from MacPort because the version provided by
+Apple is ways to ancient to suffice. See also @ref install_cmake_mac.
+
+On Windows, it is strongly advised to use the
+<a href="http://sourceforge.net/projects/mingw/files/MinGW/">MinGW
+environment</a> to build SimGrid. Any other compilers are not tests
+(and thus probably broken). We usually use the
+<a href="http://www.activestate.com/activeperl/downloads">activestate</a>
+version of Perl, and the
+<a href="http://msysgit.googlecode.com/files/Git-1.7.4-preview20110204.exe">msys</a>
+version of git on this architecture, but YMMV. See also @ref install_cmake_win.
+
+@subsection install_src_fetch Retrieving the source
+
+If you just want to use SimGrid, you should probably grab the latest
+stable version available from the
+<a href="https://gforge.inria.fr/frs/?group_id=12">download page</a>.
+We do our best to release soon and release often, but sometimes you
+need to install the developer version of SimGrid, directly from the
+git repository. Avoid the git version if you are not sure, as it may
+break on you, or even worse.
+
+@verbatim
+git clone git://scm.gforge.inria.fr/simgrid/simgrid.git simgrid
+@endverbatim
+
+@subsection install_src_config Configuring the build
+
+Note that compile-time options are very different from @ref options
+"run-time options".
+
+\subsubsection install_cmake_howto Setting compilation options
+
+The default configuration should be ok for most usages, but if you
+need to change something, there is several ways to do so. First, you
+can use environment variable. For example, you can change the used
+compilers by issuing these commands before launching cmake:
+
+@verbatim
+export CC=gcc-4.4
+export CXX=g++-4.4
+@endverbatim
+
+Another way to do so is to use the -D argument of cmake as follows.
+Note that the terminating dot is mandatory (see @ref
+install_cmake_outsrc to understand its meaning).
+
+@verbatim
+cmake -DCC=clang -DCXX=clang++ .
+@endverbatim
+
+Finally, you can use a graphical interface such as ccmake to change
+these settings. Simply follow the instructions after starting the
+interface.
+
+@verbatim
+ccmake .
+@endverbatim
+
+\subsubsection install_cmake_list SimGrid compilation options
+
+In addition to the classical cmake configuration variables, SimGrid
+accepts several options, as listed below.
+
+ @li <b>CMAKE_INSTALL_PREFIX</b> (path): Where to install SimGrid
+ (e.g. /usr/local or /opt).
+
+ @li <b>enable_compile_optimizations</b> (ON/OFF): request the
+ compiler to produce efficient code. You want to activate it,
+ unless you want to debug SimGrid itself (as efficient code may
+ 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.
+
+\subsubsection install_cmake_reset Resetting the compilation configuration
+
+If you need to empty the cache of values saved by cmake (either
+because you added a new library or because something seriously went
+wrong), you can simply delete the file CMakeCache.txt that is created
+at the root of the source tree. You may also want to edit this file
+directly in some circumstances.
+
+\subsubsection install_cmake_outsrc Compiling into a separate directory
+
+By default, the files produced during the compilation are placed in
+the source directory. As the compilation generates a lot of files, it
+is advised to to put them all in a separate directory. It is then
+easier to cleanup, and this allows to compile several configurations
+out of the same source tree. For that, simply enter the directory
+where you want the produced files to land, and invoke cmake (or
+ccmake) with the full path to the simgrid source as last argument.
+This approach is called "compilation out of source tree".
+
+@verbatim
+mkdir build
+cd build
+cmake [options] ..
+make
+@endverbatim