\endverbatim
-\subsection faq_compiling_cvs Compiling SimGrid from the CVS
+\subsection faq_compiling_svn Compiling SimGrid from the SVN
-The project development takes place in the cvs, where all changes are
+The project development takes place in the svn, where all changes are
commited when they happen. Then every once in a while, we make sure that the
code quality meets our standard and release an archive from the code in the
-CVS. We afterward go back to the development in the CVS. So, if you need a
+SVN. We afterward go back to the development in the SVN. So, if you need a
recently added feature and can afford some little problem with the stability
-of the lastest features, you may want to use the CVS version instead of a
+of the lastest features, you may want to use the SVN version instead of a
released one.
For that, you first need to get the "simgrid" module from
We insist on the fact that you really need the latest versions of
autoconf, automake and libtool. Doing this step on exotic architectures/systems
(i.e. anything different from a recent linux distribution) may be
-... uncertain. If you need to compile the CVS version on a machine where all these
-dependencies are not met, the easiest is to do <tt>make dist</tt> in the CVS
+... uncertain. If you need to compile the SVN version on a machine where all these
+dependencies are not met, the easiest is to do <tt>make dist</tt> in the SVN
dir of another machine where all dependencies are met. It will create an
archive you may deploy on other sites just as a regular stable release.
-In summary, the following commands will checkout the CVS, regenerate the
+In summary, the following commands will checkout the SVN, regenerate the
configure script and friends, configure SimGrid and build it.
-\verbatim cvs -d :pserver:anonymous@scm.gforge.inria.fr:/cvsroot/simgrid login
-cvs -d :pserver:anonymous@scm.gforge.inria.fr:/cvsroot/simgrid checkout simgrid
+\verbatim svn checkout svn://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk
+mv trunk simgrid
cd simgrid
./bootstrap
./configure --enable-maintainer-mode --prefix=<where to install SimGrid>
Then, if you want to install SimGrid on the current box, just do:
\verbatim make install \endverbatim
-If you want to build an snapshot of the CVS to deploy it on another box (for
+If you want to build an snapshot of the SVN to deploy it on another box (for
example because the other machine don't have the autotools), do:
\verbatim make dist \endverbatim
Moreover, you should never call the autotools manually since you must run
them in a specific order with specific arguments. Most of the times, the
makefiles will automatically call the tools for you. When it's not possible
-(such as the first time you checkout the CVS), use the ./bootstrap command
+(such as the first time you checkout the SVN), use the ./bootstrap command
to call them explicitely.
environments (MSG and SD) have good chances to work, but we didn't test
ourselves. This section explains how we generate the SimGrid DLL so that you
can build it for yourself. First of all, you need to have a version more
-recent than 3.1 (ie, a CVS version as time of writting).
+recent than 3.1 (ie, a SVN version as time of writting).
In order to cross-compile the package to windows from linux, you need to
install mingw32 (minimalist gnu win32). On Debian, you can do so by
You can use the VPATH support of configure to compile at the same time for
linux and windows without dupplicating the source nor cleaning the tree
-between each. Just run bootstrap (if you use the CVS) to run the autotools.
+between each. Just run bootstrap (if you use the SVN) to run the autotools.
Then, create a linux and a win directories. Then, type:
\verbatim cd linux; ../configure --srcdir=.. <usual configure flags>; make; cd ..
cd win; ../configure --srcdir=.. --host=i586-mingw32msvc <flags>; make; cd ..
easily that what you change for one arch does not break the other one.
It is possible that this VPATH build thing breaks from time to time in the
-CVS since it's quite fragile, but it's granted to work in any released
+SVN since it's quite fragile, but it's granted to work in any released
version. If you experience problems, drop us a mail.
Another possible source of issue is that at the moment, building the
planned because this is a very specific need (and doing it in a
generic way is thus very hard). However some people have implemented
their own batch schedulers. Vincent Garonne wrote one during his PhD
-and put his code in the contrib directory of our CVS so that other can
+and put his code in the contrib directory of our SVN so that other can
keep working on it. You may find inspinring ideas in it.
\subsubsection faq_MIA_checkpointing I need a checkpointing thing
<platform_description version="1">
\endverbatim
You should try to use the surfxml_update.pl script that can be found
-<a href="http://gforge.inria.fr/plugins/scmcvs/cvsweb.php/contrib/platform_generation/?cvsroot=cvsroot%2Fsimgrid">here</a>.
+<a href="https://gforge.inria.fr/plugins/scmsvn/viewcvs.php/contrib/trunk/platform_generation/?rev=4721&root=simgrid"">here</a>.
\subsection faq_trouble_valgrind Valgrind-related issues
