On Fri, Dec 28, 2012 at 3:29 PM, Rolf Eike Beer wrote:
> Changing the compiler usually will not work anyway. That's why we have
> separate build trees: wipe the whole thing and start again.
>
Yes, I have a habit of runnning
rm -rf * && cmake -DNEW_OPTIONS ..
because changing cache variables (e
Jed Brown wrote:
> On Fri, Dec 28, 2012 at 2:52 PM, Rolf Eike Beer wrote:
> > Don't specify the compiler like this:
> >
> > CC=clang cmake .
>
> I'm not looking for a work-around [*], I'm looking for the problem to be
> fixed so it stops blowing up in users' faces. The fact is that
> (a) -DCMAKE_C
On Fri, Dec 28, 2012 at 2:52 PM, Rolf Eike Beer wrote:
> Don't specify the compiler like this:
>
> CC=clang cmake .
>
I'm not looking for a work-around [*], I'm looking for the problem to be
fixed so it stops blowing up in users' faces. The fact is that
(a) -DCMAKE_C_COMPILER is an established a
Jed Brown wrote:
> $ echo 'project (Test C)' > CMakeLists.txt
> $ cmake -DCMAKE_C_COMPILER:FILEPATH=clang .
> -- The C compiler identification is Clang 3.1.0
> -- Check for working C compiler: /usr/bin/clang
> -- Check for working C compiler: /usr/bin/clang -- works
> -- Detecting C compiler ABI i
On 2012-12-28 14:56, Jed Brown wrote:
$ echo 'project (Test C)' > CMakeLists.txt
$ cmake -DCMAKE_C_COMPILER:FILEPATH=clang .
-- The C compiler identification is Clang 3.1.0
-- Check for working C compiler: /usr/bin/clang
-- Check for working C compiler: /usr/bin/clang -- works
-- Detecting C com
$ echo 'project (Test C)' > CMakeLists.txt
$ cmake -DCMAKE_C_COMPILER:FILEPATH=clang .
-- The C compiler identification is Clang 3.1.0
-- Check for working C compiler: /usr/bin/clang
-- Check for working C compiler: /usr/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler A
