Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-09-06 Thread Alexander Neundorf
On Saturday 05 September 2009, Alexander Neundorf wrote: On Sunday 28 June 2009, Alexander Neundorf wrote: On Tuesday 12 May 2009, Philip Lowman wrote: On Mon, May 11, 2009 at 4:53 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Monday 11 May 2009, Bill Hoffman

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-09-05 Thread Alexander Neundorf
On Sunday 28 June 2009, Alexander Neundorf wrote: On Tuesday 12 May 2009, Philip Lowman wrote: On Mon, May 11, 2009 at 4:53 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Monday 11 May 2009, Bill Hoffman wrote: Alexander Neundorf wrote: On Monday 11 May 2009,

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-06-28 Thread Alexander Neundorf
On Tuesday 12 May 2009, Philip Lowman wrote: On Mon, May 11, 2009 at 4:53 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Monday 11 May 2009, Bill Hoffman wrote: Alexander Neundorf wrote: On Monday 11 May 2009, Bill Hoffman wrote: So, CMake has done what it does now

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-05-11 Thread Bill Hoffman
So, CMake has done what it does now from the start. There was a short period of time when it did not, and that was when a re-write was done, and it quickly broke some existing projects. Here is the thread: http://www.cmake.org/pipermail/cmake/2007-March/013204.html I think the rule should

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-05-11 Thread Brad King
Bill Hoffman wrote: So, CMake has done what it does now from the start. There was a short period of time when it did not, and that was when a re-write was done, and it quickly broke some existing projects. Here is the thread: http://www.cmake.org/pipermail/cmake/2007-March/013204.html I

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-05-11 Thread Alexander Neundorf
On Monday 11 May 2009, Bill Hoffman wrote: So, CMake has done what it does now from the start. There was a short period of time when it did not, and that was when a re-write was done, and it quickly broke some existing projects. Here is the thread: Yes, I can imagine that. Still the current

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-05-11 Thread Bill Hoffman
Alexander Neundorf wrote: On Monday 11 May 2009, Bill Hoffman wrote: So, CMake has done what it does now from the start. There was a short period of time when it did not, and that was when a re-write was done, and it quickly broke some existing projects. Here is the thread: Yes, I can

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-05-11 Thread Alexander Neundorf
On Monday 11 May 2009, Bill Hoffman wrote: Alexander Neundorf wrote: On Monday 11 May 2009, Bill Hoffman wrote: So, CMake has done what it does now from the start. There was a short period of time when it did not, and that was when a re-write was done, and it quickly broke some existing

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-05-11 Thread Philip Lowman
On Mon, May 11, 2009 at 4:53 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Monday 11 May 2009, Bill Hoffman wrote: Alexander Neundorf wrote: On Monday 11 May 2009, Bill Hoffman wrote: So, CMake has done what it does now from the start. There was a short period of time

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

2009-05-10 Thread Philip Lowman
On Sun, May 10, 2009 at 5:08 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: The attached patch (against current cvs HEAD) changes the behaviour of set( CACHE) and option() slightly. Until now it behaves like this: if a variable FOO is set to a value, and then set FOO to a value in