Identifying the library binary, among all the build variants,.There are two main challenges associated with linking: If (boost::regex_match(line, matches, pat)) It uses the Boost.Regex library, which has aīoost::regex pat( "^Subject: (Re: |Aw: )*(.*)" ) To demonstrate linking with a Boost binary library, we'll use theįollowing simple program that extracts the subject lines fromĮmails. You can append the version number to the toolset name, preceded by If you have multiple versions of a particular compiler installed, If you previously chose a toolset for the purposes ofīuilding bjam, you should assume it won't work and insteadĬhoose newly from the table below.
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_35_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: