The library should build and work with a reasonably compliant compiler. The library was successfully built and tested on the following platforms:
The following compilers/platforms are not supported and will likely fail to compile the library:
In order to compile the library under these compilers special preparations are needed. First, in case of MinGW or Cygwin make sure you have installed the latest GCC version. The library will most likely fail to compile with GCC 3.x.
Second, at some point the library will require a Message Compiler tool (
which is not available in MinGW, Cygwin and MSVC Express Edition. You have
three options to settle the problem. The recommended solution is to obtain
mc.exe. This tool is available in Windows
SDK, which can be downloaded from the Microsoft site freely (for example,
Also, this tool should be available in Visual Studio 2010 Express Edition.
During the compilation,
be accessible through one of the directories in your
Another way is to attempt to use the
distributed with MinGW and Cygwin, which is the analogue of the original
mc.exe. In order to do that you will have
to patch Boost.Build files (in particular, the
file) as described in this
ticket. After that you will be able to specify the
option to bjam to build the library.
Lastly, you can disable support for event log backend by defining the
macro when building the library. This will remove the need for the message
compiler. See this section
for more configuration options.
Cygwin support is rather preliminary. Some functionality is not available. In particular, the socket-based syslog backend is not supported, as it is based on Boost.ASIO, which doesn't compile on this platform. However, the native syslog support is still in place.
Furthermore, in order to compile the library the following parameters should
be explicitly specified in the bjam command line: