On Fri, Feb 11, 2011 at 6:00 AM, David Cole wrote:
> To use "--debug-trycompile" effectively, you have to:
>
> - run *without* "--debug-trycompile" all the way through once to establish
> all the cache settings
> - remove/delete the *single* cache entry whose try_compile result you are
> trying t
To use "--debug-trycompile" effectively, you have to:
- run *without* "--debug-trycompile" all the way through once to establish
all the cache settings
- remove/delete the *single* cache entry whose try_compile result you are
trying to debug
- run again with "--debug-trycompile"
The reasons are:
On Fri, Feb 11, 2011 at 1:47 AM, Michael Wild wrote:
> On 02/11/2011 04:30 AM, Jack Poulson wrote:
> > This is occurring with CMake 2.8.3 on OSX for several different
> > check_function_exists calls. Is this expected behavior?
> >
> > Jack
>
> Seriously, we're going to need some more information
On 02/11/2011 04:30 AM, Jack Poulson wrote:
> This is occurring with CMake 2.8.3 on OSX for several different
> check_function_exists calls. Is this expected behavior?
>
> Jack
Seriously, we're going to need some more information than just "I get
false positives"...
Michael
_
This is occurring with CMake 2.8.3 on OSX for several different
check_function_exists calls. Is this expected behavior?
Jack
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
P