with absolutely no joy.
Whenever I try to build a solution for my project, the cmake test for
the fortran compiler generates a solution file for VS 8 that can't be
processed by VS 8.
So far I've pissed away about 2/3 of a day between trying to rebuild
CMake (I found a reference to something
I am using the Visual Studio 8 2005 generator with cmake and intel fortran
compiler.
I load the solution in Visual studio and when I compile I get the following
error
Building Fortran object test.obj
C:\Users\Alin M Elena\testFortran\test.f90(2) : Error: Error in opening the
compiled module
I'm having some trouble getting a clean way to set the warning level
in my projects with Visual Studio 2005.
When I try this
SET(CMAKE_C_WARNING_LEVEL 4)
SET(CMAKE_CXX_WARNING_LEVEL 4)
It seems to be ignored because the project files still have the
warning level set to 3. I only want to turn
I'm having some trouble getting a clean way to set the warning level
in my projects with Visual Studio 2005.
When I try this
SET(CMAKE_C_WARNING_LEVEL 4)
SET(CMAKE_CXX_WARNING_LEVEL 4)
It seems to be ignored because the project files still have the
warning level set to 3. I only want to turn up
Hi,
If I tell CMake to generate Visual Studio 8 project files, CMake
requires that the right cl.exe can be found in PATH. More
specifically, if the wrong cl.exe is found in PATH (say from Visual
Studio 7), then CMake just pukes with some strange error.
This confuses several of my users (who
Jesper Eskilson wrote:
Hi,
If I tell CMake to generate Visual Studio 8 project files, CMake
requires that the right cl.exe can be found in PATH. More
specifically, if the wrong cl.exe is found in PATH (say from Visual
Studio 7), then CMake just pukes with some strange error.
This confuses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to build cmake from cvs on windows with visual studio 8. I'm
using the NMake Makefiles generator. Apart from a lot of warnings
(deprecated functions), cmake was built successfully and I can run cmake
from there. The problem arises after
