[Cmake] Another gripe about CMake

[Mathieu Mazerolle]

We use gcc without /usr/lib/gcc-lib: it turns out that GCC does work just
fine without that directory if you built it without shared libs and tell it
not to use standard libs+headers. Since we're developing for an embedded
platform, this is our actual situation.

I'm not sure if I understand what you mean when you say Cmake always needs
the module directory to work: Ken said modules are optional, so in what way
is the modules directory alays required no matter what?

-- Matt

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


> > I guess what I was trying to say was: "cmake should not crash if I
> > decide to delete the Modules directory". If I delete math.h, and don't
> > use it, gcc doesn't crash: the equivalent is not true with CMake in your
> > example.
>
> Try removing /usr/lib/gcc-lib and see if g++ still runs correctly.  I
> agree CMake shouldn't crash, but it always needs its module directory to
> work.
>
> -Brad
>
> _______________________________________________
> Cmake mailing list
> Cmake at public.kitware.com
> http://public.kitware.com/mailman/listinfo/cmake
>