A
lgorithmique
N
umérique
D
istribuée
Public GIT Repository
projects
/
simgrid.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
documentation improvement
[simgrid.git]
/
doc
/
doxygen
/
install.doc
diff --git
a/doc/doxygen/install.doc
b/doc/doxygen/install.doc
index
d65ddad
..
8867f4c
100644
(file)
--- a/
doc/doxygen/install.doc
+++ b/
doc/doxygen/install.doc
@@
-12,18
+12,19
@@
disk and you're set.
Recompiling an official archive is not much more complex, actually.
SimGrid has very few dependencies and rely only on very standard
Recompiling an official archive is not much more complex, actually.
SimGrid has very few dependencies and rely only on very standard
-tools. Recompiling the archive should be done in a few lines:
+tools. First, download the *@SimGridRelease.tar.gz* archive
+from [the download page](https://gforge.inria.fr/frs/?group_id=12).
+Then, recompiling the archive should be done in a few lines:
-@verbatim
-wget https://gforge.inria.fr/frs/download.php/28674/SimGrid-3.9.tar.gz
-tar xf SimGrid-3.9.tar.gz
-cd SimGrid-3.9
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~{.sh}
+tar xf @SimGridRelease.tar.gz
+cd @SimGridRelease
cmake -DCMAKE_INSTALL_PREFIX=/opt/simgrid .
make
make install
cmake -DCMAKE_INSTALL_PREFIX=/opt/simgrid .
make
make install
-@endverbatim
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-If you want to stay on the ble
n
ding edge, you should get the latest
+If you want to stay on the ble
e
ding edge, you should get the latest
git version, and recompile it as you would do for an official archive.
Depending on the files you change in the source tree, some extra
tools may be needed.
git version, and recompile it as you would do for an official archive.
Depending on the files you change in the source tree, some extra
tools may be needed.
@@
-85,8
+86,7
@@
have access to your architecture to build SimGrid on it.
SimGrid only uses very standard tools:
@li C compiler, C++ compiler, make and friends.
SimGrid only uses very standard tools:
@li C compiler, C++ compiler, make and friends.
- @li perl (but you may try to go without it) and libpcre (but we are
- working on removing this dependency)
+ @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
@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
@@
-441,8
+441,6
@@
compiling a source file. There are:
\verbatim
- HelloWorld.c The example source file.
- CMakeLists.txt It allows to configure the project.
\verbatim
- HelloWorld.c The example source file.
- CMakeLists.txt It allows to configure the project.
-- FindPCRE.cmake This finds and links to the pcre library (Normally included
- into Simgrid directory "GnuWin32").
- README This explaination.
\endverbatim
- README This explaination.
\endverbatim
@@
-468,8
+466,8
@@
create a target with the same name of the source.
################
#It creates a target called 'TARGET_NAME.exe' with the sources 'SOURCES'
add_executable(TARGET_NAME SOURCES)
################
#It creates a target called 'TARGET_NAME.exe' with the sources 'SOURCES'
add_executable(TARGET_NAME SOURCES)
-#Links TARGET_NAME with simgrid
and pcre
-target_link_libraries(TARGET_NAME simgrid
pcre
)
+#Links TARGET_NAME with simgrid
+target_link_libraries(TARGET_NAME simgrid)
\endverbatim
\li To initialize and build your project, you'll need to run
\verbatim
\endverbatim
\li To initialize and build your project, you'll need to run
\verbatim