Visual Studio 2013:CL.exe退出与代码-1073741515 [英] Visual Studio 2013: CL.exe exited with code -1073741515

查看:4046
本文介绍了Visual Studio 2013:CL.exe退出与代码-1073741515的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个新鲜的Windows 8.1 Pro x64安装与新鲜 Visual Studio 2013 Pro。
当尝试使用Platform Toolset将项目编译为 Windows7.1SDK 时,我会收到

 错误1错误MSB6006:CL.exe退出,代码为-1073741515。 C:\Program Files(x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.targets 57 5 MenuBrowser 

我试过运行提供的Windows SDK配置工具,除了得到一个关于Visual Studio 2005和2008的错误没有安装我认为它的工作。



我尝试手动编辑注册表:

  HKEY_LOCAL_MACHINE \ SOFTWARE \Microsoft \Microsoft SDKs \Windows 

其中我手动将 CurrentInstallFolder as C:\Program Files \Microsoft SDKs\Windows\v7.1\ CurrentVersion as 7.1.7600.0.30514 。如果我看看项目属性,并点击不同的路径/变量在那里 - >更多 - >宏,我可以看到$(WindowsSdkDir)是正确的。



想我应该尝试什么?从未在Windows 7和VS 2012的旧开发计算机上遇到此问题。



L.E。作为注释,如果我尝试一个新的项目与v120工具,它的工作,但我需要Windows7.1SDK工具。

解决方案

blockquote>

尝试使用Platform Toolset将项目编译为Windows7.1SDK ...


在VS2013的新鲜安装中的有效选择。不是很清楚你一直在做什么,它肯定不是新鲜了。将Regedit.exe作为加载的武器,配置VS的注册表项设置已经变得很漂亮doggone convoluted as the late。



编译器崩溃与-1073741515 == 0xC0000135 == STATUS_DLL_NOT_FOUND。这是一个非常严重的不幸,当你定位SDK 7.1时,它应该永远不会发生,因为仍然使用相同的编译器,只有SDK目录被改变。编译器本身以及它使用的DLL不是SDK的一部分,只有在机器没有安装VS时才提供。您可以使用SysInternals的进程监视器来诊断此情况,您会看到CL.EXE进程搜索DLL而找不到它。



正确方式到目标7.1是使用v120_xp工具集选择。这将构建仍然可以在XP上运行的程序,它还自动选择安装在机器上的7.1A SDK。请尝试撤消您所做的更改。


I have a fresh Windows 8.1 Pro x64 install with a fresh Visual Studio 2013 Pro. When trying to compile a project with Platform Toolset to Windows7.1SDK I'm getting

Error   1   error MSB6006: "CL.exe" exited with code -1073741515.   C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.targets   57  5   MenuBrowser

I tried running the supplied "Windows SDK Configuration Tool" and besides getting an error about Visual Studio 2005 and 2008 not being installed I think it did its job.

I tried manually editing the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows

where I manually put CurrentInstallFolder as C:\Program Files\Microsoft SDKs\Windows\v7.1\ and CurrentVersion as 7.1.7600.0.30514. If I look at the project properties and click the different paths / variables in there -> more -> Macros, I can see that $(WindowsSdkDir) is correct.

Any idea as to what I should try? Never ran into this problem on the old development computer with Windows 7 and VS 2012.

L.E. as a note, if I try a new project with the v120 tools, it works, but I need the Windows7.1SDK tools.

解决方案

When trying to compile a project with Platform Toolset to Windows7.1SDK...

That's not a valid selection in a "fresh" install for VS2013. Not very clear what you've been doing, it certainly isn't "fresh" anymore. Do treat Regedit.exe as a loaded weapon, the registry key set that configures VS has been getting pretty doggone convoluted as of late.

The compiler crashes with -1073741515 == 0xC0000135 == STATUS_DLL_NOT_FOUND. That's a pretty serious mishap of course, it should never occur when you target SDK 7.1 since that still uses the same compiler, only the SDK directory is changed. The compiler itself, as well as the DLLs it uses, are not part of the SDK and only are provided if the machine doesn't have VS installed. You can use SysInternals' Process Monitor to diagnose this, you'll see the CL.EXE process searching for a DLL and not finding it.

The correct way to target 7.1 is to use the v120_xp toolset selection. That builds programs that can still run on XP, it automatically also selects the 7.1A SDK that was installed on your machine. Do try to undo the changes you've made.

这篇关于Visual Studio 2013:CL.exe退出与代码-1073741515的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆