set(EXECUTABLE_OUTPUT_PATH "./")
set(LIBRARY_OUTPUT_PATH "${CMAKE_HOME_DIRECTORY}/lib")
-add_executable(get_sender get_sender.c) #add_executable(<name_of_target> <src list>)
+#add_executable(<name_of_target> <src list>)
+add_executable(get_sender get_sender.c)
### Add definitions for compile
-target_link_libraries(get_sender simgrid m pthread) #target_link_libraries(<name_of_targe> <dependencies>)
+#target_link_libraries(<name_of_targe> <dependencies>)
+target_link_libraries(get_sender simgrid m pthread)
\endverbatim
Then you have to modified <project/directory>/buildtools/Cmake/MakeExeLib.cmake and add
\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").
+- FindPCRE.cmake This finds and links to the pcre library (Normally included
+ into Simgrid directory "GnuWin32").
- README This explaination.
\endverbatim
################
# FIND TARGETS #
################
-add_executable(TARGET_NAME SOURCES) #It creates a target called 'TARGET_NAME.exe' with the sources 'SOURCES'
-target_link_libraries(TARGET_NAME simgrid pcre) #Links TARGET_NAME with simgrid and pcre
+#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)
\endverbatim
\li To initialize and build your project, you'll need to run
\verbatim
just an example to illustrate a possible way to compile everything;
feel free to organize it as you want).
- \li <tt>sched.h</tt>: a description of the core of the
- scheduler (i.e. which functions are can be used by the
- agents). For example we could find the following functions
- (master, forwarder, slave).
-
- \li <tt>sched.c</tt>: a C file including <tt>sched.h</tt> and
- implementing the core of the scheduler. Most of these
- functions use the MSG functions defined in section \ref
- msg_task_usage.
-
- \li <tt>masterslave.c</tt>: a C file with the main function, i.e.
- the MSG initialization (MSG_init()), the platform
- creation (e.g. with MSG_create_environment()), the
- deployment phase (e.g. with MSG_function_register() and
- MSG_launch_application()) and the call to
- MSG_main()).
+\li <tt>sched.h</tt>: a description of the core of the
+ scheduler (i.e. which functions are can be used by the
+ agents). For example we could find the following functions
+ (master, forwarder, slave).
+\li <tt>sched.c</tt>: a C file including <tt>sched.h</tt> and
+ implementing the core of the scheduler. Most of these
+ functions use the MSG functions defined in section \ref
+ msg_task_usage.
+\li <tt>masterslave.c</tt>: a C file with the main function, i.e.
+ the MSG initialization (MSG_init()), the platform
+ creation (e.g. with MSG_create_environment()), the
+ deployment phase (e.g. with MSG_function_register() and
+ MSG_launch_application()) and the call to MSG_main()).
To compile such a program, we suggest to use the following
Makefile. It is a generic Makefile that we have used many times with