On Fri, Nov 13, 2009 at 4:01 PM, wrote:
>
> I'm sorry, I was being a little flippant. I had an un-escaped "\" in my
> perl script that set the INCLUDE environment variable. Apparently, CMake was
> unable to compile a test program because of this messed up path, and thus
> assumed the box must be
mean to mislead you.
-
Aaron Wright
John Drescher
11/13/2009 11:24 AM
To
aaron_wri...@selinc.com, CMake mailing list
cc
Subject
Re: [CMake] NMake Generation Error: machine type 'X86' conflicts with
target machine type 'x64
On Fri, Nov 13, 2009 at 1:15 PM, wrote:
>
> Bill,
> I think you were right. I took a hard look at my SDK paths and
> changed a capital "I" to a lower-case "i" and everything seems better.
> Thanks for help.
>
I am confused about that. Windows paths and filenames are not case
sensitive.
aaron_wri...@selinc.com wrote:
Bill,
I think you were right. I took a hard look at my SDK paths and
changed a capital "I" to a lower-case "i" and everything seems better.
Thanks for help.
On a side note, perhaps "assuming" x64 when x86 fails is a bad
algorithm, or at least c
gorithm, or at least confusing.
-
Aaron Wright
Bill Hoffman
Sent by: cmake-boun...@cmake.org
11/13/2009 09:07 AM
To
aaron_wri...@selinc.com
cc
CMake , Bill Hoffman
Subject
Re: [CMake] NMake Generation Error: machine type 'X86' conflicts with
t
aaron_wri...@selinc.com wrote:
I have the windows SDK installed. It came with Visual Studio. I run
everything from perl, so in my script, I set the environment to:
$ENV{"VSINSTALLDIR"} = "C:\\Program Files\\Microsoft Visual
Studio 9.0";
$ENV{"VCINSTALLDIR"} = "C:\\Program F
dows\\v6.0A\\Lib;" .
$ENV{"LIB"};
$ENV{"LIBPATH"} =
"C:\\WINDOWS\\Microsoft.NET\\Framework\\v3.5;C:\\WINDOWS\\Microsoft.NET\\Framework\\v2.0.50727;C:\\Program
Files\\Microsoft Visual Studio 9.0\\VC\\LIB;" . $ENV{"LIBPATH"};
Note the Windows SDK
-
Richard Wackerbarth wrote:
Aaron,
Perhaps I have it wrong, but I think that the problem is that you are using
CMakeCache.txt that was created on a different machine.
CMakeCache.txt acts as a "configuration file" that overrides the registry,
environmental variables, and everything else that ha
for it in one pass.
-
Aaron Wright
Richard Wackerbarth
Sent by: cmake-boun...@cmake.org
11/13/2009 08:46 AM
Please respond to
Richard Wackerbarth
To
aaron_wri...@selinc.com
cc
CMake
Subject
Re: [CMake] NMake Generation Error: machine type 'X8
Aaron,
Perhaps I have it wrong, but I think that the problem is that you are using
CMakeCache.txt that was created on a different machine.
CMakeCache.txt acts as a "configuration file" that overrides the registry,
environmental variables, and everything else that has a default value.
This allow
aaron_wri...@selinc.com wrote:
I've tried this on several machines and CMake always seems to think the
box is x64 even though it clearly says it's x86. I can fix the problem
by deleting CMakeCache.txt and running CMake again, which is weird. I'm
trying to automate the whole thing in a night b
I've tried this on several machines and CMake always seems to think the
box is x64 even though it clearly says it's x86. I can fix the problem by
deleting CMakeCache.txt and running CMake again, which is weird. I'm
trying to automate the whole thing in a night build script so this
behavior is n
I'm trying to use nmake to build a simple library, but cmake seems to have
a problem figuring out if my machine is x86 or x64. For example, I run,
cmake -G "NMake Makefiles" ..
and I get:
CMakeFiles\cmTryCompileExec.dir\testCCompiler.c.obj : fatal error LNK1112:
module machine type 'X86' confli
13 matches
Mail list logo
