MS C ++ 2010和mspdb100.dll [英] MS C++ 2010 and mspdb100.dll

查看:131
本文介绍了MS C ++ 2010和mspdb100.dll的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

微软的C ++编译器和链接器似乎与 mspdb100.dll 有着奇怪的关系。当从IDE运行时,编译器和链接器当然可以正常工作。当从命令行运行任何一个,我得到一个错误。



没问题,我找到DLL并将其复制到目录。现在编译器工作正常,但链接器死机。



我可以通过将%VS10%\Common7\IDE添加到我的路径来解决问题,但是各种原因(表现,系统纯度,OCD等),我不想这样做。为什么这个设置太好了,还有什么我可以做的来解决它?

解决方案

尝试运行 path\to\VC\bin\vcvars32.bat 从你当前的shell 第一个。这应该确保您的命令行设置与IDE设置匹配。



这不是一个永久的修复 - 您需要在每次启动新的shell时执行此操作



你可能还会找到一些方法,将 .bat 中的所有内容永久添加到环境变量中,但是....像你问过的,为什么没有MS安装这样做呢?


Microsoft's C++ compiler and linker seem to have an odd relationship with mspdb100.dll. When run from the IDE, of course, the compiler and linker work fine. When running either one from the command line, I get an error.

No problem, I located the DLL and copied it to the directory. Now the compiler works fine, but the linker dies.

I could solve the problem by adding "%VS10%\Common7\IDE" to my PATH, but for various reasons (performance, system purity, OCD, etc), I don't want to do that. Why is this setup so touchy, and is there anything else I can do to solve it?

解决方案

try running path\to\VC\bin\vcvars32.bat from within your current shell first. This should ensure your command-line setup will match the IDE-setup.

This is not a permanent fix -- you need to do it every time you launch a new shell.

You could probably also find some way to add everything that's in that .bat permanently to the environment variables, but.... like you asked, why the heck doesn't the MS install do that already?

这篇关于MS C ++ 2010和mspdb100.dll的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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