When you extract the library from its zip file, you must preserve its internal directory structure (for example by using the -d option when extracting). If you didn't do that when extracting, then you'd better stop reading this, delete the files you just extracted, and try again!
This library should not need configuring before use; most popular compilers/standard libraries/platforms are already supported "as is". If you do experience configuration problems, or just want to test the configuration with your compiler, then the process is the same as for all of boost; see the configuration library documentation.
The library will encase all code inside namespace boost.
This is a header only library provided your compiler supports C++11 or later. Support for C++03 compilers is still present, but is now deprecated and may be removed without further notice!
The only people that still need to build the external libboost_regex library are those that are either:
Further, this library may now be used in "standalone" mode without the rest of the Boost C++ libraries, in order to do this you must either:
in this case if
<boost/config.hpp> is not present then the library will
automoatically enter standalone mode. Or:
If you are using this library with ICU, note that since it is now header only,
it will be up to you to link to the ICU libraries if you use
<boost/regex/icu.hpp> unless you are using the supplied CMake
The library comes with a very basic CMakeLists.txt that allows this library to be used from other CMake scripts.
CMakeLists.txt defines two targets:
Boost::regex This is the target to use for normal
header only builds.
Boost::regex_icu This is the target to use if
you are using
<boost/regex/icu.hpp> in your code, and wish to have the
ICU dependencies taken care of for you.
There is also one configuration option:
This is now the preferred method for building and installing legacy versions this library, please refer to the getting started guide for more information.
Boost.Regex is now capable of performing a configuration check to test whether ICU is already installed in your compiler's search paths. When you build you should see a message like this:
Performing configuration checks - has_icu builds : yes
Which means that ICU has been found, and support for it will be enabled in the library build.
If you don't want the regex library to use ICU then build with the "--disable-icu" command line option.
If instead you see:
Performing configuration checks - has_icu builds : no
Then ICU was not found and support for it will not be compiled into the library.
If you think that it should have been found, then you will need to take a look
at the contents of the file boost-root/bin.v2/config.log
for the actual error messages obtained when the build carried out the configuration
check. You will then need to fix these errors by ensuring your compiler gets
invoked with the correct options. The main options that you're likely to pass
Adds "/some/path" to the list of paths seached for include
files, normally equivalent to
Adds "/some/path" to the list of paths searched for external libraries, set this to the location of the ICU binaries if they're in a non-standard location.
Sets the C++ standard supported: XX should be either 03, 11, 14, 17 or 2a.
Passes "FLAGS" directly to the compiler, an option of last resort!
Passes "FLAGS" directly to the compiler on the link step, an option of last resort!
Configuration results are cached - if you try rebuilding with different compiler options then add an "-a" to the bjam command line to force all targets to be rebuilt.
ICU is a C++ library just like Boost is, as such your copy of ICU must have been built with the same C++ compiler (and compiler version) that you are using to build Boost. Boost.Regex will not work correctly unless you ensure that this is the case: it is up to you to ensure that the version of ICU you are using is binary compatible with the toolset you use to build Boost.
And finally, if you want to build/test with multiple compiler versions, all with different ICU builds, then the only way to achieve that currently is to modify your user-config.jam so that each toolset has the necessary compiler/linker options set so that ICU is found automatically by the configuration step (providing the ICU binaries use the standard names, all you have to add is the appropriate header-include and linker-search paths).
The Regex library is "just a bunch of source files": nothing special is required to build them.
You can either build the files under boost-path/libs/regex/src/*.cpp as a library, or add them directly to your project. This is particularly useful if you need to use specific compiler options not supported by the default Boost build.
There are two #defines you should be aware of: