> OK, I am pretty sure (99.9%) it is not actually using that compiler for the
> tests. The CMAKE_CXX_COMPILER value is not actually used by the visual
> studio IDE projects. However, that does seem to be some disturbing
> output I need to change the platform files so that the cl full path is
John Drescher wrote:
On Fri, Mar 20, 2009 at 5:42 PM, John Drescher wrote:
If you select "Visual Studio 8 2005" as a generator, it should not use VC6.
Please make sure you start with an empty binary directory, with no
CmakeCache.txt file.
I just created a new build tree selected vs2005 and
> If you select "Visual Studio 8 2005" as a generator, it should not use VC6.
> Please make sure you start with an empty binary directory, with no
> CmakeCache.txt file.
>
I just created a new build tree selected vs2005 and it still used the
vc6 compiler:
Check for working C compiler: C:/Program
John Drescher wrote:
But then with this setup cmake-2.6.3 is scanning my vc6 headers and
libs to generate vc2005 projects.
This has not caused me any problems but I am unsure if checks like
partial template specification are being used or is this part of cmake
not really used if I use the .sln
>>> But then with this setup cmake-2.6.3 is scanning my vc6 headers and
>>> libs to generate vc2005 projects.
>>>
>>
>> This has not caused me any problems but I am unsure if checks like
>> partial template specification are being used or is this part of cmake
>> not really used if I use the .sln a
John Drescher wrote:
On Fri, Mar 20, 2009 at 3:49 PM, John Drescher wrote:
If you use the IDE generators for CMake, you do not need to modify the
environment at all. It is only when using nmake or make, that you need an
environment that is setup to run the compiler. If you do want to use
nma
On Fri, Mar 20, 2009 at 3:49 PM, John Drescher wrote:
>> If you use the IDE generators for CMake, you do not need to modify the
>> environment at all. It is only when using nmake or make, that you need an
>> environment that is setup to run the compiler. If you do want to use
>> nmake, VS 2003
> If you use the IDE generators for CMake, you do not need to modify the
> environment at all. It is only when using nmake or make, that you need an
> environment that is setup to run the compiler. If you do want to use
> nmake, VS 2003 and above have command prompts that can be found in the
> "
John Drescher wrote:
Makes sense. So then I should be opening cmake-gui from the compiler's
command prompt instead of the shortcut on the desktop. Not a big deal
I am one to use the command prompt all the time windows or linux..
I'm not very familar with cmake-gui but I don't see another option
>> Makes sense. So then I should be opening cmake-gui from the compiler's
>> command prompt instead of the shortcut on the desktop. Not a big deal
>> I am one to use the command prompt all the time windows or linux..
>>
> I'm not very familar with cmake-gui but I don't see another option.
>
Thanks.
John Drescher schrieb:
On Fri, Mar 20, 2009 at 3:02 PM, Christian Ehrlicher
wrote:
John Drescher schrieb:
On my windows XP box, I have VC6, 2003, 2005 and 2008 installed and I
have selected VS2005 for the build however all the CMake checks are
happening for VC6. It does not seem to cause any h
John Drescher schrieb:
On my windows XP box, I have VC6, 2003, 2005 and 2008 installed and I
have selected VS2005 for the build however all the CMake checks are
happening for VC6. It does not seem to cause any harm but what about
header and library differences between the compilers? I mean all th
On my windows XP box, I have VC6, 2003, 2005 and 2008 installed and I
have selected VS2005 for the build however all the CMake checks are
happening for VC6. It does not seem to cause any harm but what about
header and library differences between the compilers? I mean all the
checks for stl ... are
13 matches
Mail list logo
