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.
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
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
Microsoft (R) Visual C++ 2010 Express Version 10.0.30319.1. Copyright (C) Microsoft Corp. All rights reserved.
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>