MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014810CMakeCMakepublic2014-03-15 22:082016-06-10 14:31
ReporterNikolaus Demmel 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformDarwinOSOS XOS Version10.9
Product VersionCMake 2.8.12.1 
Target VersionFixed in Version 
Summary0014810: Make CMakeFindFrameworks module configurable
DescriptionThis issue is related to the recently reported: http://www.itk.org/Bug/view.php?id=14809 [^]

The list of paths to be searched in CMakeFindFrameworks is hardcoded. There should be a way to globally extend it. For example homebrew is commonly used to install unix software on OS X these days. Any frameworks installed through homebrew will be in `/usr/local/Library/Frameworks` and thus be missed by CMake.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0014809closed Matt McCormick FindPythonLibs issue (at least on OS X). Should it use sysconfig? 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-03-15 22:08Nikolaus DemmelNew Issue
2014-03-17 08:58Brad KingRelationship addedrelated to 0014809
2014-03-17 08:59Brad KingNote Added: 0035415
2014-04-02 06:39Nikolaus DemmelNote Added: 0035619
2014-04-02 08:33Brad KingNote Added: 0035620
2016-06-10 14:29Kitware RobotNote Added: 0042508
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0035415)
Brad King   
2014-03-17 08:59   
The CMakeFindFrameworks module pre-dated the find_library and related command support for searching in frameworks automatically. Its use in FindTCL and FindPtyhonLibs is historical and should be refactored. The find_* commands are very configurable and will search more framework paths than the module.
(0035619)
Nikolaus Demmel   
2014-04-02 06:39   
It was not quite transparent to me that the mechanism looking for Frameworks for the built-in find_* commands is different from the CMakeFindFrameworks module.

So the resolution -- as you suggest -- would be remove the use of CMakeFindFrameworks in all existing modules and mabe add some clear hint in the code and documentation of CMakeFindFrameworks that it is a historical module and superseeded by the mechanism in the find_* commands?
(0035620)
Brad King   
2014-04-02 08:33   
Re 0014810:0035619: Yes, CMakeFindFrameworks should not be used anymore. See also 0014809 for its use in FindPythonLibs.

The find_* commands are very configurable.
(0042508)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.