User forums > Help
is vc10 known to work with nightly builds?
bvanevery:
I am using C::B SVN 7550. I'm trying to get it to work with a Windows SDK 7.1 installation on Vista. I'm endeavoring to build Ogre with CMake. I can build it fine using Visual Studio 2010 Express, or from a MSBuild command line. Now I am trying to do a C::B Nmake build. I selected a C::B nightly build because 10.05 doesn't have vc10 under Settings... Compiler and Debugger... Selected Compiler. SVN 7550 does, but no amount of path configuration has yielded any joy. I believe I've stated plenty of them:
Search Directories:
Compiler:
c:\Program Files\Microsoft Visual Studio 10.0\VC\include
C:\Program Files\Microsoft SDKs\Windows\v7.1\INCLUDE
Linker:
c:\Program Files\Microsoft Visual Studio 10.0\VC\lib
C:\Program Files\Microsoft SDKs\Windows\v7.1\Lib
C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework\v3.5
Resource Compiler (decided by C::B, not me)
c:\Program Files\Microsoft Visual Studio 10.0\VC\include
Toolchain Executables:
Compiler's installation directory (auto-detected):
c:\Program Files\Microsoft Visual Studio 10.0\VC
Additional Paths:
C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework\v3.5
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE
C:\Program Files\Microsoft Visual Studio 10.0\Common7\Tools
c:\Program Files\Microsoft Visual Studio 10.0\VC\Bin\VCPackages
C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools
C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin
These I copied at some labor from the environment of my Windows SDK 7.1 command prompt. Have I missed something, or do C::B nightlies simply not work with vc10? The error is:
--- Quote ---"OGRE - all": The compiler's setup is invalid so Code::Blocks cannot find/run the compiler. Probably the toolchain path within the compiler options is not setup correctly?! Skipping...
Nothing to be done (all items are up-to-date).
--- End quote ---
Alpha:
First see if removing all of your paths, then clicking Auto-detect, enables it to work correctly.
If not, try the following.
Toolchain executables: Compiler's installation directory:
--- Code: ---C:\Program Files\Microsoft Visual Studio 10.0\VC
--- End code ---
Toolchain executables: Additional Paths:
--- Code: ---C:\Program Files\Microsoft Visual Studio 10.0\VC\bin
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE
C:\Program Files\Microsoft SDKs\Windows\v7.1\bin
--- End code ---
Search directories: Compiler:
--- Code: ---C:\Program Files\Microsoft Visual Studio 10.0\VC\include
C:\Program Files\Microsoft SDKs\Windows\v7.1\Include
--- End code ---
Search directories: Linker:
--- Code: ---C:\Program Files\Microsoft Visual Studio 10.0\VC\lib
C:\Program Files\Microsoft SDKs\Windows\v7.1\Lib
--- End code ---
bvanevery:
--- Quote from: Alpha on January 09, 2012, 11:54:32 pm ---First see if removing all of your paths, then clicking Auto-detect, enables it to work correctly.
--- End quote ---
I started these explorations with no additional paths, just auto-detect, and it didn't work. That's why I added all those paths in the 1st place, in accord with all the forum searching and finding the Installing A Supported Compiler wiki page.
--- Quote ---If not, try the following.
--- End quote ---
Amounting to, removing .NET search directories, and adding a (supposed to be unnecessary) \VC\bin directory.
On some previous run I didn't have the .NET directories. Thus that's not the problem. Also, they're not supposed to matter as they're .NET things, not C/C++ things. In any event they're standard Windows SDK paths in a standard order. I'd be more willing to delete the .NET paths if it didn't require deleting everything to re-add them later. Some other IDEs have "shift up and down" arrows, or at least will insert a new entry after the highlighted cursor. I'll make some feature requests about that.
If adding \VC\bin were necessary, that would indeed be quite a bug. But adding it didn't change anything, so that's not the problem. (Or else there are multiple problems, rendering this tactic ineffective.)
I've turned on compiler logging. Oddly, this has no effect on messages at all. It would seem that "the compiler's setup is invalid" is really to be taken at face value. Nothing is happening that can be logged.
I will ask again, in case it was missed due to the amount of material I've presented. Is vc10 known to work with nightly builds?
Does someone have a known good, proven installation that can happily compile vc10 projects? If so, then another possibility is a CMake problem, which I haven't explored yet. CMake MinGW builds work fine; this is a CMake Nmake build.
Alternately, can someone reproduce the error?
Alpha:
--- Quote from: bvanevery on January 10, 2012, 02:29:39 am ---
--- Quote ---If not, try the following.
--- End quote ---
Amounting to, removing .NET search directories, and adding a (supposed to be unnecessary) \VC\bin directory.
--- End quote ---
OK, just double checking something easy had not been missed (I had written from memory as I do not currently have Visual Studio installed).
--- Quote from: bvanevery on January 10, 2012, 02:29:39 am ---I've turned on compiler logging. Oddly, this has no effect on messages at all. It would seem that "the compiler's setup is invalid" is really to be taken at face value. Nothing is happening that can be logged.
--- End quote ---
I assume you have tried scrolling (I cannot find any text in my Code::Blocks logs?).
--- Quote from: bvanevery on January 10, 2012, 02:29:39 am ---If so, then another possibility is a CMake problem, which I haven't explored yet. CMake MinGW builds work fine; this is a CMake Nmake build.
--- End quote ---
Sorry, I had missed when you mentioned CMake the first time.
Is the CMake executable in your system's/Code::Blocks executable's path?
Does CMake support generating a .cbp that use VC?
Is your project set up to use the Nmake file as a makefile?
If you create a standard console project using Code::Blocks' project wizard, does it compile?
Do all of the programs listed in your toolchain executables correspond to an actual program on your hard drive?
Try launching Code::Blocks with the -v argument (codeblocks.exe -v); some of the additional output may find the root of the problem.
bvanevery:
--- Quote from: Alpha on January 10, 2012, 06:05:19 am ---Try launching Code::Blocks with the -v argument
--- End quote ---
#@!# it's trying to find vc9! "Execution of command 'C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\cl.exe' failed (the system cannot find the file specified.)" That directory did exist on my system recently, but I deleted it. Perhaps it is reading a stale or inappropriate value from the registry. Perhaps CMake did something goofy. Perhaps C::B just doesn't do what it's supposed to. "Compiler and Debugger" says vc10. It's 6 am and I'm too tired to continue right now, will resume later.
Later came sooner. I threw out my previous CMake build. This time instead of accepting the default compiler, I manually specified the C and C++ compilers. They are set to C:\Program Files\Microsoft Visual Studio 10.0\VC\bin\cl.exe . I get the same error as before, it's trying to find vc9. I haven't checked all of CMake's internals but I think it is unlikely to be configured for vc9. C::B appears to search for vc9 inappropriately. It may be a general problem, or it may be specific to my system due to a messed up registry.
Can anyone reproduce the problem?
Navigation
[0] Message Index
[#] Next page
Go to full version