API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Sep 8th, 2017
112
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.60 KB | None | 0 0
raw download clone embed print report
  1. Check for working C compiler: cl
  2. Check for working C compiler: cl -- broken
  3. CMake Error at D:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:50 (MESSAGE):
  4. The C compiler "cl" is not able to compile a simple test program.
  5.  
  6. It fails with the following output:
  7.  
  8. Change Dir: H:/Scientific Visualization/Exercise 1/template-build/CMakeFiles/CMakeTmp
  9.  
  10.  
  11.  
  12. Run Build Command:D:\PROGRA~2\MICROS~1.0\Common7\IDE\devenv.com
  13. CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec
  14.  
  15.  
  16.  
  17. Microsoft (R) Visual Studio Version 9.0.21022.8.
  18.  
  19. Copyright (C) Microsoft Corp. All rights reserved.
  20.  
  21.  
  22.  
  23. The project consists entirely of configurations that require support for
  24. platforms which are not installed on this machine. The project cannot be
  25. loaded.
  26.  
  27. The project consists entirely of configurations that require support for
  28. platforms which are not installed on this machine. The project cannot be
  29. loaded.
  30.  
  31. Invalid project
  32.  
  33.  
  34.  
  35. Use:
  36.  
  37. devenv [solutionfile | projectfile | anyfile.ext] [switches]
  38.  
  39.  
  40.  
  41. The first argument for devenv is usually a solution file or project file.
  42.  
  43. You can also use any other file as the first argument if you want to have
  44. the
  45.  
  46. file open automatically in an editor. When you enter a project file, the
  47. IDE
  48.  
  49. looks for an .sln file with the same base name as the project file in the
  50.  
  51. parent directory for the project file. If no such .sln file exists, then
  52. the
  53.  
  54. IDE looks for a single .sln file that references the project. If no such
  55. single
  56.  
  57. .sln file exists, then the IDE creates an unsaved solution with a default
  58. .sln
  59.  
  60. file name that has the same base name as the project file.
  61.  
  62.  
  63.  
  64. Command line builds:
  65.  
  66. devenv solutionfile.sln /build [ solutionconfig ] [ /project
  67. projectnameorfile [ /projectconfig name ] ]
  68.  
  69. Available command line switches:
  70.  
  71.  
  72.  
  73. /Build Builds the solution or project with the specified solution
  74.  
  75. configuration. For example "Debug". If multiple platforms
  76.  
  77. are possible, the configuration name must be enclosed in quotes
  78.  
  79. and contain platform name. For example: "Debug|Win32".
  80.  
  81. /Clean Deletes build outputs.
  82.  
  83. /Command Starts the IDE and executes the command.
  84.  
  85. /Deploy Builds and then deploys the specified build configuration.
  86.  
  87. /Edit Opens the specified files in a running instance of this
  88.  
  89. application. If there are no running instances, it will
  90.  
  91. start a new instance with a simplified window layout.
  92.  
  93. /LCID Sets the default language in the IDE for the UI.
  94.  
  95. /Log Logs IDE activity to the specified file for troubleshooting.
  96.  
  97. /NoVSIP Disables the VSIP developer's license key for VSIP testing.
  98.  
  99. /Out Appends the build log to a specified file.
  100.  
  101. /Project Specifies the project to build, clean, or deploy.
  102.  
  103. Must be used with /Build, /Rebuild, /Clean, or /Deploy.
  104.  
  105. /ProjectConfig Overrides the project configuration specified in the
  106. solution
  107.  
  108. configuration. For example "Debug". If multiple platforms are
  109.  
  110. possible, the configuration name must be enclosed in quotes
  111.  
  112. and contain platform name. For example: "Debug|Win32".
  113.  
  114. Must be used with /Project.
  115.  
  116. /Rebuild Cleans and then builds the solution or project with the
  117.  
  118. specified configuration.
  119.  
  120. /ResetAddin Removes commands and command UI associated with the specified
  121. Add-in.
  122.  
  123. /ResetSettings Restores the IDE's default settings, optionally resets to
  124.  
  125. the specified VSSettings file.
  126.  
  127. /ResetSkipPkgs Clears all SkipLoading tags added to VSPackages.
  128.  
  129. /Run Compiles and runs the specified solution.
  130.  
  131. /RunExit Compiles and runs the specified solution then closes the IDE.
  132.  
  133. /SafeMode Launches the IDE in safe mode loading minimal windows.
  134.  
  135. /Upgrade Upgrades the project or the solution and all projects in it.
  136.  
  137. A backup of these files will be created as appropriate. Please
  138.  
  139. see Help on 'Visual Studio Conversion Wizard' for more
  140.  
  141. information on the backup process.
  142.  
  143.  
  144.  
  145. Product-specific switches:
  146.  
  147.  
  148.  
  149. /debugexe Open the specified executable to be debugged. The
  150.  
  151. remainder of the command line is passed to this
  152.  
  153. executable as its arguments.
  154.  
  155. /useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables
  156.  
  157. instead of IDE paths for VC++ builds.
  158.  
  159.  
  160.  
  161. To attach the debugger from the command line, use:
  162.  
  163. VsJITDebugger.exe -p <pid>
  164.  
  165.  
  166.  
  167.  
  168.  
  169. CMake will not be able to correctly generate this project.
  170. Call Stack (most recent call first):
  171. CMakeLists.txt:2 (PROJECT)
  172.  
  173.  
  174. Configuring incomplete, errors occurred!
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
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!