the declared test name should allow for easy subset filtering from ctest.
the tests binary file can take any name.Buildīoost:: is an alias to the default build artifact of package īoost:::: is an alias to a specific variant of package, if defined doc: contains the documentation targetsĪlias are used to map any target to a boost::library (where library is a known library or tool of boost).Some naming conventions are under development. īOOST_BUILD_DOC if set to ON, will build the documentation as part of the default build (defaults to OFF)īOOST_BUILD_TEST if set to ON, will build the test as part of the default build (defaults to OFF)īOOST_CREATE_VISIBLE_HEADER_ONLY if set to ON, will create a target for header only libraries that are For example, to have all files for header only libraries, directly in your IDE:Ĭmake -DBOOST_WITH_COMPONENT=test:build. Those are high level options passed to cmake. there is no need for copying header files around: the files stay in their original library/submodule/locationĪnd their location is propagated to dependent project.the dependencies between the libraries are explicit, which is a good thing.libraries having a boost-decl.cmake but not having a CMakeLists.txt are considered header only, and their dependencies are properly declared such that their dependencies are propagated properly to their dependant/child projects.Header only and automatically added to the super project, which lowers the development/porting libraries not having a boost-decl.cmake / CMakeLists.txt are considered as.This is mostly for creatingĪ convenient ALIAS target (for eg. only the two variables $Īre defined when a CMakeLists.txt is included.Written without the help of any external function or CMake package. each CMakeLists.txt makes no assumption of an existing super project: they are.Of doc and tests, the main build/CMakeLists.txt staying standalone) This should allow for easier redistribution (discarding the packaging the libraries, their documentation and the corresponding tests are decoupled, as.there is never direct inclusion from one CMakeLists.txt to another one.handles order of declaration of targets, inter dependencies.Those are meant to show some functional and real-case examples for porting to cmake: The current superproject CMakeLists.txt copies those CMakeLists.txt and boost-decl.cmake to their corresponding folders in the target libraries of Boost, prior to running anything else. add a CMakeLists.txt in each of the libs//, where the are taken from the.Take a look at the existing boost-decl.cmake in this repo for the expected format. a file in libs//build/boost-decl.cmake that indicates the components and their dependencies wrt.in this repository, create a folder libs/.The description of the package, components and their dependencies is made via a tiny text file, boost-decl.cmake the libraries and components are then included in the main project, in the topological order of their dependencies.those descriptions are read by the super project CMakeLists.txt.each package describes its components and, for each component, their dependencies.each library or tool of Boost is called a package.
0 kommentar(er)
