[Cmake] Another gripe about CMake

[Mathieu Mazerolle]

Hi Ken,
The issue about removing the modules directory was simply that it doesn't
need to be there, so I removed it, and I was suprised to see it crash. Of
course the solution is "don't do that" (Patient: "It hurts when I do this"
Doctor: "Then stop doing it").

The only cross-compiling issue for me is that WIN32 is defined when I'm
trying to build a makefile for another platform. CMake has no distinction
between host and target: It assumes that the host is the target, thus the
limitation of only being able to generate Unix makefiles with the Unix build
of CMake, and a variety of Windows make files with the Windows version.
Fixing this should be easy, and as Brad pointed out, would be a good
candidate for the next version. I would suggest de-coupling the host and
target settings internally in the code by removing the #ifdef WIN32 ||
!__CYGWIN__ stuff and making them if( hostPlatform == WIN32 ) or something.

I'll stop asking obnoxious questions now :) Overall, I'm very impressed with
CMake: it's head and shoulders over other non-commercial build tools, IMO.
It's a nice piece of work! Like I said before, my own solution for now will
probably be to change CMake and rebuild it to support the 1 or 2 minor
things I want changed. This is now my problem, not the list's.

Thanks to everyone for actively discussing this.
-- Matt

----- Original Message -----
From: "Ken Martin" <ken . martin at kitware . com>
To: "'Mathieu Mazerolle'" <mathieu_mazerolle at hotmail . com>; "'Brad King'"
<brad . king at kitware . com>
Cc: "'CMake'" <cmake at public . kitware . com>
Sent: Wednesday, December 11, 2002 3:19 PM
Subject: RE: [Cmake] Another gripe about CMake


> I think this discussion may be missing the point etc. I assume there is
> some real issue underlying this. I doubt you want to delete your modules
> directory because you are low on disk space and need the extra 10K. So
> there must be some other driver to this discussion. Could we focus on
> that instead? I'm assuming it is some cross compiler issue and some of
> the modules are not working right for you? Something like that maybe? In
> Cmake 1.4 I do not think the Modules were loaded by CMake. In Cmake
> 1.5/1.6 some of the modules are used by CMake for determining the
> SystemInfo etc.
>
> Thanks
> Ken
>