MS C ++ 2010 and mspdb100.dll

Question

The Microsoft C ++ compiler and linker seems to have an odd relationship with mspdb100.dll . Of course, when starting from the IDE, the compiler and linker work fine. When I start one from the command line, I get an error message.

No problem, I found the DLL and copied it to the directory. Now the compiler is working fine, but the linker is dying.

I could solve the problem by adding "% VS10% \ Common7 \ IDE" to my PATH, but for various reasons (performance, system cleanliness, OCD, etc.) I do not want to do this. Why is this setting so moving, and is there anything else I can do to solve it?

Answer 1

try running path\to\VC\bin\vcvars32.bat from inside your current shell. This should ensure that your command line setup matches the IDE setup.

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

Perhaps you can also find a way to add everything in this .bat to the constant environment variables, but ... as you asked, why the hell isn’t the MS installation already doing this?

Answer 2

Add Microsoft Visual Studio 10.0 \ Common7 \ IDE to your path and this problem will no longer exist. You can create without using this stupid batch file every time.

Answer 3

I noticed when I installed Microsoft Visual Studio 2010 Express in the "Microsoft Visual Studio 2010 Express" folder in the "Start" menu, there is a link to the "Visual Studio Command Prompt (2010)", which sets all the necessary environment variables when opened. This way you do not have to edit the PATH variable.

This shortcut does the following:

% comspec% / k "C: \ Program Files \ Microsoft Visual Studio 10.0 \ VC \ vcvarsall.bat" "x86

If you are not comfortable using the shortcut, perhaps you could learn something useful from learning what this .bat file does?

Answer 4

I know this is a bit outdated, but if someone is looking for a way to get the compiler to work from the command line; here is what i did to launch it.

I use Win7 32bit and Visual Studio 2010. I created a small batch file in C: \ Windows. open the cmd prompt on C: \ Windows as an administrator, then type the following:

 copy con cl.bat @"C:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32" %1 %2 %3 %4 %5 %6 @"C:\Program Files\Microsoft Visual Studio 10.0\VC\bin\cl" %1 %2 %3 %4 %5 %6 

then press f6 and press Enter again.

Obviously, the path you will use is the installation path to where you installed Visual Studio.

Now you have a working command line compiler from any location or directory in the windows. To verify this, go to the desktop and open the cmd command as admin; I prefer to use Ctrl + Shift and right click and then select a command prompt. At the command prompt, type "cl" (without quotation marks) and press enter. you will see the message "Configuring the environment for using Microsoft Visual Studio 2010 x86 tools"

type "cl" and press Enter and you will get information about the compiler. you are all ready to compile.

enjoy it!

Answer 5

I met the same error because we installed the vs2010 x86 version on the x64 system ...

Open two folders:

C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319

C: \ Program Files (x86) \ Microsoft Visual Studio 10.0 \ VC \ bin

You will find two cvtres.exe . Click Righ, select Properties, then Details. Uninstall the previous version and cmake will work well. Hope this helps you.

Thanks to "zhoudongao" @ http://bbs.csdn.net/topics/390121452?page=1#post-394768226 .

Answer 6

Maybe this will help someone ...

I solved this problem by adding

 PATH += %PATH_TO_VS_IN_YOUR_SYSTEM%/Common7/IDE; 

in nvcc.profile .

Of course, %PATH_TO_VS_IN_YOUR_SYSTEM% is the actual path to Visual Studio on your system.

Answer 7

Old, but perhaps still valid:

For me, "C: \ Windows \ System32" somehow disappeared from the PATH variable.

Adding the missing folder to the path resolved this error. See Also The VS2010 command line gives an error: cannot determine the location of the VS common tools folder

Answer 8

if you try to run the tools from the cmd.exe window directly, you need to install the environment by running the vcvars32.bat file, which will install the environment for you. instead, you can run the visual studio command line, which automatically starts vcvars32.bat. if you still have a problem, then this is definitely a known variable path problem.

make sure that the variable "path in the environment has the value " c: \ windows \ system32 \ " added to it, because it will need the .bat file to configure the VC tools.

this problem etc. usually occur due to the installation on a machine of many development platforms, which can probably change the path variable.

check it out .. https://schrievkrom.wordpress.com/2011/01/25/error-cannot-determine-the-location-of-the-vs-common-tools-folder/