[Cmake] Small suggestion for future versions of cmake

[Ken Martin]

I agree. Some of these files can be moved into CMakeTmp. We may need a
subdir under CMakeTmp for TryCompile output, but I still think it is
best to put what we can into a subdir and not clutter the build tree too
much.

-----Original Message-----
From: cmake-admin at public.kitware.com
[mailto:cmake-admin at public.kitware.com] On Behalf Of Thomas Deschamps
Sent: Wednesday, December 18, 2002 9:58 PM
To: cmake at public.kitware.com
Subject: [Cmake] Small suggestion for future versions of cmake

Hi cmake users and developers,

I am using the CVS version of cmake.

I am wondering why this CMakeTmp directory is used for, since it is
empty.

A suggestion: Why don't someone put all C*Make* files into this 
directory (except CMakeList.txt)?

It will make less garbage when using cvs on our personal directories, 
like now for my big project toto:

Before
 > cvs diff toto
? CMakeCCompiler.cmake
? CMakeCXXCompiler.cmake
? CMakeCache.txt
? CMakeError.log
? CMakeSystem.cmake
? CMakeTmp
? Makefile
? cmake.check_cache
? cmake.check_depends
? cmake.depends
cvs server: Diffing .
...

After (eventually)
 > cvs diff toto
? CMakeTmp
? Makefile
cvs server: Diffing .
...

Notice that CMakeList.txt belongs to the cvs repository.
And this is for only one repository (For vtk(http://www.vtk.org) for 
example the output is really bigger).

But it is just a suggestion.
Anyway, I am a very happy cmake user.
Except a little pb: if I erase CMakeCache.txt, then cmake will produce 
the error
CMake Error: The selected VTK was built with "g++", but the current 
compiler is "c++".  Please set CMAKE_CXX_COMPILER to "g++".
But in my CMakeList.txt, there is one line saying
SET( CMAKE_CXX_COMPILER "g++" )
Strange isn't it?

Thomas

_______________________________________________
Cmake mailing list
Cmake at public.kitware.com
http://public.kitware.com/mailman/listinfo/cmake