maidsafe-archive / maidsafe-common Goto Github PK

View Code? Open in Web Editor NEW

37.0 37.0 25.0 9.82 MB

Library of utility functions

Home Page: https://github.com/maidsafe/MaidSafe-Common/wiki

License: Other

C++ 97.72% C 0.40% CMake 1.87%

maidsafe-common's People

Contributors

Stargazers

Watchers

maidsafe-common's Issues

Doesn't compile on Ubuntu amd64

First, I built third_party_libs, it went good, then I tried to build Maidsafe-Common:

gamepad@GamePad-MU:~/MaidSafe-Common/maidsafe_common_lib/build/Linux/Release$ cmake ../../.. -DBOOST_LIB_DIR=/usr/lib
================================================================================

Building a package which is OK to release.
-- No proto files to be generated
-- Found python executable: style checking enabled.
-- Found library /usr/lib/x86_64-linux-gnu/librt.so
-- Found library /usr/lib/x86_64-linux-gnu/libc.so
-- Found library /usr/lib/x86_64-linux-gnu/libm.so
-- Found library /usr/lib/x86_64-linux-gnu/libdl.so
-- Found library /usr/lib/x86_64-linux-gnu/libpthread.so
================================================================================
CMake Error at /usr/share/cmake-2.8/Modules/FindBoost.cmake:621 (FILE):
  file Internal CMake error when trying to open file:
  /usr/local/include/boost/version.hpp for reading.
Call Stack (most recent call first):
  build/maidsafe_find_boost.cmake:114 (FIND_PACKAGE)
  CMakeLists.txt:120 (INCLUDE)


CMake Error at /usr/share/cmake-2.8/Modules/FindBoost.cmake:634 (MATH):
  math cannot parse the expression: " / 100000": syntax error, unexpected
  exp_DIVIDE, expecting exp_OPENPARENT or exp_NUMBER (2)
Call Stack (most recent call first):
  build/maidsafe_find_boost.cmake:114 (FIND_PACKAGE)
  CMakeLists.txt:120 (INCLUDE)


CMake Error at /usr/share/cmake-2.8/Modules/FindBoost.cmake:635 (MATH):
  math cannot parse the expression: " / 100 % 1000": syntax error, unexpected
  exp_DIVIDE, expecting exp_OPENPARENT or exp_NUMBER (2)
Call Stack (most recent call first):
  build/maidsafe_find_boost.cmake:114 (FIND_PACKAGE)
  CMakeLists.txt:120 (INCLUDE)


CMake Error at /usr/share/cmake-2.8/Modules/FindBoost.cmake:636 (MATH):
  math cannot parse the expression: " % 100": syntax error, unexpected
  exp_MOD, expecting exp_OPENPARENT or exp_NUMBER (2)
Call Stack (most recent call first):
  build/maidsafe_find_boost.cmake:114 (FIND_PACKAGE)
  CMakeLists.txt:120 (INCLUDE)


-- Boost version: ..
-- Found the following Boost libraries:
--   filesystem
--   system
--   thread
--   unit_test_framework
================================================================================

Tests included: All.   93 Google Tests.

    To include all tests,                cmake ../../.. -DMAIDSAFE_TEST_TYPE=ALL
    To include behavioural tests,        cmake ../../.. -DMAIDSAFE_TEST_TYPE=BEH
    To include functional tests,        cmake ../../.. -DMAIDSAFE_TEST_TYPE=FUNC
================================================================================

The libraries, headers, cmake modules and tools will be installed to:

    "/home/gamepad/MaidSafe-Common/installed"


To include this project in any other MaidSafe project, use:

    -DMAIDSAFE_COMMON_INSTALL_DIR="/home/gamepad/MaidSafe-Common/installed"


To force the rebuild of the third party libs, use one of:

 cmake ../../.. -DFORCE_THIRD_PARTY_BUILD=ALL
 cmake ../../.. -DFORCE_THIRD_PARTY_BUILD=GMOCK_GTEST
 cmake ../../.. -DFORCE_THIRD_PARTY_BUILD=CRYPTOPP
 cmake ../../.. -DFORCE_THIRD_PARTY_BUILD=PROTOBUF
 cmake ../../.. -DFORCE_THIRD_PARTY_BUILD=GLOG


To build and install this project now, run:

    cmake --build . --config Release --target install


================================================================================

-- Configuring incomplete, errors occurred!
gamepad@GamePad-MU:~/MaidSafe-Common/maidsafe_common_lib/build/Linux/Release$

Boost was installed from repositories.

Windows style checker outputs non-ASCII char on failure

The style checker script for windows outputs a non-printable character which is breaking the XML parsing on CDash.

Dashboard script fails to continue when encountering a versioning issue

Whenever common or another project dependency has a version increase and that dependent project has not been updated to handle the new version, the build will correctly throw an error like below:

CMake Error at C:/maidsafe/MaidSafe-Common/installed/share/maidsafe/cmake_modules/maidsafe_standard_setup.cmake:300 (MESSAGE):

This project needs MAIDSAFE_COMMON_VERSION 1000

Found MAIDSAFE_COMMON_VERSION 1001

This is fine, and expected, however the dashboard script then attempts to recover itself, before failing and stopping. The idea of having the script running continuous integration tests was that if it encountered such a problem, then it would just continue onto the next project.

This therefore, prevents subsequent projects from being built and test run against them.

CTest script fails to use consistent build mode for MSVC

When the CTest script is invoked with parameters "Nightly" or "NightlyDebug", the targets are built in Debug mode, but the exe run by CTest is the Release one.

UtilsTest.BEH_ENCRYPT_ReadWriteFile failed or timed out

Tested on Win7. See http://dash.maidsafe.net/testDetails.php?test=515073&build=5669

Cmake 2.8.5 hangs when building Common with Visual Studio 10 flag

When building common, or any other project, if you use the -G "Visual Studio 10" flag, the build hangs when it attempts to test the compiler.

If you downgrade cmake from 2.8.5 to 2.8.4 it will run successfully, without any problems.

Environment:

-Windows 7 32bit
-Cmake 2.8.5 (Later downgraded for workaround to 2.8.4)
-Visual Studio 10 Express Edition

Dashboard script not catching an error

This was originally submitted as maidsafe-archive/MaidSafe-Encrypt#1

Environment
Windows 7 (32bit), Visual Studio 2010, Cmake 2.8.4

Issue
When you attempt to install Maidsafe-Encrypt in either release or debug an error occurs (error can be found at the stacktrace section of this report).

The problem is the dashboard script (MaidSafe-Common\installed\share\maidsafe\cmake_modules/maidsafe_dashboard.cmake) doesn't catch this error, and submits results to the dashboard as if the project has correctly installed.

We should catch the error and report it correctly, as later project which depend upon Encrypt being installed, fail to build as they notice Encrypt isn't installed.

Stacktrace
c:\nightly\MaidSafe-Encrypt\build\Win_MSVC>cmake --build . --config Release --ta
rget install

Invalid Command Line. Unknown Switch : p:Configuration=Release.

Use:
vcexpress [solutionfile | projectfile | anyfile.ext] [switches]

The first argument for vcexpress is usually a solution file or project file.
You can also use any other file as the first argument if you want to have the
file open automatically in an editor. When you enter a project file, the IDE
looks for an .sln file with the same base name as the project file in the
parent directory for the project file. If no such .sln file exists, then the
IDE looks for a single .sln file that references the project. If no such single
.sln file exists, then the IDE creates an unsaved solution with a default .sln
file name that has the same base name as the project file.

Command line builds:
vcexpress solutionfile.sln /build [ solutionconfig ] [ /project projectnameorfil
e [ /projectconfig name ] ]
Available command line switches:

/Log Logs IDE activity to the specified file for troubleshooting.
/ResetSettings Restores the IDE's default settings, optionally resets to
the specified VSSettings file.
/SafeMode Launches the IDE in safe mode loading minimal windows.

Product-specific switches:

/debugexe Open the specified executable to be debugged. The
remainder of the command line is passed to this
executable as its arguments.
/useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables
instead of IDE paths for VC++ builds.

To attach the debugger from the command line, use:
VsJITDebugger.exe -p

c:\nightly\MaidSafe-Encrypt\build\Win_MSVC>

Why configure boost --without-mpi --without-python?

Any distribute of linux Fedora, Ubuntu, etc. has its own upstream packager to package of boost.

They would not disable mpi and python for boost.

When I use default boost library in my Ubuntu OS.
Here are the error logs while compile MaidSafe-Common.

-- Boost version: 1.48.0
-- Found the following Boost libraries:
-- filesystem
-- system
-- thread
-- date_time
-- unit_test_framework
CMake Error at build/Linux/Debug/boost_libs.cmake:93 (ADD_LIBRARY):
add_library cannot create imported target "boost_mpi_python-" because
another target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:147 (INCLUDE)

CMake Error at build/Linux/Debug/boost_libs.cmake:121 (ADD_LIBRARY):
add_library cannot create imported target "boost_mpi_python-" because
another target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:147 (INCLUDE)

CMake Error at build/Linux/Debug/boost_libs.cmake:161 (ADD_LIBRARY):
add_library cannot create imported target "boost_python-" because another
target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:147 (INCLUDE)

CMake Error at build/Linux/Debug/boost_libs.cmake:193 (ADD_LIBRARY):
add_library cannot create imported target "boost_python-" because another
target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:147 (INCLUDE)

CMake Error at build/Linux/Debug/boost_libs.cmake:197 (ADD_LIBRARY):
add_library cannot create imported target "boost_mpi_python-" because
another target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:147 (INCLUDE)

CMake Error at build/Linux/Debug/boost_libs.cmake:209 (ADD_LIBRARY):
add_library cannot create imported target "boost_python-" because another
target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:147 (INCLUDE)

-- Coverage OFF. To enable, do: export COVERAGE=ON and re-run CMake

How to use Kademlia demo?

I entered the below command .

./KademliaDemo-d --bs_ip 192.168.12.11 --bs_port 1000 --bs_id 00a67c0b34a311cff7711346d41cec8e864d2c2859570951e8f1812c60a95f24b4aede354535a38f6d9e5c0039d5f44ac8192a4b409e20cbac979ef5847d1181 -p 10000 --noconsole

and I was prompted :
E0625 16:03:48.822669 27427 message_handler.cc:dht:267] MakeSerialisedWrapperMessage - type 1005 - No public key for receiver provided.
Node failed to join the network with return code <-1>.

How to fix it?and how can I set up a test network environment with 1,000 nodes inside by using kademlia demo?

Fix to allow OSX builds.

The OpenMP library is not supported for express editions of Visual Studio

We are now making use of the OpenMP library in Common. Currently Microsoft doesn't provide support in their express editions of Visual Studio for this library.

This presents several issues for us:

Express editions will fail to build common, as in encrypt.cc we include omp.h (line 29 "#include <omp.h>". Obviously the express editions will fail to find omp.h, and will fail to build. We will need to cater for this to allow the projects to still build.
Successful builds using express editions of the code will not make use of the OpenMP library. This therefore will not enable threading in the self encryption process. If an alternative solution is not available for such environments we'll need to clearly state this limitation, as performance implications will obviously be apparent.
Our Windows CI servers current run express editions, which will lead to builds without threading. As such any tests around this will be worthless. If an alternative to OpenMP exist here it might be more suitable. Either way if we continue to use OpenMP with a workaround for express editions for threading, then we will need to invest in infrastructure to cover this scenario for continuous integration feedback.

Threadpool test failed

Note: Google Test filter = ThreadpoolTest.BEH_BASE_SingleTask
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from ThreadpoolTest
[ RUN ] ThreadpoolTest.BEH_BASE_SingleTask
/home/prakash/workspace/MAIDSAFE_TEST_ROOT/MaidSafe-Common/maidsafe_common_lib/src/maidsafe/common/tests/test_threadpool.cc:143: Failure
Value of: work_.completed_tasks().size()
Actual: 2
Expected: 3U
Which is: 3
[ FAILED ] ThreadpoolTest.BEH_BASE_SingleTask (367 ms)
[----------] 1 test from ThreadpoolTest (367 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (367 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] ThreadpoolTest.BEH_BASE_SingleTask

maidsafe_find_boost.cmake breaks boost auto-detection

In the file maidsafe_common_lib/build/maidsafe_find_boost.cmake:

Some default options for the boost include path set the wrong variables and result in a complete breakage of the auto-detection and various parsing functions in Cmakes shipped "FindBoost.cmake" file if boost is not at the assumed location (which is, strangely enough /usr/local/include instead of /usr/include)

This patch fixes the problem:

https://gist.github.com/a4c52f036fc61c24abac

(I spend > 1.5h hours on this problem :( )

--Marenz

Dashboard script fails to update common when it's version number increments

Dashboard script fails to update common when it's version number increments, which causes all later project who are expecting the new version of common to fail.

You can manually update common, but the dashboard script should really do this, since a workaround defeats the purpose of CI.

TESTcommon-d linker error regarding boost

Building and installing MadeSafe-Common on linux results in a linker error in boost (see https://gist.github.com/1064630 )

The problem happens when MaidSafe-Common is compiled with -std=c++0x and boost isn't. As it happens, the package of my distribution is not build with -std=c++0x

Boost emulates a certain c++0x features using structs and namespaces (see file boost/detail/scoped_enum_emulation.hpp ) but this emulation causes changes in the symbol names, thus the linker error when not using the emulation. A solution to this problem is, to turn off that c++0x feature and enable the emulation, right before including the header files in question.

The linked patch does exactly that: https://gist.github.com/1064737

The question is though, when to enable it and when not. The best thing is probably to add it as a cmake option or add a cmake script that tests whether the given boost installation was compiled with -std=c++0x or not

--Marenz

Release Build Error

During a make of the release build (Ubuntu) from the main Super Project I encountered the following errors:

[ 44%] Built target maidsafe_lifestuff_manager_core_dummy
/home/maidsafe/maidsafe/MaidSafe/src/common/src/maidsafe/common/utils.cc: In      function ‘std::string maidsafe::Base64Encode(const string&)’:
/home/maidsafe/maidsafe/MaidSafe/src/common/src/maidsafe/common/utils.cc:277:57: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]
/home/maidsafe/maidsafe/MaidSafe/src/common/src/maidsafe/common/utils.cc:277:57: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]
cc1plus: all warnings being treated as errors
make[2]: ***    [src/common/CMakeFiles/maidsafe_common.dir/src/maidsafe/common/utils.cc.o]    Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [src/common/CMakeFiles/maidsafe_common.dir/all] Error 2
make: *** [all] Error 2

The Debug build which was built before the Release one, worked as expected.

Fix CMakeLists.txt in third_party_libs for Linux and OSX

Glog's headers for Windows are installed when building for Linux and OSX.

Dashboard script fails when a new 3rd party library is introduced

The recent introduction of BreakPad to common as a 3rd party library, saw the Continuous Integration builds of common fail in all environments. This is due to the dashboard script not being able to detect when a new 3rd party library has been introduced. As this library will not be built, calls to this will cause the build to fail, which then requires a manual rebuild of the 3rd party library.

Preferably we would avoid this scenario and detect an addition, possibly by comparing a previous and current library list, and upon detection of changes, trigger a rebuild of all 3rd party libs (which is probably easier than trying to detect the distinct library that has changed, which would then also present an unhandled scenario of a library removal).

Can't build TESTCommon, on Cent OS 64bit

Steps

Pull maidsafe-common using git
Build common "cmake ../.." from MaidSafe-Common/maidsafe_common_lib/build/Linux
Build and install "cmake --build . --target install" from MaidSafe-Common/maidsafe_common_lib/build/Linux
Build release "cmake ../../.." from MaidSafe-Common/maidsafe_common_lib/build/Linux/Release

It will fail with build TESTCommon

/usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../include/c++/4.4.4/bits/basic_string.h:2498: note: std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char, _Traits = std::char_traits, _Alloc = std::allocator]
make[2]: *** [CMakeFiles/TESTcommon.dir/src/maidsafe/common/tests/detect_platform_test.cc.o] Error 1
make[1]: *** [CMakeFiles/TESTcommon.dir/all] Error 2

make: *** [all] Error 2

This prevents you from being able to execute most of the tests

ThreadsafeChunkStoreTest.BEH_TSCS_Misc

Intermittent failure on linux see following
http://dash.maidsafe.net/testSummary.php?project=7&name=ThreadsafeChunkStoreTest.BEH_TSCS_Misc&date=2011-05-20

crypto RNG on Linux

Depending on the frequency of the required operation, AsymEncrypt and AsymSign (and presumably other operations that require the Linux RNG) might return an empty string because the exception generated internally by crypto++. I would suggest either introducing an error code to make it evident that the operation has failed or an internal cycle to make sure a non-empty string is returned.

ThreadPool::Start method should not be public

FileChunkStoreTest.BEH_FCS_Store failed or timed out

Tested on Win7. See http://dash.maidsafe.net/testDetails.php?test=515116&build=5671

Common Does not Build for Win64 using MSVC Express

MaidSafe Common built on a x64 machine with Boost compiled for x64

cmake ../.. -G "Visual Studio 10 Win64"

and

cmake --build . --config Debug --target install

Gives the Following Output:

Build started 07/10/2011 15:02:22.
Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\install.vcxproj" on node 1 (default targets).
Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\install.vcxproj" (1) is building "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ALL_BUILD
.vcxproj" (2) on node 1 (default targets).
Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ALL_BUILD.vcxproj" (2) is building "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTboo
st.vcxproj" (3) on node 1 (default targets).
Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTboost.vcxproj" (3) is building "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ZERO_CH
ECK.vcxproj" (4) on node 1 (default targets).
PrepareForBuild:
Creating directory "x64\Debug\ZERO_CHECK".
InitializeBuildStatus:
Creating "x64\Debug\ZERO_CHECK\ZERO_CHECK.unsuccessfulbuild" because "AlwaysCreate" was specified.
CustomBuild:
Checking Build System
CMake does not need to re-run because C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib/build/Win_MSVC/CMakeFiles/generate.stamp is up-to-date.
FinalizeBuildStatus:
Deleting file "x64\Debug\ZERO_CHECK\ZERO_CHECK.unsuccessfulbuild".
Touching "x64\Debug\ZERO_CHECK\ZERO_CHECK.lastbuildstate".
Done Building Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ZERO_CHECK.vcxproj" (default targets).
Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTboost.vcxproj" (3) is building "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\maidsaf
e_common_static.vcxproj" (5) on node 1 (default targets).
PrepareForBuild:
Creating directory "maidsafe_common_static.dir\Debug".
Creating directory "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\Debug".
InitializeBuildStatus:
Creating "maidsafe_common_static.dir\Debug\maidsafe_common_static.unsuccessfulbuild" because "AlwaysCreate" was specified.
CustomBuild:
Building Custom Rule C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib/CMakeLists.txt
CMake does not need to re-run because C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\CMakeFiles\generate.stamp is up-to-date.
ClCompile:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\CL.exe /c /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_commo
n_lib/src" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/installed/include/maidsafe" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/installed/include/breakpad" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Comm
on/installed/include" /IC:/Users/maidsafe/Downloads/Test/boost_1_47_0 /Zi /nologo /W4 /WX /Od /Ot /Oy /D _DEBUG /D DEBUG /D CMAKE_MAIDSAFE_COMMON_VERSION=1003 /D STATICLIB /D BOOST_FILESYSTEM_NO_DEPRECATED /D BOOST_FILES
YSTEM_VERSION=3 /D WIN32 /D _WIN32 /D WINDOWS /D WIN32 /D MAIDSAFE_WIN32 /D MSVC /D WIN32_LEAN_AND_MEAN /D _WIN32_WINNT=0x501 /D _CONSOLE /D _UNICODE /D UNICODE /D _BIND_TO_CURRENT_VCLIBS_VERSION=1 /D NOMINMA
X /D GOOGLE_GLOG_DLL_DECL= /D BOOST_ALL_NO_LIB /D "CMAKE_INTDIR="Debug"" /D _UNICODE /D UNICODE /Gm- /EHsc /MTd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Fo"maidsafe_common_static.dir\Debug" /Fd"C:/Users/maidsafe/Dow
nloads/Test/MaidSafe-Common/maidsafe_common_lib/build/Win_MSVC/Debug/maidsafe_common-d-0_10_03.pdb" /Gd /TP /wd4996 /errorReport:queue ....\src\maidsafe\common\breakpad.cc ....\src\maidsafe\common\buffered_chunk_store.
cc ....\src\maidsafe\common\crypto.cc ....\src\maidsafe\common\file_chunk_store.cc ....\src\maidsafe\common\log.cc ....\src\maidsafe\common\memory_chunk_store.cc ....\src\maidsafe\common\securifier.cc ....\src\maid
safe\common\threadsafe_chunk_store.cc ....\src\maidsafe\common\utils.cc /c
breakpad.cc
buffered_chunk_store.cc
crypto.cc
file_chunk_store.cc
log.cc
memory_chunk_store.cc
securifier.cc
threadsafe_chunk_store.cc
utils.cc
Generating Code...
Lib:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\Lib.exe /OUT:"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\Debug\maidsafe_common-d-0_10_03.lib" /NOLOGO maidsa
fe_common_static.dir\Debug\breakpad.obj
maidsafe_common_static.dir\Debug\buffered_chunk_store.obj
maidsafe_common_static.dir\Debug\crypto.obj
maidsafe_common_static.dir\Debug\file_chunk_store.obj
maidsafe_common_static.dir\Debug\log.obj
maidsafe_common_static.dir\Debug\memory_chunk_store.obj
maidsafe_common_static.dir\Debug\securifier.obj
maidsafe_common_static.dir\Debug\threadsafe_chunk_store.obj
maidsafe_common_static.dir\Debug\utils.obj
maidsafe_common_static.vcxproj -> C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\Debug\maidsafe_common-d-0_10_03.lib
FinalizeBuildStatus:
Deleting file "maidsafe_common_static.dir\Debug\maidsafe_common_static.unsuccessfulbuild".
Touching "maidsafe_common_static.dir\Debug\maidsafe_common_static.lastbuildstate".
Done Building Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\maidsafe_common_static.vcxproj" (default targets).
PrepareForBuild:
Creating directory "TESTboost.dir\Debug".
InitializeBuildStatus:
Creating "TESTboost.dir\Debug\TESTboost.unsuccessfulbuild" because "AlwaysCreate" was specified.
CustomBuild:
Building Custom Rule C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib/CMakeLists.txt
CMake does not need to re-run because C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\CMakeFiles\generate.stamp is up-to-date.
ClCompile:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\CL.exe /c /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_commo
n_lib/src" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/installed/include/maidsafe" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/installed/include/breakpad" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Comm
on/installed/include" /IC:/Users/maidsafe/Downloads/Test/boost_1_47_0 /Zi /nologo /W4 /WX /Od /Ot /Oy /D _DEBUG /D DEBUG /D CMAKE_MAIDSAFE_COMMON_VERSION=1003 /D STATICLIB /D BOOST_FILESYSTEM_NO_DEPRECATED /D BOOST_FILES
YSTEM_VERSION=3 /D WIN32 /D _WIN32 /D WINDOWS /D WIN32 /D MAIDSAFE_WIN32 /D MSVC /D WIN32_LEAN_AND_MEAN /D _WIN32_WINNT=0x501 /D _CONSOLE /D _UNICODE /D UNICODE /D _BIND_TO_CURRENT_VCLIBS_VERSION=1 /D NOMINMA
X /D GOOGLE_GLOG_DLL_DECL= /D BOOST_ALL_NO_LIB /D "CMAKE_INTDIR="Debug"" /D _UNICODE /D UNICODE /Gm- /EHsc /MTd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Fo"TESTboost.dir\Debug" /Fd"C:/Users/maidsafe/Downloads/Test/M
aidSafe-Common/maidsafe_common_lib/build/Win_MSVC/Debug/TESTboost.pdb" /Gd /TP /wd4996 /errorReport:queue ....\src\maidsafe\common\tests\main.cc ....\src\maidsafe\common\tests\boost\bind_test.cc ....\src\maidsafe\comm
on\tests\boost\format_test.cc ....\src\maidsafe\common\tests\boost\smart_ptr_test.cc /c
main.cc
bind_test.cc
format_test.cc
smart_ptr_test.cc
Generating Code...
ManifestResourceCompile:
C:\Program Files\Microsoft SDKs\Windows\v7.1\bin\rc.exe /nologo /fo"TESTboost.dir\Debug\TESTboost.exe.embed.manifest.res" TESTboost.dir\Debug\TESTboost_manifest.rc
Link:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\link.exe /ERRORREPORT:QUEUE /OUT:"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\Debug\TESTboost.exe" /VERSION:"
0.0" /INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib "Debug\maidsafe_common-d-0_10_03.lib" "C:\Users\maidsafe\Downloads\Test\MaidS
afe-Common\installed\lib\Debug\libglog_static.lib" "C:\Users\maidsafe\Downloads\Test\boost_1_47_0\stage\lib\libboost_unit_test_framework-vc100-mt-sgd-1_47.lib" "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\installed
lib\Debug\gtest.lib" ws2_32.lib odbc32.lib odbccp32.lib WSock32.lib IPHlpApi.lib "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\installed\lib\Debug\cryptopp_d.lib" "C:\Users\maidsafe\Downloads\Test\boost_1_47_0\stage
lib\libboost_filesystem-vc100-mt-sgd-1_47.lib" "C:\Users\maidsafe\Downloads\Test\boost_1_47_0\stage\lib\libboost_system-vc100-mt-sgd-1_47.lib" "C:\Users\maidsafe\Downloads\Test\boost_1_47_0\stage\lib\libboost_thread-vc10
0-mt-sgd-1_47.lib" /MANIFEST /ManifestFile:"TESTboost.dir\Debug\TESTboost.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG /PDB:"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsaf
e_common_lib\build\Win_MSVC\Debug\TESTboost.pdb" /SUBSYSTEM:CONSOLE /STACK:"10000000" /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib/build/Win_MSVC/Debug/TES
Tboost.lib" /MACHINE:X64 TESTboost.dir\Debug\TESTboost.exe.embed.manifest.res
TESTboost.dir\Debug\main.obj
TESTboost.dir\Debug\bind_test.obj
TESTboost.dir\Debug\format_test.obj
TESTboost.dir\Debug\smart_ptr_test.obj /machine:x64 /debug
libglog_static.lib(vlog_is_on.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64' [C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTboost.
vcxproj]
Done Building Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTboost.vcxproj" (default targets) -- FAILED.
Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ALL_BUILD.vcxproj" (2) is building "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTcom
mon.vcxproj" (6) on node 1 (default targets).
PrepareForBuild:
Creating directory "TESTcommon.dir\Debug".
InitializeBuildStatus:
Creating "TESTcommon.dir\Debug\TESTcommon.unsuccessfulbuild" because "AlwaysCreate" was specified.
CustomBuild:
Building Custom Rule C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib/CMakeLists.txt
CMake does not need to re-run because C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\CMakeFiles\generate.stamp is up-to-date.
ClCompile:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\CL.exe /c /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_commo
n_lib/src" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/installed/include/maidsafe" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/installed/include/breakpad" /I"C:/Users/maidsafe/Downloads/Test/MaidSafe-Comm
on/installed/include" /IC:/Users/maidsafe/Downloads/Test/boost_1_47_0 /Zi /nologo /W4 /WX /Od /Ot /Oy /D _DEBUG /D DEBUG /D CMAKE_MAIDSAFE_COMMON_VERSION=1003 /D STATICLIB /D BOOST_FILESYSTEM_NO_DEPRECATED /D BOOST_FILES
YSTEM_VERSION=3 /D WIN32 /D _WIN32 /D WINDOWS /D WIN32 /D MAIDSAFE_WIN32 /D MSVC /D WIN32_LEAN_AND_MEAN /D _WIN32_WINNT=0x501 /D _CONSOLE /D _UNICODE /D UNICODE /D _BIND_TO_CURRENT_VCLIBS_VERSION=1 /D NOMINMA
X /D GOOGLE_GLOG_DLL_DECL= /D BOOST_ALL_NO_LIB /D "CMAKE_INTDIR="Debug"" /D _UNICODE /D UNICODE /Gm- /EHsc /MTd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Fo"TESTcommon.dir\Debug" /Fd"C:/Users/maidsafe/Downloads/Test/
MaidSafe-Common/maidsafe_common_lib/build/Win_MSVC/Debug/TESTcommon.pdb" /Gd /TP /wd4996 /errorReport:queue ....\src\maidsafe\common\tests\main.cc ....\src\maidsafe\common\tests\crypto_test.cc ....\src\maidsafe\common
\tests\detect_platform_test.cc ....\src\maidsafe\common\tests\file_chunk_store_test.cc ....\src\maidsafe\common\tests\memory_chunk_store_test.cc ....\src\maidsafe\common\tests\securifier_test.cc ....\src\maidsafe\com
mon\tests\threadsafe_chunk_store_test.cc ....\src\maidsafe\common\tests\utils_test.cc /c
main.cc
crypto_test.cc
detect_platform_test.cc
file_chunk_store_test.cc
memory_chunk_store_test.cc
securifier_test.cc
threadsafe_chunk_store_test.cc
utils_test.cc
Generating Code...
ManifestResourceCompile:
C:\Program Files\Microsoft SDKs\Windows\v7.1\bin\rc.exe /nologo /fo"TESTcommon.dir\Debug\TESTcommon.exe.embed.manifest.res" TESTcommon.dir\Debug\TESTcommon_manifest.rc
Link:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\link.exe /ERRORREPORT:QUEUE /OUT:"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\Debug\TESTcommon.exe" /VERSION:
"0.0" /INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib "Debug\maidsafe_common-d-0_10_03.lib" "C:\Users\maidsafe\Downloads\Test\Maid
Safe-Common\installed\lib\Debug\gtest.lib" "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\installed\lib\Debug\cryptopp_d.lib" "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\installed\lib\Debug\libglog_static.lib" "
C:\Users\maidsafe\Downloads\Test\boost_1_47_0\stage\lib\libboost_filesystem-vc100-mt-sgd-1_47.lib" "C:\Users\maidsafe\Downloads\Test\boost_1_47_0\stage\lib\libboost_system-vc100-mt-sgd-1_47.lib" "C:\Users\maidsafe\Downlo
ads\Test\boost_1_47_0\stage\lib\libboost_thread-vc100-mt-sgd-1_47.lib" ws2_32.lib odbc32.lib odbccp32.lib WSock32.lib IPHlpApi.lib /MANIFEST /ManifestFile:"TESTcommon.dir\Debug\TESTcommon.exe.intermediate.manifest" /MANI
FESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG /PDB:"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\Debug\TESTcommon.pdb" /SUBSYSTEM:CONSOLE /STACK:"10000000" /TLBID:1 /DYNAMICBA
SE /NXCOMPAT /IMPLIB:"C:/Users/maidsafe/Downloads/Test/MaidSafe-Common/maidsafe_common_lib/build/Win_MSVC/Debug/TESTcommon.lib" /MACHINE:X64 TESTcommon.dir\Debug\TESTcommon.exe.embed.manifest.res
TESTcommon.dir\Debug\main.obj
TESTcommon.dir\Debug\crypto_test.obj
TESTcommon.dir\Debug\detect_platform_test.obj
TESTcommon.dir\Debug\file_chunk_store_test.obj
TESTcommon.dir\Debug\memory_chunk_store_test.obj
TESTcommon.dir\Debug\securifier_test.obj
TESTcommon.dir\Debug\threadsafe_chunk_store_test.obj
TESTcommon.dir\Debug\utils_test.obj /machine:x64 /debug
libglog_static.lib(vlog_is_on.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64' [C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTcommon
.vcxproj]
Done Building Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTcommon.vcxproj" (default targets) -- FAILED.
Done Building Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ALL_BUILD.vcxproj" (default targets) -- FAILED.
Done Building Project "C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\install.vcxproj" (default targets) -- FAILED.

Build FAILED.

"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\install.vcxproj" (default target) (1) ->
"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ALL_BUILD.vcxproj" (default target) (2) ->
"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTboost.vcxproj" (default target) (3) ->
(Link target) ->
libglog_static.lib(vlog_is_on.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64' [C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTboos
t.vcxproj]

"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\install.vcxproj" (default target) (1) ->
"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\ALL_BUILD.vcxproj" (default target) (2) ->
"C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTcommon.vcxproj" (default target) (6) ->
libglog_static.lib(vlog_is_on.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64' [C:\Users\maidsafe\Downloads\Test\MaidSafe-Common\maidsafe_common_lib\build\Win_MSVC\TESTcomm
on.vcxproj]

0 Warning(s)
2 Error(s)

Time Elapsed 00:00:58.58

third_party_libs

I get an error when using cmake to build the third_party_libs (protobuf specifically). I open up the vcxproj/.sln and try a build and get a whole bunch of errors. I have done a recent (last night) "git clone" of the MaidSafe-Common repository, so the suggested CMake solution of "get the latest source" doesn't work.

I can provide the CMake and Visual Studio errors, if helpful (they're too large to post here).

-Jeff