User forums > Help
is vc10 known to work with nightly builds?
MortenMacFly:
--- Quote from: bvanevery on January 10, 2012, 11:58:46 am ---Perhaps CMake did something goofy. Perhaps C::B just doesn't do what it's supposed to. "Compiler and Debugger" says vc10.
--- End quote ---
Look: If you are using CMake, then Makefiles are being generated which are only called by Code::Blocks. So the compiler / debugger setup of Code::Blocks is not relevant because in case of Makefiles the compiler is not used! All you need to do is that C::B can find the right make executable (nmake in case of VCV10). So verify that the toolchain path is setup to VC10, and includes the folder where nmake is found and the make executable is setup correctly to nmake.
Check your Cmake setup and configure VC 10 correctly in CMake, then let Cmake produce the correct Makefiles. This is probably not an error of Code::Blocks.
bvanevery:
--- Quote from: MortenMacFly on January 10, 2012, 12:15:39 pm ---This is probably not an error of Code::Blocks.
--- End quote ---
One way or another, looking for vc9 is definitely an error of Code::Blocks. I see no reason for that to be happening. The CMake .txt and .cmake files are configured for c:/Program Files/Microsoft Visual Studio 10.0/VC/bin/cl.exe. There is no occurrence of the string "9.0" in any CMake .txt or .cmake file, except for 2 instances for Boost configuration, that have nothing to do with Visual Studio.
I did a new build to make it easier to find the word "nmake" in the CMake files. I am surprised to find out that "nmake" is not given a hardwired path at generation time. So, it has to be found on a search path somewhere. Since nmake actually lives in C:\Program Files\Microsoft Visual Studio 10.0\VC\bin, and that path is configured, C::B should be picking it up. I also tried starting C::B from within a Windows SDK 7.1 Command Prompt environment. Assuming C::B reads its environment, it should be picking it up. But is it?
oBFusCATed:
Have you read this: http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F ?
bvanevery:
--- Quote from: oBFusCATed on January 10, 2012, 01:24:52 pm ---Have you read this: http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F ?
--- End quote ---
Yes, as I said above, I turned on compiler logging and nothing is logged. The suggestion about scrolling down, didn't turn out to matter. There is nothing logged at all, it's failing before ever getting to that stage.
Who has a known good vc10 setup? I've not heard anyone say they have that yet.
seb_seb0:
It works fine for me.
I am using the last nightly (SVN 7671)
I am on Windows 7 64 bits.
I have installed Visual Studio Express 2010
You can see my settings in screenshots
Additional paths in "Toolchain": "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE"
It works as well a 32 bits XP computer (at work). Same settings (only difference : "Program Files" in place of "Program Files (x86)")
Quick Checks you can do:
Are you able to compile a Hello World program on the command line ?
Another easy check: do you have the correct Compiler activated in your project / target ? (menu project -> build options, check the value in the combo-box for the main project and all the targets.) If you have not set it manually, and if VC is not your default compiler, then you will have this message.
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version