2 @page install Installing Simgrid
6 The easiest way to install SimGrid is to go for a binary package.
7 Under Debian or Ubuntu, this is very easy as SimGrid is directly
8 integrated to the official repositories. Under Windows, SimGrid can be
9 installed in a few clicks once you downloaded the installer from
10 gforge. If you just want to use Java, simply copy the jar file on your
13 Recompiling an official archive is not much more complex, actually.
14 SimGrid has very few dependencies and rely only on very standard
15 tools. First, download the *@SimGridRelease.tar.gz* archive
16 from [the download page](https://gforge.inria.fr/frs/?group_id=12).
17 Then, recompiling the archive should be done in a few lines:
19 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~{.sh}
20 tar xf @SimGridRelease.tar.gz
22 cmake -DCMAKE_INSTALL_PREFIX=/opt/simgrid .
25 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
27 If you want to stay on the bleeding edge, you should get the latest
28 git version, and recompile it as you would do for an official archive.
29 Depending on the files you change in the source tree, some extra
32 @section install_binary Installing a binary package
34 @subsection install_binary_linux Binary packages for linux
36 Most of the developers use a Debian or Ubuntu system, and some of us
37 happen to be Debian Maintainers, so the packages for these systems are
38 well integrated with these systems and very up-to-date. To install them,
42 apt-get install simgrid
45 On other Linux variants, you probably want to go for a source install.
46 Please contact us if you want to contribute the build scripts for your
47 preferred distribution.
49 @subsection install_binary_win Installation wizard for Windows
51 Before starting the installation, make sure that you have the following dependencies:
52 @li cmake 2.8 <a href="http://www.cmake.org/cmake/resources/software.html">(download page)</a>
53 @li MinGW <a href="http://sourceforge.net/projects/mingw/files/MinGW/">(download page)</a>
54 @li perl <a href="http://www.activestate.com/activeperl/downloads">(download page)</a>
55 @li git <a href="http://msysgit.googlecode.com/files/Git-1.7.4-preview20110204.exe">(download page)</a>
57 Then download the package <a href="https://gforge.inria.fr/frs/?group_id=12">SimGrid Installer</a>,
58 execute it and follow instructions.
60 @image html win_install_01.png Step 1: Accept the license.
61 @image html win_install_02.png Step 2: Select packets to install.
62 @image html win_install_03.png Step 3: Choice where to install packets previously selected. Please don't use spaces in path.
63 @image html win_install_04.png Step 4: Add CLASSPATH to environment variables.
64 @image html win_install_05.png Step 5: Add PATH to environment variables.
65 @image html win_install_06.png Step 6: Restart your computer to take in consideration environment variables.
67 @subsection install_binary_java Using the binary jar file
69 The easiest way to install the Java bindings of SimGrid is to grab the
71 <a href="https://gforge.inria.fr/frs/?group_id=12">Download page</a>,
72 and copy it in your classpath (typically, in the same directory than
73 your source code). If you go for that version, there is no need to
74 install the C library as it is bundled within the jar file. Actually,
75 only a bunch of architectures are supported this way to keep the
76 jar file size under control and because we don't have access to every
77 exotic architectures ourselves.
79 If the jarfile fails on you, complaining that your architecture is not
80 supported, drop us an email: we may extend the jarfile for you, if we
81 have access to your architecture to build SimGrid on it.
83 @section install_src Installing from source
85 @subsection install_src_deps Resolving the dependencies
87 SimGrid only uses very standard tools:
88 - C compiler, C++ compiler, make and friends.
89 - perl (but you may try to go without it)
90 - We use cmake to configure our compilation
91 (<a href="http://www.cmake.org/cmake/resources/software.html">download page</a>).
92 You need cmake version 2.8 or higher. You may want to use ccmake
93 for a graphical interface over cmake.
95 - osX: with <a href="http://www.finkproject.org/">fink</a>: `sudo fink install boost1.53.nopython`
96 - debian: `apt-get install libboost-dev`
98 On MacOSX, it is advised to use the clang compiler (version 3.0 or
99 higher), from either MacPort or XCode. If you insist on using gcc on
100 this system, you still need a recent version of this compiler, so you
101 need an unofficial gcc47 from MacPort because the version provided by
102 Apple is ways to ancient to suffice. See also @ref install_cmake_mac.
104 On Windows, it is strongly advised to use the
105 <a href="http://sourceforge.net/projects/mingw/files/MinGW/">MinGW
106 environment</a> to build SimGrid, with <a href="http://www.mingw.org/wiki/MSYS">
107 MSYS tools</a> installed. Any other compilers are not tested
108 (and thus probably broken). We usually use the
109 <a href="http://www.activestate.com/activeperl/downloads">activestate</a>
110 version of Perl, and the
111 <a href="http://msysgit.googlecode.com/files/Git-1.7.4-preview20110204.exe">msys</a>
112 version of git on this architecture, but YMMV. See also @ref install_cmake_win.
114 @subsection install_src_fetch Retrieving the source
116 If you just want to use SimGrid, you should probably grab the latest
117 stable version available from the
118 <a href="https://gforge.inria.fr/frs/?group_id=12">download page</a>.
119 We do our best to release soon and release often, but sometimes you
120 need to install the developer version of SimGrid, directly from the
121 git repository. Avoid the git version if you are not sure, as it may
122 break on you, or even worse.
125 git clone git://scm.gforge.inria.fr/simgrid/simgrid.git simgrid
128 @subsection install_src_config Configuring the build
130 Note that compile-time options are very different from @ref options
133 \subsubsection install_cmake_howto Setting compilation options
135 The default configuration should be ok for most usages, but if you
136 need to change something, there is several ways to do so. First, you
137 can use environment variables. For example, you can change the used
138 compilers by issuing these commands before launching cmake:
145 Note that other variables are available, such as CFLAGS and CXXFLAGS to add
146 options for respectively the C compiler and the C++ compiler.
148 Another way to do so is to use the -D argument of cmake as follows.
149 Note that the terminating dot is mandatory (see @ref
150 install_cmake_outsrc to understand its meaning).
153 cmake -DCC=clang -DCXX=clang++ .
156 Finally, you can use a graphical interface such as ccmake to change
157 these settings. Simply follow the instructions after starting the
164 \subsubsection install_cmake_list SimGrid compilation options
166 In addition to the classical cmake configuration variables, SimGrid
167 accepts several options, as listed below.
169 @li <b>CMAKE_INSTALL_PREFIX</b> (path): Where to install SimGrid
170 (e.g. /usr/local or /opt).
172 @li <b>enable_compile_optimizations</b> (ON/OFF): request the
173 compiler to produce efficient code. You want to activate it,
174 unless you want to debug SimGrid itself (as efficient code may
175 be appear mangled to the debuggers).
177 @li <b>enable_debug</b> (ON/OFF): disable this if simulation speed
178 really matters to you. All log messages of gravity debug or
179 below will be discarded at compilation time. Since there is
180 quite a bunch of such log messages in SimGrid itself, this can
181 reveal faster than discarding them at runtime as usually. But of
182 course, it is then impossible to get any debug message from
183 SimGrid if something goes wrong.
185 @li <b>enable_model-checking</b> (ON/OFF): Only enable this if you
186 actually plan to use the model-checking aspect of SimGrid. This
187 mode of execution is still under heavy work, but it should be
188 rather usable now. Be <b>warned</b> that this option will hinder
189 your simulation speed even if you simulate without activating
190 the model-checker. We are working on improving this situation.
192 @li <b>enable_compile_warnings</b> (ON/OFF): request the compiler to
193 issue error message whenever the source code is not perfectly
194 clean. If you develop SimGrid itself, you must activate it to
195 ensure the code quality, but as a user, that option will only
198 @li <b>enable_maintainer_mode</b> (ON/OFF): you only need to set
199 this option if you modify very specific parts of SimGrid itself
200 (the XML parsers and other related elements). Adds an extra
201 dependency on flex and flexml.
203 @li <b>enable_tracing</b> (ON/OFF): disable this if you have issues
204 with the tracing module. But this module is now very stable and
205 you really should try to enjoy this beauty.
207 @li <b>enable_smpi</b> (ON/OFF): disable this if you have issues
208 with the module allowing to run MPI code on top of SimGrid. This
209 module very stable, but if you really don't need it, you can
212 @li <b>enable_mallocators</b> (ON/OFF): disable this when tracking
213 memory issues within SimGrid, or the caching mechanism used
214 internally will fool the debuggers.
216 @li <b>enable_jedule</b> (ON/OFF): enable this to get SimDag
217 producing traces that can then be visualized with the Jedule
220 @li <b>enable_lua</b> (ON/OFF): enable this if you want to enjoy the
221 lua bindings of SimGrid. Adds an extra dependency on lua library
222 and developer header files.
225 @li <b>enable_ns3</b> (ON/OFF): whether you want to use ns3.
226 See section @ref pls_simgrid_configuration_ns3.
227 @li <b>NS3_HINT</b> (path): Where to search for NS3 (eg /usr or /opt).
228 @li <b>enable_latency_bound_tracking</b> (ON/OFF): enable it if you
229 want to be warned when communications are limited by round trip
230 time while doing packet-level simulation.
231 @li <b>enable_documentation</b> (ON/OFF) : whether the documentation should be
232 generated during the compilation. Default is ON.
234 \subsubsection install_cmake_reset Resetting the compilation configuration
236 If you need to empty the cache of values saved by cmake (either
237 because you added a new library or because something seriously went
238 wrong), you can simply delete the file CMakeCache.txt that is created
239 at the root of the source tree. You may also want to edit this file
240 directly in some circumstances.
242 \subsubsection install_cmake_outsrc Compiling into a separate directory
244 By default, the files produced during the compilation are placed in
245 the source directory. As the compilation generates a lot of files, it
246 is advised to to put them all in a separate directory. It is then
247 easier to cleanup, and this allows to compile several configurations
248 out of the same source tree. For that, simply enter the directory
249 where you want the produced files to land, and invoke cmake (or
250 ccmake) with the full path to the SimGrid source as last argument.
251 This approach is called "compilation out of source tree".
260 \subsubsection install_cmake_win Cmake on Windows (with MinGW + MSYS)
262 Cmake can produce several kind of of makefiles. Under Windows, it has
263 no way of determining what kind you want to use, so you have to hint it:
266 cmake -G "MSYS Makefiles" (other options) .
270 \subsubsection install_cmake_mac Cmake on Mac OS X
272 SimGrid compiles like a charm with clang on Mac OS X:
275 cmake -DCMAKE_C_COMPILER=/path/to/clang -DCMAKE_CXX_COMPILER=/path/to/clang++ .
279 With the XCode version of clang 4.1, you may get the following error message:
281 CMake Error: Parse error in cache file build_dir/CMakeCache.txt. Offending entry: /SDKs/MacOSX10.8.sdk
284 In that case, edit the CMakeCache.txt file directly, so that the
285 CMAKE_OSX_SYSROOT is similar to the following. Don't worry about the
286 warning that the "-pthread" argument is not used, if it appears.
288 CMAKE_OSX_SYSROOT:PATH=/Applications/XCode.app/Contents/Developer/Platforms/MacOSX.platform/Developer
291 \subsection install_src_compil Compiling SimGrid
293 In most cases, compiling and installing SimGrid is enough:
297 make install # try "sudo make install" if you don't have the permission to write
300 In addition, several compilation targets are provided in SimGrid. If
301 your system is well configured, the full list of targets is available
302 for completion when using the Tab key. Note that some of the existing
303 targets are not really for public consumption so don't worry if some
304 stuff don't work for you.
307 make simgrid Build only the SimGrid library and not any example
308 make masterslave Build only this example (and its dependencies)
309 make clean Clean the results of a previous compilation
310 make install Install the project (doc/ bin/ lib/ include/)
311 make uninstall Uninstall the project (doc/ bin/ lib/ include/)
312 make dist Build a distribution archive (tgz)
313 make distcheck Check the dist (make + make dist + tests on the distribution)
314 make doc Create SimGrid documentation
317 If you want to see what is really happening, try adding VERBOSE=1 to
318 your compilation requests:
324 @subsection install_src_test Testing SimGrid
326 Once everything is built, you may want to test the result. SimGrid
327 comes with an extensive set of regression tests (see @ref
328 inside_cmake_addtest "that page of the insider manual" for more
329 details). Running the tests is done using the ctest binary that comes
330 with cmake. These tests are run every night and the result is publicly
331 <a href="http://cdash.inria.fr/CDash/index.php?project=Simgrid">available</a>.
334 ctest # Launch all tests
335 ctest -D Experimental # Launch all tests and report the result to
336 # http://cdash.inria.fr/CDash/index.php?project=SimGrid
337 ctest -R msg # Launch only the tests which name match the string "msg"
338 ctest -j4 # Launch all tests in parallel, at most 4 at the same time
339 ctest --verbose # Display all details on what's going on
340 ctest --output-on-failure # Only get verbose for the tests that fail
342 ctest -R msg- -j5 --output-on-failure # You changed MSG and want to check that you didn't break anything, huh?
343 # That's fine, I do so all the time myself.
346 \section install_setting_own Setting up your own code
348 \subsection install_setting_MSG MSG code on Unix (Linux or Mac OSX)
350 Do not build your simulator by modifying the SimGrid examples. Go
351 outside the SimGrid source tree and create your own working directory
352 (say <tt>/home/joe/SimGrid/MyFirstScheduler/</tt>).
354 Suppose your simulation has the following structure (remember it is
355 just an example to illustrate a possible way to compile everything;
356 feel free to organize it as you want).
358 \li <tt>sched.h</tt>: a description of the core of the
359 scheduler (i.e. which functions are can be used by the
360 agents). For example we could find the following functions
361 (master, forwarder, slave).
362 \li <tt>sched.c</tt>: a C file including <tt>sched.h</tt> and
363 implementing the core of the scheduler. Most of these
364 functions use the MSG functions defined in section \ref
366 \li <tt>masterslave.c</tt>: a C file with the main function, i.e.
367 the MSG initialization (MSG_init()), the platform
368 creation (e.g. with MSG_create_environment()), the
369 deployment phase (e.g. with MSG_function_register() and
370 MSG_launch_application()) and the call to MSG_main()).
372 To compile such a program, we suggest to use the following
373 Makefile. It is a generic Makefile that we have used many times with
374 our students when we teach the C language.
378 masterslave: masterslave.o sched.o
380 INSTALL_PATH = $$HOME
382 PEDANTIC_PARANOID_FREAK = -O0 -Wshadow -Wcast-align \
383 -Waggregate-return -Wmissing-prototypes -Wmissing-declarations \
384 -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations \
385 -Wmissing-noreturn -Wredundant-decls -Wnested-externs \
386 -Wpointer-arith -Wwrite-strings -finline-functions
387 REASONABLY_CAREFUL_DUDE = -Wall
388 NO_PRAYER_FOR_THE_WICKED = -w -O2
389 WARNINGS = $(REASONABLY_CAREFUL_DUDE)
390 CFLAGS = -g $(WARNINGS)
392 INCLUDES = -I$(INSTALL_PATH)/include
393 DEFS = -L$(INSTALL_PATH)/lib/
394 LDADD = -lm -lsimgrid
398 $(CC) $(INCLUDES) $(DEFS) $(CFLAGS) $^ $(LIBS) $(LDADD) -o $@
401 $(CC) $(INCLUDES) $(DEFS) $(CFLAGS) -c -o $@ $<
404 rm -f $(BIN_FILES) *.o *~
410 The first two lines indicates what should be build when typing make
411 (<tt>masterslave</tt>) and of which files it is to be made of
412 (<tt>masterslave.o</tt> and <tt>sched.o</tt>). This makefile assumes
413 that you have set up correctly your <tt>LD_LIBRARY_PATH</tt> variable
414 (look, there is a <tt>LDADD = -lm -lsimgrid</tt>). If you prefer using
415 the static version, remove the <tt>-lsimgrid</tt> and add a
416 <tt>$(INSTALL_PATH)/lib/libsimgrid.a</tt> on the next line, right
417 after the <tt>LIBS = </tt>.
419 More generally, if you have never written a Makefile by yourself, type
420 in a terminal: <tt>info make</tt> and read the introduction. The
421 previous example should be enough for a first try but you may want to
422 perform some more complex compilations...
425 \subsection install_setting_win_provided Compile the "HelloWorld" project on Windows
427 In the SimGrid install directory you should have an HelloWorld project to explain you how to start
428 compiling a source file. There are:
430 - HelloWorld.c The example source file.
431 - CMakeLists.txt It allows to configure the project.
432 - README This explanation.
435 Now let's compile this example:
436 \li Run windows shell "cmd".
437 \li Open HelloWorld Directory ('cd' command line).
438 \li Create a build directory and change directory. (optional)
439 \li Type 'cmake -G"MinGW Makefiles" \<path_to_HelloWorld_project\>'
441 \li You should obtain a runnable example ("HelloWorld.exe").
443 For compiling your own code you can simply copy the HelloWorld project and rename source name. It will
444 create a target with the same name of the source.
447 \subsection install_setting_win_new Adding and Compiling a new example on Windows
449 \li Put your source file into the helloWord directory.
450 \li Edit CMakeLists.txt by removing the Find Targets section and add those two lines into this section
455 #It creates a target called 'TARGET_NAME.exe' with the sources 'SOURCES'
456 add_executable(TARGET_NAME SOURCES)
457 #Links TARGET_NAME with simgrid
458 target_link_libraries(TARGET_NAME simgrid)
460 \li To initialize and build your project, you'll need to run
462 cmake -G"MinGW Makefiles" <path_to_HelloWorld_project>
464 \li Run "mingw32-make"
465 \li You should obtain "TARGET_NAME.exe".
467 \subsection install_Win_ruby Setup a virtualbox to use SimGrid-Ruby on windows
469 Allan Espinosa made these set of Vagrant rules available so that you
470 can use the SimGrid Ruby bindings in a virtual machine using
471 VirtualBox. Thanks to him for that. You can find his project here:
472 https://github.com/aespinosa/simgrid-vagrant