Re: [cmake-developers] How to handle package Config.cmake files with dependencies ?

2012-03-07 Thread Michael Hertling
On 02/27/2012 10:05 PM, Brad King wrote: On 2/27/2012 3:37 PM, Michael Wild wrote: On 02/27/2012 09:15 PM, Alexander Neundorf wrote: When the FooConfig.cmake has been found, Foo_FOUND is set to TRUE: // Set a variable marking whether the package was found. std::string foundVar =

Re: [cmake-developers] How to handle package Config.cmake files with dependencies ?

2012-03-07 Thread Michael Hertling
On 02/27/2012 09:15 PM, Alexander Neundorf wrote: Hi, I think find_package in Config mode might still need some more work. When the FooConfig.cmake has been found, Foo_FOUND is set to TRUE: // Set a variable marking whether the package was found. std::string foundVar = this-Name;

Re: [cmake-developers] How to handle package Config.cmake files with dependencies ?

2012-03-07 Thread Brad King
On 3/7/2012 9:49 AM, Michael Hertling wrote: been found, but in module mode, AFAIK, it's set to Foo_DIR-NOTFOUND even if a find module has succeeded The Foo_DIR variable is not set or added to the cache at all if a FindFoo module is loaded regardless of whether it succeeds. It is only if no

Re: [cmake-developers] Ninja windows

2012-03-07 Thread David Cole
On Wed, Mar 7, 2012 at 5:24 PM, David Cole david.c...@kitware.com wrote: On Wed, Mar 7, 2012 at 5:10 PM, Bill Hoffman bill.hoff...@kitware.com wrote: On 3/6/2012 6:17 PM, Peter Kümmel wrote: The following tests FAILED: 78 - CustomCommandWorkingDirectory (Failed) 80 - BuildDepends (Failed)

[cmake-developers] [CMake 0013027]: Annoying dialog box repeatedly displayed while configure step

2012-03-07 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13027 == Reported By:Dhanannjay Djay Deo Assigned To:

Re: [cmake-developers] Ninja windows

2012-03-07 Thread Bill Hoffman
On 3/7/2012 5:24 PM, David Cole wrote: That might be fixed just now (perhaps) by stuff that I merged into 'next' this afternoon. Try with the very latest next of CMake. (One of the commits from Peter K. had not yet been merged into next and it dealt with directory creation...) That fixed it.