Boost_NAMESPACEĪlternate namespace used to build boost with e.g.
Names with and without this suffix will both be tried. Suffix for thread component library name, such as pthread or 圆4).ĭefault is auto-computed for the C++ compiler in use. Set to the architecture-specific library suffix (e.g. Default isĪuto-computed for the C++ compiler in use. Set to the compiler-specific library suffix (e.g. Set to ON to use libraries compiled with STLPort deprecated "native Boost_USE_STLPORT_DEPRECATED_NATIVE_IOSTREAMS Set to ON to use libraries compiled with STLPort ("p" tag). Set to ON to use libraries compiled with a debug Python build ("y" Set to ON or OFF to specify whether to use libraries linked to the Set to ON or OFF to specify whether to use libraries linked Set to ON to force the use of the static libraries. Set to OFF to use the non-multithreaded libraries ("mt" tag). Set to ON or OFF to specify whether to search and use the release Users or projects may tell this module which variant to find by Other Variables ¶īoost libraries come in many variants encoded in their file name. Values of the targets created by the first call. Than variables created by this module: multiple calls toįind_package(Boost) in the same directory or sub-directories withĭifferent options (e.g. It is important to note that the imported targets behave differently If usingīoost::thread, then Threads::Threads will also be added automatically. If system is not specified when using find_package() and ifīoost::system is not added to target_link_libraries(). Implicit dependencies such as Boost::filesystem requiringīoost::system will be automatically detected and satisfied, even Interface target to enable dynamic linking with MSVC Interface target to disable automatic linking with MSVC Linking during compilation (adds -DBOOST_LIB_DIAGNOSTIC). Interface target to enable diagnostic information about Boost's automatic
Target for specific component dependency (shared or static library) New in version 3.15: Alias for Boost::boost. Search results affected by the changes and searches again. Tree (excluding environment variables) this module discards previous When one changes settings used by previous searches in the same build Locations in Boost_LIBRARY_DEBUG and Boost_LIBRARY_RELEASE. Library directories in Boost_LIBRARY_DIR_DEBUG andīoost_LIBRARY_DIR_RELEASE and individual library Using the above hints (excluding BOOST_INCLUDEDIR andīoost_ADDITIONAL_VERSIONS), "lib" directories near Boost_INCLUDE_DIR,Īnd the library name configuration settings below. Then it searches for requested component libraries Hint variables (excluding BOOST_LIBRARYDIR) and saves the result inīoost_INCLUDE_DIR. This module first searches for the Boost header files using the above Not specified as CMake variables or cache entries. One may specify these as environment variables if they are Note that some hint names start in upper-caseīOOST. Should not read these entries directly but instead use the above Users may set these hints or results as CACHE entries.
#Cmake boost asio install
(Boost install locations may contain the version). List of Boost versions not known to this module. Set to ON to disable searching in locations not This module reads hints about search locations from variables: BOOST_ROOT, BOOSTROOT Here is an example for using the Boost::filesystem library: set(Boost_USE_STATIC_LIBS OFF)įind_package(Boost 1.New in version 3.3: Per-configuration variables Boost_LIBRARY_DIR_RELEASE and The other compiled libraries are available, and include dependencies as needed. The import targets are in the Boost:: namespace. Thisįunctionality was backported into CMake 3.9. In a recent merge request, CMake started assuming that the dependencies hold from the last version it knows about, and will use that (along with giving a warning). However, CMake has the dependency information baked into it for all known versions of Boost, so CMake must be newer than Boost for these to work. These targets handle dependencies for you as well, so they are a very nice way to add Boost libraries. In CMake 3.5, imported targets were added. There are a growing number of settings, but here are the three most common ones: set(Boost_USE_STATIC_LIBS OFF) Be sure to check the page for the minimum required version of CMake you are using and see what options you have.įirst, you can customize the behavior of the Boost libraries selected using a set of variables that you set before searching for Boost.
#Cmake boost asio full
See FindBoost for a full description this will just give a quick overview and provide a recipe. The Boost library is included in the find packages that CMake provides, but it has a couple of oddities in how it works.
0 kommentar(er)
