X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/3c8e3b397e8f213abb133ceaa1dd40efbae561b1..44f2cbefae6aa317668fb8cdf9df9a5841c71719:/doc/FAQ.doc
diff --git a/doc/FAQ.doc b/doc/FAQ.doc
index 1a324fd336..b4ccfcea68 100644
--- a/doc/FAQ.doc
+++ b/doc/FAQ.doc
@@ -107,6 +107,17 @@ cd simgrid
./configure --enable-maintainer-mode
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
+to call them explicitely.
+
+If you need to compile the CVS version on a machine where all these
+dependencies are not met, the easiest is to do make dist in the CVS
+dir, on another machine where all dependencies are met. It will create an
+archive you may deploy on other sites just as a regular stable release.
+
\subsection faq_setting_MSG Setting up your own MSG code
Do not build your simulator by modifying the SimGrid examples. Go
@@ -238,11 +249,12 @@ in the meanwhile, simply don't build the examples in cross-compilation
Program (cross-)compiled with mingw32 do request an extra DLL at run-time to be
usable. For example, if you want to test your build with wine, you should do
the following to put this library where wine looks for DLLs.
-\verbatim cp /usr/share/doc/mingw32-runtime/mingwm10.dll.gz ~/.wine/c/windows/system/
+\verbatim
+cp /usr/share/doc/mingw32-runtime/mingwm10.dll.gz ~/.wine/c/windows/system/
gunzip ~/.wine/c/windows/system/mingwm10.dll.gz
\endverbatim
-The DLL is builded in src/.libs, and installed in the /bin directory
+The DLL is builded in src/.libs, and installed in the prefix/bin directory
when you run make install.
If you want to use it in a native project on windows, you need to use