User forums > Help
is vc10 known to work with nightly builds?
bvanevery:
--- Quote from: seb_seb0 on January 10, 2012, 10:24:28 pm ---Quick Checks you can do:
Are you able to compile a Hello World program on the command line ?
--- End quote ---
Only if I fire up a Windows SDK 7.1 command prompt. Otherwise, paths to vc10 are (deliberately) not available. This is a self-defense strategy when working with multiple compilers and builds on Windows.
--- Quote ---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.
--- End quote ---
I'm using SVN 7671 now. I'll be darned, the default for the option you describe is "Microsoft Visual C++ 2005/2008." And now that I change it to vc10, the build magically starts to work. I am wondering if this is a misfeature. I would have expected the project options to be the same as I configured with CMake. Pretty rough learning curve if this is expected behavior; thanks for straightening this out.
MortenMacFly:
--- Quote from: bvanevery on January 11, 2012, 01:38:42 am ---I would have expected the project options to be the same as I configured with CMake. Pretty rough learning curve if this is expected behavior; thanks for straightening this out.
--- End quote ---
How should that be? Code::Blocks does know nothing about CMake and actually cannot know anything. It's your duty to setup the project to let C::B know what you've actually configured in CMake.
bvanevery:
--- Quote from: MortenMacFly on January 11, 2012, 07:48:32 am ---
--- Quote from: bvanevery on January 11, 2012, 01:38:42 am ---I would have expected the project options to be the same as I configured with CMake. Pretty rough learning curve if this is expected behavior; thanks for straightening this out.
--- End quote ---
How should that be? Code::Blocks does know nothing about CMake and actually cannot know anything. It's your duty to setup the project to let C::B know what you've actually configured in CMake.
--- End quote ---
CMake knows the format of the .cbp file and generates such. I would expect a .cbp file to provide the compiler info to C::B. It is possible that CMake does not in fact put the compiler info in the .cbp file; I don't know. But if a .cbp file can't tell C::B which compiler to use even in principle, that's bad design. As is making this sort of trivia "my responsibility." But hey, open source is for fixing things, right?
oBFusCATed:
Yes, CMake doesn't know your compiler setup.
Also it is not logical to put the compiler setup in the project,
because the purpose of the project (original one) is to be computer independent,
so you can move the project and it will work on your friends machine,
if he has the correct compiler and libraries.
MortenMacFly:
--- Quote from: oBFusCATed on January 11, 2012, 09:26:17 am ---Also it is not logical to put the compiler setup in the project,
--- End quote ---
I guess he meant a "pointer" to the compiler to use. This (of course) is in the project file. However, where the compiler is and where it has its resources is (as oBFusCATed stated correctly) user depended. So this is a "user global" configuration you are responsible for inside C::B, not using CMake.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version