Re: [CMake] unset() command

On Wed, Sep 3, 2008 at 2:00 PM, Alexander Neundorf <[EMAIL PROTECTED]>wrote: > On Tuesday 26 August 2008, Philip Lowman wrote: > > On Mon, Aug 25, 2008 at 10:31 AM, Fernando Cacciola < > > > > [EMAIL PROTECTED]> wrote: > > > And while you are it.. I currently use: set(var) to read the value > > >

Re: [CMake] unset() command

On Tuesday 26 August 2008, Philip Lowman wrote: > On Mon, Aug 25, 2008 at 10:31 AM, Fernando Cacciola < > > [EMAIL PROTECTED]> wrote: > > And while you are it.. I currently use: set(var) to read the value > > back from the cache (very usefull somtimes), but this is undocumented and > > extremely no

Re: [CMake] unset() command

On Mon, Aug 25, 2008 at 10:31 AM, Fernando Cacciola < [EMAIL PROTECTED]> wrote: > And while you are it.. I currently use: set(var) to read the value > back from the cache (very usefull somtimes), but this is undocumented and > extremely none-obvous, so, can we have a "fetch(var)" as well? > > Shou

Re: [CMake] unset() command

Brad King wrote: Philip Lowman wrote: On Wed, Aug 20, 2008 at 10:54 AM, Brad King <[EMAIL PROTECTED] > wrote: The "set" command already supports unsetting: set(FOO xyz) set(FOO) # unsets if(DEFINED FOO) message("This message does not appear.")

Re: [CMake] unset() command

Alan W. Irwin wrote: On 2008-08-20 14:07-0400 Brad King wrote: Alan W. Irwin wrote: if(FOO) still gives different results depending on whether there has ever been a set command executed for the variable. Really? Can you provide example code demonstrating this? OOPS. Sorry for that noise

Re: [CMake] unset() command

Philip Lowman wrote: > On Thu, Aug 21, 2008 at 9:01 AM, Brad King <[EMAIL PROTECTED] > > wrote: > However, this: > > unset(MY_CACHE_VARIABLE) > > should not remove the cache entry. It should only unset the CMake > variable. In order to remove the cache

Re: [CMake] unset() command

On Thu, Aug 21, 2008 at 9:01 AM, Brad King <[EMAIL PROTECTED]> wrote: > Philip Lowman wrote: > > On Wed, Aug 20, 2008 at 10:54 AM, Brad King <[EMAIL PROTECTED] > > > wrote: > > > > The "set" command already supports unsetting: > > > > set(FOO xyz) > > set(FOO)

Re: [CMake] unset() command

Philip Lowman wrote: > On Wed, Aug 20, 2008 at 10:54 AM, Brad King <[EMAIL PROTECTED] > > wrote: > > The "set" command already supports unsetting: > > set(FOO xyz) > set(FOO) # unsets > if(DEFINED FOO) > message("This message does not appear.") >

Re: [CMake] unset() command

On Wed, Aug 20, 2008 at 10:46 AM, Mike Jackson <[EMAIL PROTECTED]> wrote: > Is that more what you were after? > > The source for these examples can be found at: > > http://titanium.imts.us/viewvc/Task_7/MXADataModel/Resources/ > > Look for MXAFindExpat.cmake and MXAAdjustLibVars.cmake > > Does tha

Re: [CMake] unset() command

On Wed, Aug 20, 2008 at 10:54 AM, Brad King <[EMAIL PROTECTED]> wrote: > The "set" command already supports unsetting: > > set(FOO xyz) > set(FOO) # unsets > if(DEFINED FOO) > message("This message does not appear.") > endif(DEFINED FOO) > > I think it should just be fixed for CACHE and ENV varia

Re: [CMake] unset() command

Alan W. Irwin wrote: > However, I would like to point out there is still a documentation concern > here. Yes, I will look at updating the documentation of the set() and if() commands to address this. -Brad ___ CMake mailing list CMake@cmake.org http://w

Re: [CMake] unset() command

On 2008-08-20 14:07-0400 Brad King wrote: Alan W. Irwin wrote: if(FOO) still gives different results depending on whether there has ever been a set command executed for the variable. Really? Can you provide example code demonstrating this? OOPS. Sorry for that noise. However, I would li

Re: [CMake] unset() command

Alan W. Irwin wrote: > if(FOO) > > still gives different results depending on whether there has ever been a > set command executed for the variable. Really? Can you provide example code demonstrating this? -Brad ___ CMake mailing list CMake@cmake.org

Re: [CMake] unset() command

On 2008-08-20 10:54-0400 Brad King wrote: Philip Lowman wrote: So I submitted a patch to add a new unset() command to CMake. The command will unset normal or cache variables (causing them to become undefined). The command also supports unsetting environment variables, in case anyone has to do

Re: [CMake] unset() command

Philip Lowman wrote: > So I submitted a patch to add a new unset() command to CMake. The > command will unset normal or cache variables (causing them to become > undefined). The command also supports unsetting environment variables, > in case anyone has to do that. > > The primary use case that

Re: [CMake] unset() command

Philip Lowman wrote: > So I submitted a patch to add a new unset() command to CMake. The > command will unset normal or cache variables (causing them to become > undefined). The command also supports unsetting environment variables, > in case anyone has to do that. > > The primary use case that

Re: [CMake] unset() command

If I am understanding correctly, you are looking for a debug version of a library. If you can not find that library, then you default to using the non-debug version of the library? If that is the case then there are some CMake macros that might help. I grabbed one from either the FindQt4 or

[CMake] unset() command

So I submitted a patch to add a new unset() command to CMake. The command will unset normal or cache variables (causing them to become undefined). The command also supports unsetting environment variables, in case anyone has to do that. The primary use case that drove me to implement this was thi