troubles compiling boost?

checkout your bin.v2\config.log file for more details...

compiling icu4c for use with boost

ICU - International Components for Unicodepypt/icu4c · GitHub - (Unofficial) mirror of ICU for C/C++ (ICU4C), updated hourly from SVN.
I had some trouble when trying to get regex icu going. As it talks about in Building and Installing the Library - 1.53.0, you'll want to define U_STATIC_IMPLEMENTATION=1 in env and supplying bjam/b2 with define=U_STATIC_IMPLEMENTATION=1 -sICU_PATH=%ICU_PATH%. When building a vs2010 build from within a "Visual Studio x64 Win64 Command Prompt (2010)" cmd.exe, I would have thought that would produce x64 by default when using devenv /Build. It doesn't produce x64, it produces x86 by default when using "devenv icu4c\source\allinone\allinone.sln /Build Debug". To produce a proper x64 build, add a |64 like: "devenv icu4c\source\allinone\allinone.sln /Build Release|x64". You can see if it works by running "icu4c\source\allinone\icucheck.bat x64 Release".

Also, I had some trouble linking my first app with icu and received an error that looked something like this (shortened a bit):

This let me know I wasn't linking something, but which library had Collator::createInstance defined? To find this out, I went into the icu4c\bin64 folder and ran the following to find the function signature.

which shows icuin51.dll defines our missing function. Turns out, the julp/FindICU.cmake cmake rule only adds the uc component by default. To get icuin51.lib in your ICU_LIBARIES variable, you need to pass in the i18n component in the find_package call.
find_package(ICU 4.4 COMPONENTS uc i18n REQUIRED)

Then since it ended up giving me shared dlls instead of static libs as I asked, you need to copy the dlls to the same folder as your binary, or put them in a system path. I chose to implement a post_build custom_command to do the copies, a copy_if_different for both debug and release dlls in the cwd of the binary.

boost::date_time

Keyboard History Utility has stopped working || doskey b2 and boost build issues

Using vs2012 x86 native cmdline prompt, I could not get the boost build to compile. It would continually show a crash dialog...hazah, more fun.#6653 (b2.exe crashes a loaded doskey.exe) – Boost C++ Libraries - closed, not sure it should be....agree, the issue is that doskey is crashing.#9488 (bjam.exe and doskey not getting along) – Boost C++ Libraries - Check your HKEY_CURRENT_USER\Software\Microsoft\Command Processor . I found cygwin places a .bashrc.bat in the user's profile. Deleting this key allowed the build to complete.
Then, since I have clink installed, it continually displays the clink startup text between each compile-c-c++ line. It would be nice to be able to silence the clink startup text...