X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/446e8038598b209dd9f9b6e673a0436dea320b61..1095cadacd735f79bded966f30b4d6ebb1cf13ab:/doc/FAQ.doc diff --git a/doc/FAQ.doc b/doc/FAQ.doc index 577226445c..020d580c94 100644 --- a/doc/FAQ.doc +++ b/doc/FAQ.doc @@ -11,8 +11,10 @@ not familiar with compiling C files under UNIX. If you follow these instructions and still have some troubles, drop an e-mail to . -\subsection faq_compiling Compiling SimGrid +\subsection faq_compiling Compiling SimGrid from an archive +First of all, you need to download the latest version of SimGrid from +here. Suppose you have uncompressed SimGrid in some temporary location of your home directory (say /home/joe/tmp/simgrid-3.0.1 ). The simplest way to use SimGrid is to install it in your home @@ -63,6 +65,48 @@ Thus, there is two ways to link your program with SimGrid: \verbatim export LD_LIBRARY_PATH=$HOME/lib/:$LD_LIBRARY_PATH \endverbatim + +\subsection faq_compiling_cvs Compiling SimGrid from the CVS + +The project development takes place in the cvs, 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 +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 +released one. + +For that, you first need to get the "simgrid" module from +here. + +You won't find any configure and a few other things +(Makefile.in's, documentation, ...) will be missing as well. The +reason for that is that all these files have to be regenerated using the +latest versions of autoconf, libtool, automake +(>1.9) and doxygen (>1.4). To generate the configure and +the Makefile.in's, you just have to launch the bootstrap +command that resides in the top of the source tree. Then just follow the +instructions of Section \ref faq_compiling. + +We insist on the fact that you really need the latest versions of +autoconf and automake. Doing this step on exotic architectures/systems +(i.e. anything different from a recent linux distribution) may be +... uncertain. If you want to use the CVS version on another +architecture/system, you should do the previous steps on a perfectly +standard box, then do a make dist that will build you a +perfectly portable SimGrid archive. + +In summary, the following commands will checkout the CVS, regenerate the +configure script and friends, configure SimGrid and build an archive you can +use on another machine afterward. + +\verbatim cvs -d :pserver:anonymous@scm.gforge.inria.fr:/cvsroot/simgrid login +cvs -d :pserver:anonymous@scm.gforge.inria.fr:/cvsroot/simgrid checkout simgrid +cd simgrid +./bootstrap +./configure --enable-maintainer-mode +make dist \endverbatim + \subsection faq_setting Setting up your own code Do not build your simulator by modifying the SimGrid examples. Go @@ -145,7 +189,9 @@ perform some more complex compilations... \section faq_simgrid I'm new to SimGrid. I have some questions. Where should I start? You are at the right place... Having a look to these -slides +slides +(or to these +"obsolete" slides) may give you some insights on what SimGrid can help you to do and what are its limitations. Then you definitely should read the \ref MSG_examples. There is also a mailing list: . @@ -794,7 +840,8 @@ Here are some tricks I had to use in order to run a token ring between - It was really boring to write 25,000 entries in the deployment file, so I wrote a little script examples/gras/tokenS/make_deployment.pl, which you may - want to adapt to your case. + want to adapt to your case. You could also think about hijacking + the SURFXML parser (have look at \ref faq_flexml_bypassing). - The deployment file became quite big, so I had to do what is in the FAQ entry \ref faq_flexml_limit