API tools faq
paste
Guest User

Untitled

a guest
Oct 6th, 2011
197
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.87 KB | None | 0 0
raw download clone embed print report
  1. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE):
  2. The C compiler "cl" is not able to compile a simple test program.
  3.  
  4. It fails with the following output:
  5.  
  6. Change Dir: D:/Ujcore/CMakeFiles/CMakeTmp
  7.  
  8.  
  9.  
  10. Run Build Command:D:\PROGRA~1\MICROS~1.0\Common7\IDE\devenv.com
  11. CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec
  12.  
  13.  
  14.  
  15. Microsoft (R) Visual Studio Version 9.0.21022.8.
  16.  
  17. Copyright (C) Microsoft Corp. All rights reserved.
  18.  
  19.  
  20.  
  21. The project consists entirely of configurations that require support for
  22. platforms which are not installed on this machine. The project cannot be
  23. loaded.
  24.  
  25. The project consists entirely of configurations that require support for
  26. platforms which are not installed on this machine. The project cannot be
  27. loaded.
  28.  
  29. Invalid project
  30.  
  31.  
  32.  
  33. Use:
  34.  
  35. devenv [solutionfile | projectfile | anyfile.ext] [switches]
  36.  
  37.  
  38.  
  39. The first argument for devenv is usually a solution file or project file.
  40.  
  41. You can also use any other file as the first argument if you want to have
  42. the
  43.  
  44. file open automatically in an editor. When you enter a project file, the
  45. IDE
  46.  
  47. looks for an .sln file with the same base name as the project file in the
  48.  
  49. parent directory for the project file. If no such .sln file exists, then
  50. the
  51.  
  52. IDE looks for a single .sln file that references the project. If no such
  53. single
  54.  
  55. .sln file exists, then the IDE creates an unsaved solution with a default
  56. .sln
  57.  
  58. file name that has the same base name as the project file.
  59.  
  60.  
  61.  
  62. Command line builds:
  63.  
  64. devenv solutionfile.sln /build [ solutionconfig ] [ /project
  65. projectnameorfile [ /projectconfig name ] ]
  66.  
  67. Available command line switches:
  68.  
  69.  
  70.  
  71. /Build Builds the solution or project with the specified solution
  72.  
  73. configuration. For example "Debug". If multiple platforms
  74.  
  75. are possible, the configuration name must be enclosed in quotes
  76.  
  77. and contain platform name. For example: "Debug|Win32".
  78.  
  79. /Clean Deletes build outputs.
  80.  
  81. /Command Starts the IDE and executes the command.
  82.  
  83. /Deploy Builds and then deploys the specified build configuration.
  84.  
  85. /Edit Opens the specified files in a running instance of this
  86.  
  87. application. If there are no running instances, it will
  88.  
  89. start a new instance with a simplified window layout.
  90.  
  91. /LCID Sets the default language in the IDE for the UI.
  92.  
  93. /Log Logs IDE activity to the specified file for troubleshooting.
  94.  
  95. /NoVSIP Disables the VSIP developer's license key for VSIP testing.
  96.  
  97. /Out Appends the build log to a specified file.
  98.  
  99. /Project Specifies the project to build, clean, or deploy.
  100.  
  101. Must be used with /Build, /Rebuild, /Clean, or /Deploy.
  102.  
  103. /ProjectConfig Overrides the project configuration specified in the
  104. solution
  105.  
  106. configuration. For example "Debug". If multiple platforms are
  107.  
  108. possible, the configuration name must be enclosed in quotes
  109.  
  110. and contain platform name. For example: "Debug|Win32".
  111.  
  112. Must be used with /Project.
  113.  
  114. /Rebuild Cleans and then builds the solution or project with the
  115.  
  116. specified configuration.
  117.  
  118. /ResetAddin Removes commands and command UI associated with the specified
  119. Add-in.
  120.  
  121. /ResetSettings Restores the IDE's default settings, optionally resets to
  122.  
  123. the specified VSSettings file.
  124.  
  125. /ResetSkipPkgs Clears all SkipLoading tags added to VSPackages.
  126.  
  127. /Run Compiles and runs the specified solution.
  128.  
  129. /RunExit Compiles and runs the specified solution then closes the IDE.
  130.  
  131. /SafeMode Launches the IDE in safe mode loading minimal windows.
  132.  
  133. /Upgrade Upgrades the project or the solution and all projects in it.
  134.  
  135. A backup of these files will be created as appropriate. Please
  136.  
  137. see Help on 'Visual Studio Conversion Wizard' for more
  138.  
  139. information on the backup process.
  140.  
  141.  
  142.  
  143. Product-specific switches:
  144.  
  145.  
  146.  
  147. /debugexe Open the specified executable to be debugged. The
  148.  
  149. remainder of the command line is passed to this
  150.  
  151. executable as its arguments.
  152.  
  153. /useenv CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE):
  154. The C compiler "cl" is not able to compile a simple test program.
  155.  
  156. It fails with the following output:
  157.  
  158. Change Dir: D:/Ujcore/CMakeFiles/CMakeTmp
  159.  
  160.  
  161.  
  162. Run Build Command:D:\PROGRA~1\MICROS~1.0\Common7\IDE\devenv.com
  163. CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec
  164.  
  165.  
  166.  
  167. Microsoft (R) Visual Studio Version 9.0.21022.8.
  168.  
  169. Copyright (C) Microsoft Corp. All rights reserved.
  170.  
  171.  
  172.  
  173. The project consists entirely of configurations that require support for
  174. platforms which are not installed on this machine. The project cannot be
  175. loaded.
  176.  
  177. The project consists entirely of configurations that require support for
  178. platforms which are not installed on this machine. The project cannot be
  179. loaded.
  180.  
  181. Invalid project
  182.  
  183.  
  184.  
  185. Use:
  186.  
  187. devenv [solutionfile | projectfile | anyfile.ext] [switches]
  188.  
  189.  
  190.  
  191. The first argument for devenv is usually a solution file or project file.
  192.  
  193. You can also use any other file as the first argument if you want to have
  194. the
  195.  
  196. file open automatically in an editor. When you enter a project file, the
  197. IDE
  198.  
  199. looks for an .sln file with the same base name as the project file in the
  200.  
  201. parent directory for the project file. If no such .sln file exists, then
  202. the
  203.  
  204. IDE looks for a single .sln file that references the project. If no such
  205. single
  206.  
  207. .sln file exists, then the IDE creates an unsaved solution with a default
  208. .sln
  209.  
  210. file name that has the same base name as the project file.
  211.  
  212.  
  213.  
  214. Command line builds:
  215.  
  216. devenv solutionfile.sln /build [ solutionconfig ] [ /project
  217. projectnameorfile [ /projectconfig name ] ]
  218.  
  219. Available command line switches:
  220.  
  221.  
  222.  
  223. /Build Builds the solution or project with the specified solution
  224.  
  225. configuration. For example "Debug". If multiple platforms
  226.  
  227. are possible, the configuration name must be enclosed in quotes
  228.  
  229. and contain platform name. For example: "Debug|Win32".
  230.  
  231. /Clean Deletes build outputs.
  232.  
  233. /Command Starts the IDE and executes the command.
  234.  
  235. /Deploy Builds and then deploys the specified build configuration.
  236.  
  237. /Edit Opens the specified files in a running instance of this
  238.  
  239. application. If there are no running instances, it will
  240.  
  241. start a new instance with a simplified window layout.
  242.  
  243. /LCID Sets the default language in the IDE for the UI.
  244.  
  245. /Log Logs IDE activity to the specified file for troubleshooting.
  246.  
  247. /NoVSIP Disables the VSIP developer's license key for VSIP testing.
  248.  
  249. /Out Appends the build log to a specified file.
  250.  
  251. /Project Specifies the project to build, clean, or deploy.
  252.  
  253. Must be used with /Build, /Rebuild, /Clean, or /Deploy.
  254.  
  255. /ProjectConfig Overrides the project configuration specified in the
  256. solution
  257.  
  258. configuration. For example "Debug". If multiple platforms are
  259.  
  260. possible, the configuration name must be enclosed in quotes
  261.  
  262. and contain platform name. For example: "Debug|Win32".
  263.  
  264. Must be used with /Project.
  265.  
  266. /Rebuild Cleans and then builds the solution or project with the
  267.  
  268. specified configuration.
  269.  
  270. /ResetAddin Removes commands and command UI associated with the specified
  271. Add-in.
  272.  
  273. /ResetSettings Restores the IDE's default settings, optionally resets to
  274.  
  275. the specified VSSettings file.
  276.  
  277. /ResetSkipPkgs Clears all SkipLoading tags added to VSPackages.
  278.  
  279. /Run Compiles and runs the specified solution.
  280.  
  281. /RunExit Compiles and runs the specified solution then closes the IDE.
  282.  
  283. /SafeMode Launches the IDE in safe mode loading minimal windows.
  284.  
  285. /Upgrade Upgrades the project or the solution and all projects in it.
  286.  
  287. A backup of these files will be created as appropriate. Please
  288.  
  289. see Help on 'Visual Studio Conversion Wizard' for more
  290.  
  291. information on the backup process.
  292.  
  293.  
  294.  
  295. Product-specific switches:
  296.  
  297.  
  298.  
  299. /debugexe Open the specified executable to be debugged. The
  300.  
  301. remainder of the command line is passed to this
  302.  
  303. executable as its arguments.
  304.  
  305. /useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables
  306.  
  307. instead of IDE paths for VC++ builds.
  308.  
  309.  
  310.  
  311. To attach the debugger from the command line, use:
  312.  
  313. VsJITDebugger.exe -p <pid>
  314.  
  315.  
  316.  
  317.  
  318.  
  319. CMake will not be able to correctly generate this project.
  320. Call Stack (most recent call first):
  321. CMakeLists.txt:16 (project)Use PATH, INCLUDE, LIBPATH, and LIB environment variables
  322.  
  323. instead of IDE paths for VC++ builds.
  324.  
  325.  
  326.  
  327. To attach the debugger from the command line, use:
  328.  
  329. VsJITDebugger.exe -p <pid>
  330.  
  331.  
  332.  
  333.  
  334.  
  335. CMake will not be able to correctly generate this project.
  336. Call Stack (most recent call first):
  337. CMakeLists.txt:16 (project)
  338.  
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!