-If you want modified, add or delete source files from a library you have to edit <project/directory>/tools/cmake/DefinePackages.cmake.
-Chose the section you are interested in and modify it.
-
-\verbatim
-set(SMPI_SRC
- src/smpi/smpi_base.c
- src/smpi/smpi_bench.c
- src/smpi/smpi_c99.c
- src/smpi/smpi_coll.c
- src/smpi/smpi_comm.c
- src/smpi/smpi_global.c
- src/smpi/smpi_group.c
- src/smpi/smpi_mpi.c
- src/smpi/smpi_mpi_dt.c
- src/smpi/smpi_pmpi.c
- src/smpi/smpi_replay.c
- )
-\endverbatim
-
-If your source is always added to the library, you are set. But if
-it's optional, you must ensure that it gets added to the source
-distribution when not compiled in, or it may well be missing if the
-archive is built without the option activating your source. This is
-done by adding the files to the EXTRA_DIST list, as in the following
-example:
-
-\verbatim
-### If fortran is installed compile source other-whise source is only copied in the dist
-if(SMPI_FORTRAN)
- set(SMPI_SRC
- ${SMPI_SRC}
- src/smpi/smpi_f77.c
- )
-else()
- set(EXTRA_DIST
- ${EXTRA_DIST}
- src/smpi/smpi_f77.c
- )
-endif()
-\endverbatim
-
-Don't forget to run the "make distcheck" target after any modification
-to the cmake files: it checks whether all necessary files are present
-in the distribution.
-
-\section inside_cmake_examples How to add an example?
-
-The first rule is that the content of examples/ must be interesting to
-the users. It is expected that the users will take one of these
-examples and start editing it to make it fit their needs.
-So, it should be self-contained, informative and should use only the
-public APIs.
-
-To ensure that all examples actually work as expected, every examples
-are also used as integration test (see \ref inside_tests), but you
-should still strive to keep the code under examples/ as informative as
-possible for the users. In particular, torture test cases should be
-placed in teshsuite/, not examples/, so that the users don't stumble
+To ensure that all examples actually work as expected, every example is also used as an integration test (see
+@ref inside_tests), but you should still strive to keep the code under examples/ as informative as possible for the
+users. In particular, torture test cases should be placed in teshsuite/, not examples/, so that the users don't stumble