Temp comment out for Vault-Manager & API
Fixed bug to allow VS2013 to compile protobuf.
Merge branch 'next' of github.com:maidsafe/MaidSafe into next
Fixed minor CMake error.
Fix Windows Catch::Clara error
New Catch build fixes compilation errors
Fixed problem where CTest ignores failing builds on Unix.
Deleted Catch patch as fix is now on github
Small catch fix
Added patch step for Boost v1.55
Re-added Catch patch.
Added further Boost 1.55 patches to allow use of MSVC 2103.
Fixing #113 and #114 turned out to be quite the chore. The idea for using a custom
user-config.jam didn't work as any such file in $HOME overrides. I tried patching
the Boost source distro from cmake, which isn't the most flexible make language.
Ended up going with this very simple patch instead which gets the leafname off of
$CMAKE_C_COMPILER and supplies it as the toolset for boost.

Works fine with GCC, but for clang's not hard coded into Boost.Build you'll
find it ignores the unknown clang version and silently uses default clang e.g.
toolset=clang-9.9 will have Boost actually use clang++, not clang++-9.9.
Added AddressSanitizer, MemorySanitizer, ThreadSanitizer and UndefinedSanitizer build configs.
tsan didn't auto-detect with clang 3.4. Fixed.

Turned on UBSan for all builds by default. Use -DNO_UBSAN=TRUE to disable.
copied fix from account_transfer branch.
Added detection of -fstack-protector-strong in compiler, and if
available (GCC >= 4.9, clang >= 3.5) turn it on. Costs according to
the Chrome team who implemented it is about a 3% increase in stack
consumption. Apparently they're turning it on in the Linux kernel
by default, which is good enough for me.

Removed -fPIC and -pie from clang builds with tsan on. Had hoped
from the clang sources it would work around the warnings about
infinite stack, but it doesn't.
Merge branch 'next' of github.com:maidsafe/MaidSafe into add_tsan_build_support
minor fixes by Qi
Gave up on trying to persuade protoc to stop gaining -fsanitize=undefined,
and went with a nasty hack instead as I was wasting the afternoon on it.
Perhaps someone more familiar with the build config could look into doing
it right.