Boost contains a lot of high quality cross platform C++ libraries. Some of the libraries in Boost use APIs that aren’t available in Windows Store and Phone applications. To help improve the experience Microsoft’s been working on enabling some of the Boost libraries.
We’ve made improvements to the Boost build system to support targeting the Windows Runtime for Windows Store and Phone. Also we’ve made changes to make the following Boost libraries work for Windows Store and Phone: system, chrono, date_time, smart_ptr, signals2, and thread. In addition to these Boost libraries, many others don’t use any banned APIs and work fine. This post shows how you can build and utilize portions of Boost in your Windows applications.
Here are the steps to download and setup the Boost sources for building. Boost has moved over to GitHub, now using Git submodules. More detailed information about modular Boost can be located here.
Clone Boost and setup for building. Please note this is a one-time operation that will take some time as it brings down all of the Boost sources. Throughout this post it is assumed you cloned into C:\boost.
Add the build tool, b2, to your Path environment variable. If you are using PowerShell something like following works.
A few of the changes for enabling the Windows Runtime haven’t migrated to into the ‘master’ branches or are still pending a merge. For these you will need to checkout the ‘develop’ branch or pull from my private branch containing the necessary changes.
Boost.Thread – optional only needed if going to use thread or a library that depends on it
With the latest Boost sources and your repositories setup you are now ready for building. If the Boost library/libraries you are interested in using are header file only, like Boost.Signals2 for example, then you don’t need to build and can entirely skip this step. Of the libraries we’ve enabled and verified, system, chrono, thread, and date_time are the only ones that require building.
To enable easily targeting the Windows Runtime a new feature called ‘windows-api’ has been added to the Boost build system. It accepts the values ‘store’, ‘phone’, and defaults to ‘desktop’ if not specified.
To build go to the build directory under the library you wish to use, for example to build Boost.Thread 32 bit debug for Windows 8.1 Store for static linking use the following command:
About toolsets and targeting, the toolset you specify determines which Windows version you are targeting:
The built-in Boost features variant, address-model, architecture, link can be used to produce debug/release, x86/x64/arm, and static/shared binaries. For example the following builds the release configuration, with static linking for the ARM architecture:
b2 toolset=msvc-12.0 variant=release link=static architecture=arm windows-api=store
More detailed information can be found in the Boost.Build documentation.
Once built, the binaries are output under the bin.v2 folder. The exact location is dependent on the options used and the name of the library built. For the command from before used to build Boost.Thread the binaries are located under:
Please note Visual Studio 2013 didn’t include vcvarsphone setup scripts so you won’t be able to target Phone 8.1 out of the box. With this blog post I’ve included phone setup scripts that can be used when targeting Windows Phone 8.1. To setup them up create the folders called WPSDK\WP81 under the VC Visual Studio installation directory, C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\, and copy the phone setup script files in.
With all the setup and building complete, using in an application is just the same as with any other C++ library. Setup the include path by adding C:\boost\. If the Boost library you’re using isn’t header file only then link to the lib and add the dll to the project (if not using static linking), making sure to set the ‘Content’ property to true so it is picked up for application deployment.
To help illustrate how to setup and use in an application, at the end of this post, I’ve included a simple sample Windows 8.1 Store application that utilizes the thread and signal2 libraries. The sample creates a simple signal with multiple slots using Boost threads in different ways. The sample assumes you cloned Boost into the C:\boost directory and built static linking for Boost.Thread, Boost.Date_Time, Boost.Chrono, and Boost.System, if this isn’t the case then you will need to update the include and library paths. Included with the sample also are the vcvars setup scripts for targeting Windows Phone 8.1.
For your next Windows Store and Phone application try using and let us know how it goes. Several individuals are already trying it out and Spotify is using several of the libraries in their Windows Phone application.
Not all of the libraries in Boost work yet in Windows Store and Phone, but the work we’ve done makes it easier to build and replace or update banned APIs. If one of the Boost libraries you want to use doesn’t work, depending on the banned API it might be easy to replace. We’ve added several new Boost.Predef, macros. By including <boost/predef/platform.h> you can use the BOOST_PLAT_WINDOWS_DESKTOP and BOOST_PLAT_WINDOWS_RUNTIME macros to test which platform is being targeted. For example if a call to WaitForSingleObject (only allowed in desktop) is used, you could replace it with WaitForSingleObjectEx by checking the macro for the Windows Runtime:
#include <boost/predef/platform.h>...#if BOOST_PLAT_WINDOWS_RUNTIME WaitForSingleObjectEx(handle, INFINITE, FALSE);#else WaitForSingleObject(handle, INFINITE);#endif
For more complex examples of API replacement you can take a look at the changes I made for Boost.Thread.
We are interested in hearing your feedback. What Boost libraries do you care about or what to use in your Windows Store and Phone applications?
That's a great news !
I will test the Boost.Thread and will let you know.
Great. Looking for way I can use Boost C++ Libraries (not the header-only) with Visual Studio Online.
Loved the post. Any chance we could get vcvarsxxx batch files to target WEC2013?
I have this lib:
It uses Windows Service API and LoadLibrary API family! Windows Store and Phone have these API too? Do you think that this lib can be ported to Store and Phone too?
It depeds of typeindex and filesystem too!
I would like to do this!
We are using boost in our cross platform code, and proper support for WinRT is most welcome. Boost ASIO on WinRT is missing UDP support (but patch is available on asio author's site and works fine). With added support for boost/system and boost/thread, it should be possible to use cpp-netlib, I will test this later. Thanks again!
Great, thanks a lot! Getting existing libraries like Boost to work was exactly the single major pain point I mentioned in the recent WinRT (or was it C++/CX?) survey.
@SimonRev: I'm not very familiar with Windows Embedded Compact so I'm not sure what the scripts would have to look like.
@Renato: I think you are going to have a tough time. I quickly glanced on the GitHub link you provided there are some banned APIs in use that will be easy to replace like CreateMutex and WaitForSingleObject. Depending on what you doing for LoadLibrary you might be able to use LoadPackagedLibrary instead, however the Windows Service APIs to my knowledge have no replacements. Filesystem also contains some banned APIs that would need replacing.
WinRT is getting really interesting...
@Stephen Gates -- I figured it was a long shot. But thank you. I don't currently do Modern App development, but I enjoyed the article, and if I do ever write a modern app, I would most certainly use Boost, so I appreciate the effort.
You may want to look at the cross-platform communication library called Casablanca casablanca.codeplex.com
I appreciate Microsoft supporting Boost. my notes on boost are here.
@Dave Horner: I'm unable to access the link you provided.
Can this be supported via nuget? It will be a great way to get new developers jump on to the boost bandwagon.
@Kris: Yes there is no reason why this couldn't be supported in a NuGet package. If you look on nuget.org someone already is producing a Boost NuGet package. For header file only libraries it would be no different, libraries with dlls would require building and adding the store/phone binaries to the NuGet package. Perhaps this could be done once all the changes are merged into Boost and go out in a release, should be in the next one.
My project use boost.asio, but it include "mswsock.h" which doesn't contain in wp8. Can it be patched like thread?