X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/abc6c695d534ee87fe91c84038ebbf6b9226575d..156f0f11e98a981785e3ba7cd4daa4ab81ba4b33:/examples/msg/actions/actions.c diff --git a/examples/msg/actions/actions.c b/examples/msg/actions/actions.c index edaed915e6..e45e988dde 100644 --- a/examples/msg/actions/actions.c +++ b/examples/msg/actions/actions.c @@ -7,7 +7,7 @@ #include #include #include "msg/msg.h" /* Yeah! If you want to use msg, you need to include msg/msg.h */ -#include "simix/simix.h" /* semaphores for the barrier */ +#include "simgrid/simix.h" /* semaphores for the barrier */ #include "xbt.h" /* calloc, printf */ #include "instr/instr_private.h" @@ -24,8 +24,8 @@ * In such situations, SimGrid allows to write your protocol in your * C file, and the events to react to in a separate text file. * Declare a function handling each of the events that you want to - * accept in your trace files, register them using @ref - * MSG_action_register in your main, and then use @ref + * accept in your trace files, register them using \ref + * MSG_action_register in your main, and then use \ref * MSG_action_trace_run to launch the simulation. You can either * have one trace file containing all your events, or a file per * simulated process. Check the tesh files in the example directory