From: Martin Quinson Date: Thu, 20 Sep 2018 22:45:17 +0000 (+0200) Subject: that's already converted to sphinx X-Git-Tag: v3_21~57 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/695a5d0b3490296b3df020da81d1e586f5d2f645?hp=c5f0baaa7fb91f6584fcf35db0514774b7a26d71 that's already converted to sphinx --- diff --git a/doc/doxygen/install.doc b/doc/doxygen/install.doc deleted file mode 100644 index 8b474c7388..0000000000 --- a/doc/doxygen/install.doc +++ /dev/null @@ -1,404 +0,0 @@ -/*! @page install Installing Simgrid - -@tableofcontents - -SimGrid should work out of the box on Linux, Mac OSX, FreeBSD, and Windows (under windows, only the Java interfaces are -available at the moment). - -The easiest way to install SimGrid is to go for a @ref install_binary "binary package". Under Debian or Ubuntu, this is -very easy as SimGrid is directly integrated to the official repositories. For other Linux variants, you probably want -to go for a @ref install_src "source install". Please contact us if you want to contribute the build scripts for your -preferred distribution. If you just want to use @ref install_binary_java "Java", simply copy the jar file on your disk -and you're set. - -@section install_binary Pre-compiled Packages - -@subsection install_binary_linux Binaries for Linux - -Most of us use a Debian or Ubuntu system, so the packages for these -systems are well integrated and up-to-date. To get these packages, simply type: - -@verbatim -apt-get install simgrid -@endverbatim - -@subsection install_binary_java Stable Java Package - -For the SimGrid Java bindings, grab the jar file from the [download -page](https://gforge.inria.fr/frs/?group_id=12) and copy it in your -classpath (typically, your source code root directory). This -self-contained version even includes the SimGrid native components for -the following architectures: Linux (Amd64, x86, Arm), Mac OS X 64 -bits, Windows 64 bits, FreeBSD (64 bits). - -@subsection install_binary_java_builder Nightly built Java Package - -For Windows, head to [AppVeyor](https://ci.appveyor.com/project/simgrid/simgrid). -Click on the artefact link on the right, and grab your file. If the latest build failed, there will be no artefact. Then -you will need to first click on "History" on the top and search for the last successful build. - -For non-Windows systems (Linux, Mac or FreeBSD), head to [Jenkins](https://ci.inria.fr/simgrid/job/SimGrid). -In the build history, pick the last green (or at least yellow) build that is not blinking (i.e., not currently under -build). In the list, pick a system that is close to yours, and click on the ball in the Debug row. The build artefact -will appear on the top of the resulting page. - -@subsection install_binary_java_troubleshooting Binary Java Troubleshooting - - - **Your architecture is not supported by this jarfile**. \n - If your system is in the list of the supported architectures (see - @ref install_binary_java "above"), then this is probably a bug that - @ref contributing_bugs "you should report".\n - If your system is actually not supported, you should compile your - own jarfile @ref install_src "by compiling SimGrid" on your - machine. If you feel so, @ref community_contact "contact us" so that we add - your architecture to the list. - - - **Library not found: boost-context**.\n - You should obviously install the @c boost-context library on your - machine, for example with @c apt-get. - -@section install_src Source Installs - -@subsection install_src_deps Getting the Dependencies - -Recompiling an official archive is not much more complex. SimGrid only uses very standard tools: - - C compiler, C++ compiler, make and friends. SimGrid is rather - demanding on the compiler. We use the C++11 standard, and older - compilers tend to fail on us. It seems that g++ 5.0 or higher is - required nowadays (because of boost). - SimGrid compiles well with `clang` too. - - perl (but you may try to go without it) - - We use cmake to configure our compilation - ([download page](http://www.cmake.org/cmake/resources/software.html)). - You need cmake version 2.8.8 or higher. - `ccmake` provides a nicer graphical interface compared to `cmake`. - Press `t` in `ccmake` if you need to see absolutely all - configuration options (e.g., if your python installation is not standard). - - boost: - - Debian / Ubuntu: `apt-get install libboost-dev libboost-context-dev` - - Max OS X: with [fink](http://www.finkproject.org/): `fink install boost1.53.nopython`, - or with homebrew: `brew install boost` - - Java (if you want to build the Java bindings): - - Debian / Ubuntu: `apt-get install default-jdk libgcj17-dev` (any - version of libgcj will do it; you can use libgcj16-dev or libgcj18-dev - instead, depending on your version of Debian/Ubuntu) - - Mac OS X or Windows: Grab a [full JDK](http://www.oracle.com/technetwork/java/javase/downloads) - - Lua (if you want to build with lua enabled): Your version of Lua - must be 5.3. SimGrid won't work with Lua 5.2 nor with 5.1, and - probably not with Lua 5.4 either. - - Debian / Ubuntu: `apt-get install liblua5.3-dev lua5.3` - - Windows: choco install lua53 - - From the source: you need to patch the sources to build dynamic libraries - - [Download lua 5.3](http://www.lua.org/download.html). SimGrid - won't work with lua 5.2 as lua breaks the compatibility. - - Open the archive: `tar xvfz lua-5.3.*.tar.gz` - - Enter the directory: `cd lua-5.3*` - - Patch the sources: `patch -p1 < /path/to/simgrid/...../tools/lualib.patch` - - Build and install lua: `make linux && sudo make install` - -For platform-specific details, please see @ref install_cmake_mac, -@ref install_cmake_windows, @ref install_java and @ref install_src_32bits - -@subsection install_src_fetch Getting the Sources - -You can download the *@SimGridRelease.tar.gz* archive from the -[download page](https://gforge.inria.fr/frs/?group_id=12). -Then, recompiling the archive should be done in a few lines: - -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~{.sh} -tar xf @SimGridRelease.tar.gz -cd @SimGridRelease -cmake -DCMAKE_INSTALL_PREFIX=/opt/simgrid . -make -make install -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -If you want to stay on the bleeding edge, you should get the latest git version, and recompile it as you would do for -an official archive. Depending on the files you change in the source tree, some extra tools may be needed. - -@verbatim -git clone git://scm.gforge.inria.fr/simgrid/simgrid.git simgrid -@endverbatim - -@subsection install_src_config Build Configuration - -This section is about *compile-time options*, that are very different -from @ref options "run-time options". Compile-time options fall into -two categories. @ref install_cmake_list "SimGrid-specific options" -define which part of the framework to compile while -@ref install_cmake_howto "generic options" are provided by cmake -itself. - -@subsubsection install_cmake_howto Generic build-time options - -These options specify for example the path to various system elements -(Python path, compiler to use, etc). In most case, cmake automatically -discovers the right value for these ones, but you can set them -manually on need. Notable such variables include @c CC and @c CXX, -defining respectively the C and C++ compiler executables, @c CFLAGS -and @c CXXFLAGS respectively specifying extra options to pass to the C -and C++ compilers, or @c PYTHON_EXECUTABLE specifying the path to the -python executable. The best way to discover the exact name of the -option that you need to change is to press 't' in the ccmake graphical -interface, as all options are shown (and documented) in the advanced -mode. - -Once you know their name, there is several ways to change the value of -build-time options. You can naturally use the ccmake graphical -interface for that, or you can use environment variables, or you can -prefer the @c -D flag of @c cmake. - -For example, you can change the compilers with environment variables -by issuing these commands before launching cmake: - -@verbatim -export CC=gcc-5.1 -export CXX=g++-5.1 -@endverbatim - -The same can be done by passing @c -D parameters to cmake, as follows. -Note that the ending dot is mandatory (see @ref install_cmake_outsrc). - -@verbatim -cmake -DCC=clang -DCXX=clang++ . -@endverbatim - -@subsubsection install_cmake_list SimGrid compilation options - -Here is the list of SimGrid-specific @ref install_src_config -"build-time options". - - @li CMAKE_INSTALL_PREFIX (path): Where to install SimGrid (/opt/simgrid, /usr/local, or elsewhere). - - @li enable_compile_optimizations (ON/OFF) to request the compiler to produce efficient code. You want to - activate it, unless you plan to debug SimGrid itself. Indeed, efficient code may be appear mangled to debuggers. - - @li enable_compile_warnings (ON/OFF) to request the compiler to issue error messages whenever the source code - is not perfectly clean. If you are a SimGrid developer, you have to activate this option to enforce the code - quality. As a regular user, this option will bring you nothing. - - @li enable_debug (ON/OFF). Disable this option toto discard - all log messages of gravity debug or below at compile time (see - @ref XBT_log). The resulting code is faster than if you - discarding these messages at runtime. However, it obviously - becomes impossible to get any debug info from SimGrid if - something goes wrong. - - @li enable_documentation (ON/OFF) to generate the documentation pages. - - @li enable_java (ON/OFF) to enjoy the java bindings of SimGrid. - - @li enable_jedule (ON/OFF) to get SimDag producing execution traces that can then be visualized with the - Jedule external tool. - - @li enable_lua (ON/OFF) to enjoy the lua bindings to the - SimGrid internals (this require the liblua5.3-dev and lua-5.3 packages or equivalent). - - @li enable_lib_in_jar (ON/OFF) to make sure that the native - java bindings are bundled in the jar file. - - @li enable_lto (ON/OFF) to enable the Link Time Optimization - of the C compiler. This feature really speeds up the produced - code, but it is fragile with some versions of GCC. - - @li enable_maintainer_mode (ON/OFF) is only needed if you plan to modify very specific parts of SimGrid - (e.g., the XML parsers and other related elements). Moreover, this adds an extra dependency on flex and flexml. - - @li enable_mallocators (ON/OFF) has to be disabled when tracking memory issues within SimGrid, - or our internal memory caching mechanism will fool the debuggers. - - @li enable_model-checking (ON/OFF) This execution gear - is very usable now, but enabling this option at compile time - will **hinder simulation speed** even when the model-checker is - not activated at run time. - - @li enable_ns3 (ON/OFF) if you want to use ns-3. See section @ref pls_ns3. - - @li enable_smpi (ON/OFF) to run MPI code on top of SimGrid. - - @li enable_smpi_ISP_testsuite (ON/OFF) to add many extra - tests for the model-checker module. - - @li enable_smpi_MPICH3_testsuite (ON/OFF) to add many extra - tests for the MPI module. - -@subsubsection install_cmake_reset Reset the build configuration - -To empty the cmake cache (either when you add a new library or when -things go seriously wrong), simply delete your @c CMakeCache.txt. You -may also want to directly edit this file in some circumstances. - -@subsubsection install_cmake_outsrc Out of Tree Compilation - -By default, the files produced during the compilation are placed in -the source directory. It is however often better to put them all in a -separate directory: cleaning the tree becomes as easy as removing this -directory, and you can have several such directories to test several -parameter sets or architectures. - -For that, go to the directory where the files should be produced, and -invoke cmake (or ccmake) with the full path to the SimGrid source as -last argument. - -@verbatim -mkdir build -cd build -cmake [options] .. -make -@endverbatim - -@subsubsection install_cmake_mac Mac OS X Builds - -SimGrid compiles like a charm with clang (version 3.0 or higher) on Mac OS X: - -@verbatim -cmake -DCMAKE_C_COMPILER=/path/to/clang -DCMAKE_CXX_COMPILER=/path/to/clang++ . -make -@endverbatim - -With the XCode version of clang 4.1, you may get the following error message: -@verbatim -CMake Error: Parse error in cache file build_dir/CMakeCache.txt. Offending entry: /SDKs/MacOSX10.8.sdk -@endverbatim - -In that case, edit the CMakeCache.txt file directly, so that the -CMAKE_OSX_SYSROOT is similar to the following. Don't worry about the -warning that the "-pthread" argument is not used, if it appears. -@verbatim -CMAKE_OSX_SYSROOT:PATH=/Applications/XCode.app/Contents/Developer/Platforms/MacOSX.platform/Developer -@endverbatim - -In the El Capitan version of Max OS X, Apple decided that users don't -need no /usr/include directory anymore. If you are hit by this pure -madness, just run the following command to restore that classical -UNIX directory: `xcode-select -install` - -@subsubsection install_cmake_windows Windows Builds - -Building SimGrid on Windows may be something of an adventure: -We only manage to do so ourselves with MinGW-64, ActiveState -Perl and msys -git). Have a look at out configuration scripts in @c appveyor.yml, but -don't expect too much from us: we are really not fluent with Windows. -Actually your help is welcome. - -The drawback of MinGW-64 is that the produced DLL are not compatible -with MS Visual C. clang-cl -sounds promising to fix this. If you get something working, please -@ref community_contact "tell us". - -@subsubsection install_java Build the Java bindings - -Once you have the [full JDK](http://www.oracle.com/technetwork/java/javase/downloads) installed -(on Debian/Ubuntu, grab the package ```default-jdk``` for that), things should be as simple as: - -~~~~{.sh} -cmake -Denable_java=ON . -make -~~~~ - -After the compilation, the file ```simgrid.jar``` is produced in the -root directory. If you only want to build the jarfile and its -dependencies, type ```make simgrid-java_jar```. It will save you the -time of building every C examples and other things that you don't need -for Java. - -** **Error: jni could not be found**. Sometimes, the build system fails -to find the JNI headers. In this case, you need to first locate them as follows: - -~~~~{.sh} -$ locate jni.h -/usr/lib/jvm/java-7-openjdk-amd64/include/jni.h -/usr/lib/jvm/java-8-openjdk-amd64/include/jni.h -~~~~ - -Then, set the JAVA_INCLUDE_PATH environment variable to the right -path, and relaunch cmake. If you have several version of jni installed -(as above), use the right one (check the java version you use with -```javac -version```). - -~~~~{.sh} -export JAVA_INCLUDE_PATH=/usr/lib/jvm/java-8-openjdk-amd64/include/ -cmake -Denable_java=ON . -make -~~~~ - -Note that the filename ```jni.h``` was removed from the path. - -@subsubsection install_src_32bits 32 bits Builds on Multi-arch Linux - -On a multiarch x86_64 Linux, it should be possible to compile a 32 bit -version of SimGrid with something like: - -@verbatim -CFLAGS=-m32 \ -CXXFLAGS=-m32 \ -PKG_CONFIG_LIBDIR=/usr/lib/i386-linux-gnu/pkgconfig/ \ -cmake . \ --DCMAKE_SYSTEM_PROCESSOR=i386 \ --DCMAKE_Fortran_COMPILER=/some/path/to/i686-linux-gnu-gfortran \ --DGFORTRAN_EXE=/some/path/to/i686-linux-gnu-gfortran \ --DCMAKE_Fortran_FLAGS=-m32 -@endverbatim - -If needed, implement @c i686-linux-gnu-gfortran as a script: - -@verbatim -#!/usr/bin/env sh -exec gfortran -m32 "$@" -@endverbatim - -@subsection install_src_compil Existing Compilation Targets - -In most cases, compiling and installing SimGrid is enough: - -@verbatim -make -make install # try "sudo make install" if you don't have the permission to write -@endverbatim - -In addition, several compilation targets are provided in SimGrid. If -your system is well configured, the full list of targets is available -for completion when using the Tab key. Note that some of the existing -targets are not really for public consumption so don't worry if some -stuff doesn't work for you. - -@verbatim -make simgrid Build only the SimGrid library and not any example -make app-masterworker Build only this example (works for any example) -make clean Clean the results of a previous compilation -make install Install the project (doc/ bin/ lib/ include/) -make uninstall Uninstall the project (doc/ bin/ lib/ include/) -make dist Build a distribution archive (tgz) -make distcheck Check the dist (make + make dist + tests on the distribution) -make documentation Create SimGrid documentation -@endverbatim - -If you want to see what is really happening, try adding VERBOSE=1 to -your compilation requests: - -@verbatim -make VERBOSE=1 -@endverbatim - -@subsection install_src_test Testing your build - -Once everything is built, you may want to test the result. SimGrid -comes with an extensive set of regression tests (as described in the -@ref inside_tests "insider manual"). The tests are run with @c ctest, that comes with CMake. -We run them every commit and the results are on [our -Jenkins](https://ci.inria.fr/simgrid/). - -@verbatim -ctest # Launch all tests -ctest -R msg # Launch only the tests which name match the string "msg" -ctest -j4 # Launch all tests in parallel, at most 4 at the same time -ctest --verbose # Display all details on what's going on -ctest --output-on-failure # Only get verbose for the tests that fail - -ctest -R msg- -j5 --output-on-failure # You changed MSG and want to check that you didn't break anything, huh? - # That's fine, I do so all the time myself. -@endverbatim - -*/ diff --git a/doc/doxygen/install_yours.doc b/doc/doxygen/install_yours.doc deleted file mode 100644 index 1046f524c2..0000000000 --- a/doc/doxygen/install_yours.doc +++ /dev/null @@ -1,171 +0,0 @@ -/*! @page install_yours Setup your own project - -@tableofcontents - -It is not advised to modify the simgrid source code directly, as it -will make it difficult to upgrade to the next version of SimGrid. -Instead, you should create your own working directory somewhere on -your disk (say `/home/joe/MyFirstScheduler/`), and write your code in -there. - -Then, you should find a solution to get your code compiled and linked -to the SimGrid library as needed. This page helps you to do so with -several tools: -@ref install_yours_cmake "CMake" and -@ref install_yours_makefile "Makefile." -If you configure your project with a tool that is not listed here, -we'd be glad to hear how you've done that to extend this -documentation. - -@section install_yours_cmake Building your project with CMake - -Here is a `CMakeLists.txt` that you can use as a starting point for -your project. It builds two simulators from a given set of source files. - -@verbatim -project(MyFirstScheduler) - -set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11") - -set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${CMAKE_SOURCE_DIR}/cmake/Modules/") -find_package(SimGrid REQUIRED) -include_directories(${SimGrid_INCLUDE_DIR}) - -set(SIMULATOR_SOURCES main.c other.c util.c) -add_executable(my_simulator ${SIMULATOR_SOURCES}) -target_link_libraries(my_simulator ${SimGrid_LIBRARY}) - -set(OTHER_SOURCES blah.c bar.c foo.h) -add_executable(other_xp ${OTHER_SOURCES}) -target_link_libraries(other_xp ${SimGrid_LIBRARY}) -@endverbatim - -For that, you need FindSimGrid.cmake, -that is located at the root of the SimGrid tree. You can either copy -this file into the `cmake/Modules` directory of your project, or use -the version installed on the disk. Both solutions present advantages -and drawback: if you copy the file, you have to keep it in sync -manually but your project will produce relevant error messages when -trying to compile on a machine where SimGrid is not installed. Please -also refer to the file header for more information. - -@section install_yours_makefile Building your project with Makefile - -Here is a Makefile that will work if your project is composed of three -C files named @c util.h, @c util.c and @c mysimulator.c. You should -take it as a starting point, and adapt it to your code. There is a -plenty of documentation and tutorial on Makefile if the file's -comments are not enough for you. - -@verbatim -# The first rule of a Makefile is the default target. It will be built when make is called with no parameter -# Here, we want to build the binary 'mysimulator' -all: mysimulator - -# This second rule lists the dependencies of the mysimulator binary -# How this dependencies are linked is described in an implicit rule below -mysimulator: mysimulator.o util.o - -# These third give the dependencies of the each source file -mysimulator.o: mysimulator.c util.h # list every .h that you use -util.o: util.c util.h - -# Some configuration -SIMGRID_INSTALL_PATH = /opt/simgrid # Where you installed simgrid -CC = gcc # Your compiler -WARNING = -Wshadow -Wcast-align -Waggregate-return -Wmissing-prototypes \ - -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes \ - -Wmissing-declarations -Wmissing-noreturn -Wredundant-decls \ - -Wnested-externs -Wpointer-arith -Wwrite-strings -finline-functions - -# CFLAGS = -g -O0 $(WARNINGS) # Use this line to make debugging easier -CFLAGS = -g -O2 $(WARNINGS) # Use this line to get better performance - -# No change should be mandated past that line -############################################# -# The following are implicit rules, used by default to actually build -# the targets for which you listed the dependencies above. - -# The blanks before the $(CC) must be a Tab char, not spaces -%: %.o - $(CC) -L$(SIMGRID_INSTALL_PATH)/lib/ $(CFLAGS) $^ -lsimgrid -o $@ -%.o: %.c - $(CC) -I$(SIMGRID_INSTALL_PATH)/include $(CFLAGS) -c -o $@ $< - -clean: - rm -f *.o *~ -.PHONY: clean -@endverbatim - -@section install_yours_cppeclipsedevenv Develop in C++ with SimGrid with Eclipse - -If you wish to develop your plugin or modify SimGrid using Eclipse. You have to run cmake and import it as a Makefile project. - -Next you have to activate C++11 in your build settings, add -std=c++11 in the CDT GCC Built-in compiler settings. - -![Eclipse preference page.](eclipseScreenShot.png) - -@section install_yours_javaexample Building the Java examples in Eclipse - -If you want to build our Java examples in Eclipse, get the whole -source code and open the archive on your disk. In Eclipse, select -the menu "File / Import", and then in the wizard "General / Existing -Project into Workspace". On the Next page, select the directory -"examples/java" that you can find in the SimGrid source tree as a root -directory and finish the creation. - -The file \c simgrid.jar must be in the root directory of the SimGrid -tree. That's where it is built by default, but if you don't want to -compile it yourself, just grab that file from the SimGrid website and -copy it in here. - -Please note that once you better understand SimGrid, you should not -modify the examples directly but instead create your own project in -eclipse. This will make it easier to upgrade to another version of -SimGrid. - -@section install_yours_trouble Troubleshooting your project setup - -@subsection install_yours_trouble_libpath error while loading shared libraries: libsimgrid.so - -Sometimes, the following error message (or similar) will be produced: -@verbatim -./masterworker1: error while loading shared libraries: libsimgrid.so: -cannot open shared object file: No such file or directory -@endverbatim - -The same problem can make the execution of your programs spit pages -and pages of errors similar to the following. If there is only a few -undefined references, then you want to read the next section. -@verbatim -masterworker.c:209: undefined reference to `sg_version_check' -masterworker.c:209: undefined reference to `MSG_init_nocheck' -(and many other undefined references) -@endverbatim - -In both cases, it means that the system does not manage to find the -simgrid library when it tries to execute your programs. Under Linux, -specify where to search with the LD_LIBRARY_PATH variable. -Try running the following command before executing your code. If it -helps, you should add this line to your ~/.bashrc so that it gets -executed each time you log into your computer. - -@verbatim -export LD_LIBRARY_PATH=/opt/simgrid/lib -@endverbatim - -@subsection install_yours_trouble_oldlib Only a few undefined references - -Sometimes, the compilation only spits very few "undefined reference" -errors. A possible cause is that the system selected an old version of -the SimGrid library somewhere on your disk. - -Under Linux, you can find which version was used with the following -command that will display the full path to every used dynamic library. -Once you've found the obsolete copy of SimGrid, just erase it, and -recompile and relaunch your program. -@verbatim ldd yoursimulator -@endverbatim - - -*/ diff --git a/docs/source/intro_install.rst b/docs/source/intro_install.rst index 8ab57504d8..fd7b4c9cd9 100644 --- a/docs/source/intro_install.rst +++ b/docs/source/intro_install.rst @@ -6,8 +6,9 @@ Installing SimGrid ================== -SimGrid should work out of the box on Linux, Mac OSX, FreeBSD, and Windows (under windows, only the Java interfaces are -available at the moment). +SimGrid should work out of the box on Linux, Mac OSX, FreeBSD, and +Windows (under Windows, you need to install the Windows Subsystem +Linux to get more than the Java bindings). Pre-compiled Packages --------------------- diff --git a/docs/source/intro_yours.rst b/docs/source/intro_yours.rst index 727330b58e..f0ec5c6ddc 100644 --- a/docs/source/intro_yours.rst +++ b/docs/source/intro_yours.rst @@ -6,8 +6,8 @@ Start your Own Project It is not advised to modify the SimGrid source code directly, as it will make it difficult to upgrade to the next version of SimGrid. Instead, you should create your own working directory somewhere on -your disk (say `/home/joe/MyFirstSimulator/`), and write your code in -there. +your disk (say ``/home/joe/MyFirstSimulator/``), and write your code +in there. Cloning a Template Project for S4U ---------------------------------- diff --git a/tools/cmake/DefinePackages.cmake b/tools/cmake/DefinePackages.cmake index a4a59a5733..c393933509 100644 --- a/tools/cmake/DefinePackages.cmake +++ b/tools/cmake/DefinePackages.cmake @@ -885,8 +885,6 @@ set(DOC_SOURCES doc/doxygen/inside_doxygen.doc doc/doxygen/inside_extending.doc doc/doxygen/inside_release.doc - doc/doxygen/install.doc - doc/doxygen/install_yours.doc doc/doxygen/java.doc doc/doxygen/module-msg.doc doc/doxygen/module-sd.doc