![]() That is what CMake does with the folder cmake_install_folder/share/cmake-3.15/Modules/ This way they could be used by any project (not only Gaudi-based projects). In principle these find-module files could also be moved elsewhere (on CVMFS), In Gaudi's case, the two modules shouldīe moved so it is temporary. This way the =CMAKE_MODULE_PATHĬan contain one less entry. Should also contain the modules (used with include() inĬMakeLists.txt=s). Is the usual name given to the build treeĬontains all the find-module-files ( Find?.cmake) Unfortunately there can only be one directory that contains QMTest tests, thus.Dependencies of a target should only be direct dependencies of it.Test names should be PackageName.TestName.They do not have the same name because these variables will exists and have different values in the scope of the test. In CMake tests, SRC_DIR and BIN_DIR refer to the values of PROJECT_SOURCE_DIR and PROJECT_BINARY_DIR in Gaudi.Check SyntaxHighlightingPlugin for more information. SyntaxHighlightingPlugin: Language cmake is either undefined or unsupported. In files that can be used in any projects, it is a good idea to make sur that the CMake policy is recent enough.You may have a look at how CMake modules are documented cat $(dirname $(which cmake))/./share/cmake-3.15/Modules/FeatureSummary.cmake A web documentation is generated from this comment with sphinx. It is the format chosen by Kitware to document CMake itself. CMake files and functions should be documented in rst.If you do not know which conventions to follow when editing a file, look at another file that has the same purpose and follow the same style.Be careful when using ( CMAKE_SOURCE_DIR, PROJECT_SOURCE_DIR, CMAKE_CURRENT_SOURCE_DIR, CMAKE_PROJECT_NAME, PROJECT_NAME.) Always keep in mind that a project can be built standalone or as a part of a stack of projects.A CMake option or cached variable (may be set by the user at configure time) must be all capital.In this twiki page "we" will refer to the authors (package maintainers) and "you" to the reader (developer/user).when installing TBB, also install (or do not remove) the official TBBConfig.cmake * remove FindTBB.cmake from Gaudi if it happens.remove the message() in GaudiDependencies.cmake if it happens.ROOTConfig.cmake exposes the C++ standard used to compile ROOT * in ROOT_CXX_STANDARD for example, then remove the parsing of ROOT_CXX_FLAGS in CMakeLists.txt at the top-level of Gaudi * ROOTConfig.cmake displays a message when successfully found.remove all mark_as_advanced() for them in GaudiDependencies.cmake if it happens.apparently only 2.7 is available at the moment (Boost 1.70) * BoostConfig.cmake marks Boost_DIR and boost_ _DIR as advanced.BoostConfig.cmake handles Boost_USE_STATIC_LIBS correctly * remove set(BUILD_SHARED_LIBS ON) from GaudiDependencies.cmake if it happens * BoostConfig.cmake takes QUIET argument into account * BoostConfig.cmake has a way to set the version of the python component.with a script (see appendix) or by hand or anything else.Refactored all LHCb's Gaudi-based projects: LHCb, Lbcom, Rec, Phys, Analysis Brunel, Moore, DaVinci.Any project could use these toolchains and modules, not only Gaudi. move the folder cmake/toolchains/ and the modules CcacheOption.cmake and DeveloperBuildType.cmake somewhere on CVMFS.Current error of the script is "sed: can't read cmake/GaudiProjectConfig.cmake: No such file or directory" because the file has been removed. add a job in GitLab CI to check the formatting (with clang-format).remove no longer needed stuff in the ci-utils/ folder.so symlink that points to it (no hardcoded path, the one in the current directory is pointed) ![]() set_property(TARGET PROPERTY SOVERSION ) would tell CMake to set the soname of the.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |