Re: [CMake] option bug ?

2010-07-27 Thread Michael Hertling
On 07/26/2010 10:29 PM, Alexander Neundorf wrote: On Monday 12 July 2010, Michael Hertling wrote: On 07/07/2010 09:44 AM, Michael Wild wrote: On 7. Jul, 2010, at 9:32 , Michael Hertling wrote: On 07/03/2010 01:03 AM, Chris Hillery wrote: There's a slightly nicer work-around: Change project

Re: [CMake] option bug ?

2010-07-26 Thread Alexander Neundorf
On Monday 12 July 2010, Michael Hertling wrote: On 07/07/2010 09:44 AM, Michael Wild wrote: On 7. Jul, 2010, at 9:32 , Michael Hertling wrote: On 07/03/2010 01:03 AM, Chris Hillery wrote: There's a slightly nicer work-around: Change project A's CMakeLists to set PROJB_OPENCV_LINK as a

Re: [CMake] option bug ?

2010-07-12 Thread Michael Hertling
On 07/07/2010 09:44 AM, Michael Wild wrote: On 7. Jul, 2010, at 9:32 , Michael Hertling wrote: On 07/03/2010 01:03 AM, Chris Hillery wrote: There's a slightly nicer work-around: Change project A's CMakeLists to set PROJB_OPENCV_LINK as a cache variable, ie, SET(PROJB_OPENCV_LINK NO CACHE

Re: [CMake] option bug ?

2010-07-07 Thread Michael Hertling
On 07/03/2010 01:03 AM, Chris Hillery wrote: There's a slightly nicer work-around: Change project A's CMakeLists to set PROJB_OPENCV_LINK as a cache variable, ie, SET(PROJB_OPENCV_LINK NO CACHE BOOLEAN doc). I've tested it locally and it works the way you want it to. It seems that CMake

Re: [CMake] option bug ?

2010-07-07 Thread Chris Hillery
On Wed, Jul 7, 2010 at 12:32 AM, Michael Hertling mhertl...@online.dewrote: IMO, things aren't sooo bad. ;-) [100 lines of explanation of how SET() behaves in 6 different ways elided] I think you've just proven my point. Thanks! :) Ceej aka Chris Hillery

Re: [CMake] option bug ?

2010-07-07 Thread Michael Wild
On 7. Jul, 2010, at 9:32 , Michael Hertling wrote: On 07/03/2010 01:03 AM, Chris Hillery wrote: There's a slightly nicer work-around: Change project A's CMakeLists to set PROJB_OPENCV_LINK as a cache variable, ie, SET(PROJB_OPENCV_LINK NO CACHE BOOLEAN doc). I've tested it locally and it

Re: [CMake] option bug ?

2010-07-07 Thread Michael Hertling
On 07/07/2010 09:40 AM, Chris Hillery wrote: On Wed, Jul 7, 2010 at 12:32 AM, Michael Hertling mhertl...@online.dewrote: IMO, things aren't sooo bad. ;-) [100 lines of explanation of how SET() behaves in 6 different ways elided] I think you've just proven my point. Thanks! :)

Re: [CMake] option bug ?

2010-07-04 Thread Gaspard Bucher
Hi Chris, Thanks for the detailed information. SET( CACHE ...) is effectively a good workaround. Gaspard On Sat, Jul 3, 2010 at 1:03 AM, Chris Hillery chillery-cm...@lambda.nuwrote: There's a slightly nicer work-around: Change project A's CMakeLists to set PROJB_OPENCV_LINK as a cache

Re: [CMake] option bug ?

2010-07-02 Thread Chris Hillery
There's a slightly nicer work-around: Change project A's CMakeLists to set PROJB_OPENCV_LINK as a cache variable, ie, SET(PROJB_OPENCV_LINK NO CACHE BOOLEAN doc). I've tested it locally and it works the way you want it to. It seems that CMake divides the world of variables into two classes: cache