You can append the version number to the toolset name, preceded by If you have multiple versions of a particular compiler installed, The Apache standard library in C++03 mode useī2 cxxflags=-library=stdcxx4 linkflags=-library=stdcxx4. Need can be injected with the b2 command line optionsĬxxflags=``and ``linkflags=. Standard library may not work well with Boost, unless youĪre building for C++11. That the libraries are built with the same options that yourĪppliction will use. Of options which effect binary compatibility: it is vital Note that the Oracle/Sun compiler has a large number Only very recent versions are known to work well withīoost. Includes support for Cygwin and MinGW compilers. Using this toolset may require configuring anotherĪpple's version of the GCC toolchain with support forĭarwin and MacOS X features such as frameworks. Only very recent versions are known to work well with Boost If you previously chose a toolset for the purposes ofīuilding b2, you should assume it won't work and insteadĬhoose newly from the table below. Still built for compatibility, but linking to it is no longer Boost.System is header-only since Boost 1.69.#define BOOST_ENABLE_NON_INTRUSIVE_EXCEPTION_PTR. Which requires a separately-compiled binary. Boost.Exception provides non-intrusive implementation ofĮxception_ptr for 32-bit _MSC_VER=1310 and _MSC_VER=1400.Mode, although separate compilation is recommended for serious Boost.Test can be used in “header-only” or “separately compiled”.Boost.Random has a binary component which is only needed if.Boost.Math has binary components for the TR1 and C99.Boost.Graph also has a binary component that is only needed if.Boost.Python (see the Boost.Python build documentationĪ few libraries have optional separately-compiled binaries:.The only Boost libraries that must be built separately are: Require no separately-compiled library binaries or special Of header files containing templates and inline functions, and Most Boost libraries are header-only: they consist entirely Libs / index.html if you're looking for the whole enchilada. hpp extension,Īnd live in the boost / subdirectory of the boost root, yourīoost #include directives will look like:ĭepending on your preference regarding the use of angle bracketĭon't be distracted by the doc / subdirectory it onlyĬontains a subset of the Boost documentation. Since all of Boost's header files have the. The boost / subdirectory in your #include path. To compile anything in Boost, you need a directory containing Sometimes referred to as $BOOST_ROOT in documentation and The path to the boost root directory (often /usr/local/ boost_1_79_0) is Don't expect to findĪnything you can use in these directories. Most libraries place private headers in a subdirectory calledĭetail /, or aux_ /. ForĮxample, Boost.Python's aggregate header is boost / python.hpp. #includes all of the library's other headers. Some libraries have an “aggregate header” in boost / that The Python library's def.hpp header in boost / python / def.hpp. Most libraries' public headers live in a subdirectory ofīoost /, named after the library. Some older libraries and most very small libraries place all The organization of Boost library headers isn't entirely uniform,īut most libraries follow a few patterns:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |