Re: [CMake] How to get around a CACHE problem?

2007-08-06 Thread Eric Noulard
2007/8/6, Christian Convey <[EMAIL PROTECTED]>: > > but the CMake macro writer may want to SET value as a GUESSED. > > > > SET(VAR [VALUE] [CACHE TYPE DOCSTRING [FORCE]] [GUESSED]) > > > > Do you think this proposition deserve a feature request? > > > > I think something about CMake needs rethinkin

Re: [CMake] How to get around a CACHE problem?

2007-08-06 Thread Christian Convey
On 8/6/07, Eric Noulard <[EMAIL PROTECTED]> wrote: > 2007/8/5, Christian Convey <[EMAIL PROTECTED]>: > [...] > If I summarize I think a VAR may be tested with > > IF (DEFINED VAR) --> if true VAR is defined with a value > IF (CACHED VAR) --> if true VAR value comes from CACHE > IF (PROVIDED VAR

Re: [CMake] How to get around a CACHE problem?

2007-08-05 Thread Eric Noulard
2007/8/5, Christian Convey <[EMAIL PROTECTED]>: [...] summary: SET (... CACHE ...) not set after a FATAL_ERROR. > > My work-around for now is to do it like this: > > SET( LIBRARY_OUTPUT_PATH ${MOOSBIN} CACHE PATH > "Output directory for the MOOS libraries" ) > > IF("${LIBRARY_OUTPUT_PATH}

[CMake] How to get around a CACHE problem?

2007-08-05 Thread Christian Convey
In this project I'm working on, the user is supposed to be able to specify where the project's programs and libraries are placed when they're built. So the top-level lists SET( LIBRARY_OUTPUT_PATH ${MOOSBIN} CACHE PATH "Output directory for the MOOS libraries" ) But I have a problem: If so