Fix a link in the doc

[simgrid.git] / doc / doxygen / install.doc

diff --git a/doc/doxygen/install.doc b/doc/doxygen/install.doc
index 366b75c..d65e4ed 100644 (file)
--- a/doc/doxygen/install.doc
+++ b/doc/doxygen/install.doc
@@ -138,8 +138,8 @@ can use environment variables. 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
+export CC=gcc-4.7
+export CXX=g++-4.7
 @endverbatim
 
 Note that other variables are available, such as CFLAGS and CXXFLAGS to add
@@ -182,12 +182,6 @@ accepts several options, as listed below.
       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 dropped 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
@@ -201,10 +195,6 @@ accepts several options, as listed below.
       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
@@ -232,13 +222,9 @@ accepts several options, as listed below.
       and developer 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>NS3_HINT</b> (path): Where to search for NS3 (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.
@@ -341,13 +327,11 @@ Once everything is built, you may want to test the result. SimGrid
 comes with an extensive set of regression tests (see @ref
 inside_cmake_addtest "that page of the insider manual" for more
 details). Running the tests is done using the ctest binary that comes
-with cmake. These tests are run every night and the result is publicly
-<a href="http://cdash.inria.fr/CDash/index.php?project=Simgrid">available</a>.
+with cmake. These tests are run for every commit and the result is
+publicly <a href="https://ci.inria.fr/simgrid/">available</a>.
 
 \verbatim
 ctest                    # Launch all tests
-ctest -D Experimental     # Launch all tests and report the result to
-                          # http://cdash.inria.fr/CDash/index.php?project=SimGrid
 ctest -R msg              # Launch only the tests which name match the string "msg"
 ctest -j4                 # Launch all tests in parallel, at most 4 at the same time
 ctest --verbose           # Display all details on what's going on