Advertisement
Guest User

Untitled

a guest
Dec 21st, 2013
133
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.50 KB | None | 0 0
  1. CMake Error at F:/CMake/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:446 (execute_process):
  2. execute_process given COMMAND argument with no value.
  3. Call Stack (most recent call first):
  4. F:/CMake/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:48 (CMAKE_DETERMINE_COMPILER_ID_VENDOR)
  5. F:/CMake/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
  6. CMakeLists.txt:12 (project)
  7.  
  8.  
  9. The C compiler identification is unknown
  10. The CXX compiler identification is unknown
  11. Check for working CXX compiler using: Visual Studio 10
  12. Check for working CXX compiler using: Visual Studio 10 -- broken
  13. CMake Error at F:/CMake/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:54 (message):
  14. The C++ compiler "F:/Microsoft Visual Studio 10.0/VC/bin/cl.exe" is not
  15. able to compile a simple test program.
  16.  
  17. It fails with the following output:
  18.  
  19. Change Dir: F:/Trinity/Build/CMakeFiles/CMakeTmp
  20.  
  21.  
  22.  
  23. Run Build Command:f:\MICROS~1.0\Common7\IDE\devenv.com
  24. CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec4131365674
  25.  
  26.  
  27.  
  28.  
  29. Microsoft (R) Visual Studio Version 10.0.40219.1.
  30.  
  31.  
  32. Copyright (C) Microsoft Corp. All rights reserved.
  33.  
  34.  
  35.  
  36.  
  37.  
  38. 'F:\Trinity\Build\CMakeFiles\CMakeTmp\ALL_BUILD.vcxproj' cannot be opened
  39. because its project type (.vcxproj) is not supported by this version of the
  40. application.
  41.  
  42.  
  43.  
  44. To open it, please use a version that supports this type of project.
  45.  
  46.  
  47. 'F:\Trinity\Build\CMakeFiles\CMakeTmp\cmTryCompileExec4131365674.vcxproj'
  48. cannot be opened because its project type (.vcxproj) is not supported by
  49. this version of the application.
  50.  
  51.  
  52.  
  53. To open it, please use a version that supports this type of project.
  54.  
  55.  
  56. Invalid project
  57.  
  58.  
  59.  
  60.  
  61.  
  62. Use:
  63.  
  64.  
  65. devenv [solutionfile | projectfile | anyfile.ext] [switches]
  66.  
  67.  
  68.  
  69.  
  70.  
  71. The first argument for devenv is usually a solution file or project file.
  72.  
  73.  
  74. You can also use any other file as the first argument if you want to have
  75. the
  76.  
  77.  
  78. file open automatically in an editor. When you enter a project file, the
  79. IDE
  80.  
  81.  
  82. looks for an .sln file with the same base name as the project file in the
  83.  
  84.  
  85. parent directory for the project file. If no such .sln file exists, then
  86. the
  87.  
  88.  
  89. IDE looks for a single .sln file that references the project. If no such
  90. single
  91.  
  92.  
  93. .sln file exists, then the IDE creates an unsaved solution with a default
  94. .sln
  95.  
  96.  
  97. file name that has the same base name as the project file.
  98.  
  99.  
  100.  
  101.  
  102.  
  103. Command line builds:
  104.  
  105.  
  106. devenv solutionfile.sln /build [ solutionconfig ] [ /project
  107. projectnameorfile [ /projectconfig name ] ]
  108.  
  109.  
  110. Available command line switches:
  111.  
  112.  
  113.  
  114.  
  115.  
  116. /Build Builds the solution or project with the specified solution
  117.  
  118.  
  119. configuration. For example "Debug". If multiple platforms
  120.  
  121.  
  122. are possible, the configuration name must be enclosed in quotes
  123.  
  124.  
  125. and contain platform name. For example: "Debug|Win32".
  126.  
  127.  
  128. /Clean Deletes build outputs.
  129.  
  130.  
  131. /Command Starts the IDE and executes the command.
  132.  
  133.  
  134. /Deploy Builds and then deploys the specified build configuration.
  135.  
  136.  
  137. /Edit Opens the specified files in a running instance of this
  138.  
  139.  
  140. application. If there are no running instances, it will
  141.  
  142.  
  143. start a new instance with a simplified window layout.
  144.  
  145.  
  146. /LCID Sets the default language in the IDE for the UI.
  147.  
  148.  
  149. /Log Logs IDE activity to the specified file for troubleshooting.
  150.  
  151.  
  152. /NoVSIP Disables the VSIP developer's license key for VSIP testing.
  153.  
  154.  
  155. /Out Appends the build log to a specified file.
  156.  
  157.  
  158. /Project Specifies the project to build, clean, or deploy.
  159.  
  160.  
  161. Must be used with /Build, /Rebuild, /Clean, or /Deploy.
  162.  
  163.  
  164. /ProjectConfig Overrides the project configuration specified in the
  165. solution
  166.  
  167.  
  168. configuration. For example "Debug". If multiple platforms are
  169.  
  170.  
  171. possible, the configuration name must be enclosed in quotes
  172.  
  173.  
  174. and contain platform name. For example: "Debug|Win32".
  175.  
  176.  
  177. Must be used with /Project.
  178.  
  179.  
  180. /Rebuild Cleans and then builds the solution or project with the
  181.  
  182.  
  183. specified configuration.
  184.  
  185.  
  186. /ResetAddin Removes commands and command UI associated with the specified
  187. Add-in.
  188.  
  189.  
  190. /ResetSettings Restores the IDE's default settings, optionally resets to
  191.  
  192.  
  193. the specified VSSettings file.
  194.  
  195.  
  196. /ResetSkipPkgs Clears all SkipLoading tags added to VSPackages.
  197.  
  198.  
  199. /Run Compiles and runs the specified solution.
  200.  
  201.  
  202. /RunExit Compiles and runs the specified solution then closes the IDE.
  203.  
  204.  
  205. /SafeMode Launches the IDE in safe mode loading minimal windows.
  206.  
  207.  
  208. /Upgrade Upgrades the project or the solution and all projects in it.
  209.  
  210.  
  211. A backup of these files will be created as appropriate. Please
  212.  
  213.  
  214. see Help on 'Visual Studio Conversion Wizard' for more
  215.  
  216.  
  217. information on the backup process.
  218.  
  219.  
  220.  
  221.  
  222.  
  223. Product-specific switches:
  224.  
  225.  
  226.  
  227.  
  228.  
  229. /debugexe Open the specified executable to be debugged. The
  230.  
  231.  
  232. remainder of the command line is passed to this
  233.  
  234.  
  235. executable as its arguments.
  236.  
  237.  
  238.  
  239.  
  240.  
  241. To attach the debugger from the command line, use:
  242.  
  243.  
  244. VsJITDebugger.exe -p <pid>
  245.  
  246.  
  247.  
  248.  
  249.  
  250.  
  251. CMake will not be able to correctly generate this project.
  252. Call Stack (most recent call first):
  253. CMakeLists.txt:12 (project)
  254.  
  255.  
  256. Configuring incomplete, errors occurred!
  257. See also "F:/Trinity/Build/CMakeFiles/CMakeOutput.log".
  258. See also "F:/Trinity/Build/CMakeFiles/CMakeError.log".
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement