Set( doc_string =] ) rapids_export( INSTALL example EXPORT_SET example-targets NAMESPACE example :: DOCUMENTATION doc_string ) rapids_export( BUILD example EXPORT_SET example-targets NAMESPACE example :: DOCUMENTATION doc_string )īefore rapids-cmake, if a project wanted to generate a config module they would follow the example in If this isn’t the case for a CPM package you can instead use rapids_export_cpm(), and rapids_export_package() to specify the correct generated commandsĪnd forgo using _EXPORT_SET. Great build config.cmake support so it is best to have a fallback to cpm, while it is expected that all CMake packages have install rules. The theory behind this is that most packages currently don’t have With INSTALL_EXPORT_SET it will generate a find_dependency(.
When used with BUILD_EXPORT_SET, rapids_cpm_find() will generate a CPMFindPackage(. In that case this workflow avoids having to re-install a project each timeĪ change needs to be tested in a dependent project. Reason is that developers need to work on multiple dependent projects in a fast feedback loop. Why use a build directory config file at all? The most common Propagated through the usage requirements inside a project via $. While this pattern is rare, it occurs when projects have some dependencies that aren’t needed by consumers but are In this example what we are saying is that nlohmann_json is only needed by the build directory example-configĪnd not needed by the installed example-config. The rapids_cpm_find() combines the CPMFindPackage() command and dependency tracking, in a very similar way Rapids_cpm_find( nlohmann_json 3.9.1 BUILD_EXPORT_SET example-targets ) Making sure it is part of CMAKE_MODULE_PATH for consumers. If you already have an existing Find written, rapids_export_package() simplifies the process of installing the module and The rapids_find_generate_module() allows projects to automatically generate a Find and encode via the BUILD_EXPORT_SETĪnd INSTALL_EXPORT_SET parameters when the generated module should also be installed and added to CMAKE_MODULE_PATH so that consumers can use it. Rapids_find_generate_module() and rapids_export_package(). Rapids-cmake tries to help projects simplify this process with the commands In those cases projects will have a customįind that they need to use, and install for consumers. It is common for projects to have dependencies for which CMake doesn’t have a Find. The dependency when the underlying find_package command is successful.
The rapids_find_package() command also supports non-required finds correctly. This means that when rapids_export() is called the generated example-config.cmake file will include the callįind_dependency(Threads), removing the need for developers to maintain that dual source of truth. This example records that the Threads package is required by both the export set example-targets for both the install and build configuration. The rapids_find_package() combines the find_package command and dependency tracking. Rapids_find_package( Threads REQUIRED BUILD_EXPORT_SET example-targets INSTALL_EXPORT_SET example-targets )
0 kommentar(er)
