CMake does use env vars PATH, LIB and INCLUDE when detecting executables,
libraries and header files. If your env is set up on a machine-wide basis for
vs 2003, it would not surprise me if some things were found inconsistently when
attempting to build for vs 10...
On Nov 19, 2011, at 1:48 PM,
I think though that by default, no visual studio installations place the
install path in PATH in the environment. So if I'm remembering correctly
and that is true, what other means does it use? Does it use the registry at
all? If you could kindly describe the search path it uses that would be
very
On 11/21/2011 9:23 AM, Robert Dailey wrote:
I think though that by default, no visual studio installations place the
install path in PATH in the environment. So if I'm remembering correctly
and that is true, what other means does it use? Does it use the registry
at all? If you could kindly
I have the following versions of VS installed:
VS 2003
VS 2005
VS 2008
VC 2010 Express
So I can imagine there would be a lot of confusion :P
FWIW, CMake can find VS 2003 and VS2008 just fine.
I will look at the script and debug this a bit and then report back to you
guys. Thanks for the
So I modified the CMakeVS10FindMake.cmake module to print the result of the
first call to find_program():
FIND_PROGRAM(CMAKE_MAKE_PROGRAM
NAMES devenv
HINTS
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Setup\\VS;EnvironmentDirectory]
I has been my experience with multiple versions of Visual studio installed on
Windows to remove any trace of visual studio from the system path. Period.
Having any path in the system wide PATH or User Wide PATH variable will
inevitably lead to odd ball issues like this. Then, like I said
I've also always found a key ingredient in making multiple versions of
Visual Studio work well with each other is to keep them from adding
anything about themselves into system-wide or user-wide env var
values. It's both unnecessary and counterproductive.
Especially given the fact that VS itself
Seems that for some reason the VC2010 scripts are finding the VS 2003
compiler, which is where the shorthand form of that path points. Obviously
the path for VC2010 Express doesn't have .NET in the path.
Where is it looking for the path to VC2010 Express? Maybe my environment is
setup improperly.
The best way to ensure your environment is setup correctly is to launch
cmake from one of the dedicated command prompts that come with visual
studio.
-
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software
I mean specifically is there some environment variable that CMake checks
for the location of VC2010? I want to make sure the correct path is set on
it.
Thanks.
-
Robert Dailey
On Sat, Nov 19, 2011 at 12:08 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
The best way to ensure
When I try to configure my project in CMake 2.8.6 using VC 2010 Express, I
get the following error. Any reason why?
Check for working C compiler using: Visual Studio 10
Check for working C compiler using: Visual Studio 10 -- broken
CMake Error at C:/Program Files (x86)/CMake
Well since this is VC Express, I don't have a devenv.com file in my
Common7 folder, so I guess that explains it?
Shouldn't CMake support VC2010 express?
-
Robert Dailey
On Fri, Nov 18, 2011 at 5:10 PM, Robert Dailey rcdai...@gmail.com wrote:
When I try to configure my project in
On 11/18/2011 6:10 PM, Robert Dailey wrote:
Run Build Command:C:\PROGRA~2\MICROS~2.NET
http://2.NET\Common7\IDE\devenv.com http://devenv.com
CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec
Microsoft (R) Development Environment Version 7.10.6030.
Looks like it is running VS 7,
On 11/18/2011 6:58 PM, Robert Dailey wrote:
Well since this is VC Express, I don't have a devenv.com
http://devenv.com file in my Common7 folder, so I guess that explains it?
Shouldn't CMake support VC2010 express?
-
It does, it is just confused because you have two compilers...
See
14 matches
Mail list logo
