Advertisement
Guest User

error log -wp compile

a guest
Jun 13th, 2015
284
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.95 KB | None | 0 0
  1. E:\eclipseworkspaces\cocosws\EpicBang>cocos compile -p wp8_1
  2. Running command: compile
  3. Building mode: debug
  4. building
  5. Required VS version : 12.0
  6. find vs in reg : 64bit
  7. find vs in reg : 32bit
  8. Find VS path : E:\Program Files (x86)\Microsoft Visual Studio 12.0\
  9. running: '"E:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\deven
  10. v.com" "E:\eclipseworkspaces\cocosws\EpicBang\frameworks\runtime-src\proj.win8.1
  11. -universal\MyJSGame.sln" /Build "Debug" /Project "MyJSGame.WindowsPhone"'
  12.  
  13.  
  14. Microsoft Visual Studio 2013 Version 12.0.31101.0.
  15. Copyright (C) Microsoft Corp. All rights reserved.
  16.  
  17. The operation could not be completed
  18.  
  19. Use:
  20. devenv [solutionfile | projectfile | anyfile.ext] [switches]
  21.  
  22. The first argument for devenv is usually a solution file or project file.
  23. You can also use any other file as the first argument if you want to have the
  24. file open automatically in an editor. When you enter a project file, the IDE
  25. looks for an .sln file with the same base name as the project file in the
  26. parent directory for the project file. If no such .sln file exists, then the
  27. IDE looks for a single .sln file that references the project. If no such single
  28. .sln file exists, then the IDE creates an unsaved solution with a default .sln
  29. file name that has the same base name as the project file.
  30.  
  31. Command line builds:
  32. devenv solutionfile.sln /build [ solutionconfig ] [ /project projectnameorfile [
  33. /projectconfig name ] ]
  34. Available command line switches:
  35.  
  36. /Build Builds the solution or project with the specified solution
  37. configuration. For example "Debug". If multiple platforms
  38. are possible, the configuration name must be enclosed in quotes
  39. and contain platform name. For example: "Debug|Win32".
  40. /Clean Deletes build outputs.
  41. /Command Starts the IDE and executes the command.
  42. /Deploy Builds and then deploys the specified build configuration.
  43. /Edit Opens the specified files in a running instance of this
  44. application. If there are no running instances, it will
  45. start a new instance with a simplified window layout.
  46. /LCID Sets the default language in the IDE for the UI.
  47. /Log Logs IDE activity to the specified file for troubleshooting.
  48. /NoVSIP Disables the VSIP developer's license key for VSIP testing.
  49. /Out Appends the build log to a specified file.
  50. /Project Specifies the project to build, clean, or deploy.
  51. Must be used with /Build, /Rebuild, /Clean, or /Deploy.
  52. /ProjectConfig Overrides the project configuration specified in the solution
  53. configuration. For example "Debug". If multiple platforms are
  54. possible, the configuration name must be enclosed in quotes
  55. and contain platform name. For example: "Debug|Win32".
  56. Must be used with /Project.
  57. /Rebuild Cleans and then builds the solution or project with the
  58. specified configuration.
  59. /ResetAddin Removes commands and command UI associated with the specified Ad
  60. d-in.
  61. /ResetSettings Restores the IDE's default settings, optionally resets to
  62. the specified VSSettings file.
  63. /ResetSkipPkgs Clears all SkipLoading tags added to VSPackages.
  64. /Run Compiles and runs the specified solution.
  65. /RunExit Compiles and runs the specified solution then closes the IDE.
  66. /SafeMode Launches the IDE in safe mode loading minimal windows.
  67. /Upgrade Upgrades the project or the solution and all projects in it.
  68. A backup of these files will be created as appropriate. Please
  69. see Help on 'Visual Studio Conversion Wizard' for more
  70. information on the backup process.
  71.  
  72. Product-specific switches:
  73.  
  74.  
  75. /componentsDiff Compares two component folders. Requires three arguments:
  76. OptionalTfsServerCollectionUri SourceVersionedServerFolderPath
  77. TargetVersionedServerFolderPath
  78. If OptionalTfsServerCollectionUri is not provided, then an
  79. attempt is made to use the current TFS project collection.
  80.  
  81. /debugexe Open the specified executable to be debugged. The remainder of
  82. the command line is passed to this executable as its arguments.
  83. /diff Compares two files. Takes four parameters:
  84. SourceFile, TargetFile, SourceDisplayName(optional),
  85. TargetDisplayName(optional)
  86. /openProjects /scc:git Opens committed project from git.
  87. Arguments:
  88. /repositoryUrl (/repo):<RequiredRepositoryUrl>
  89. /commitId (/id):<RequiredCommitId>
  90. /project:<RequiredProjectItemPath>
  91. /solution (/sln):<OptionalSolutionItemPath>
  92. /displayId:<OptionalCommitDisplayId>
  93. /timestamp:<OptionalCommitTimestamp>
  94. /comment:<OptionalCommitComment>
  95. /author:<OptionalCommitAuthor>
  96.  
  97. /openProjects /scc:tfs Opens versioned project from tfs.
  98. Arguments:
  99. /collection (/col):<OptionalTfsServerCollectionUri>
  100. /version:<RequiredTfsVersionSpec>
  101. /project:<RequiredProjectServerItemPath>
  102. /solution (/sln):<OptionalSolutionServerItemPath>
  103. If OptionalTfsServerCollectionUri is not provided, then an
  104. attempt is made to use the current TFS project collection.
  105. /sqldbaction Start SQL Server Data Tools and perform the action specified in
  106. the argument string.
  107. /TfsLink Opens Team Explorer and launches a viewer for the
  108. provided artifact URI if one is registered.
  109. /useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variable
  110. s
  111. instead of IDE paths for VC++ builds.
  112.  
  113. To attach the debugger from the command line, use:
  114. VsJITDebugger.exe -p <pid>
  115. Error running command, return code: 1
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement