[CMake] Why does CMAKE_FIND_FRAMEWORK always default to FIRST ignoring command line definitions?

[Charlie Sharpsteen]

David Cole wrote
> 
> On Tue, May 29, 2012 at 2:33 PM, Charlie Sharpsteen <chuck@>wrote:
>> So, is there any reason `IF(NOT DEFINED CMAKE_FIND_FRAMEWORK)` cannot be
>> used in the platform file to protect command line arguments?
>>
> 
> 
> I can't think of a good reason not to use that construct.
> 
> Questions:
> Is there a homebrew build of CMake that you're using?
> Can you patch it with `IF(NOT DEFINED CMAKE_FIND_FRAMEWORK)` where
> appropriate?
> If you can, and you do, are there any noticeable ill effects? (Do all the
> CMake tests pass?)
> 
> If the answers to these questions are reasonable, then I'd take a patch
> that does what you want with respect to variables used in Darwin.cmake, no
> problem.
> 
> 
> Thanks,
> David
> 


Thanks for the reply David! I have submitted a patch to the CMake
bugtracker:

  http://public.kitware.com/Bug/view.php?id=13261

Building CMake with this patch produced no additional failures in the
testsuite. Building QGIS is now much improved by the ability to control the
priority given to Frameworks when satisfying dependencies.

-Charlie

--
View this message in context: http://cmake.3232098.n2.nabble.com/Why-does-CMAKE-FIND-FRAMEWORK-always-default-to-FIRST-ignoring-command-line-definitions-tp7521759p7580022.html
Sent from the CMake mailing list archive at Nabble.com.