View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0014810 | CMake | CMake | public | 2014-03-15 22:08 | 2016-06-10 14:31 | ||||
Reporter | Nikolaus Demmel | ||||||||
Assigned To | Kitware Robot | ||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | Darwin | OS | OS X | OS Version | 10.9 | ||||
Product Version | CMake 2.8.12.1 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0014810: Make CMakeFindFrameworks module configurable | ||||||||
Description | This 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. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | ||||||
|
Relationships |
Notes | |
(0035415) Brad King (manager) 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 (reporter) 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 (manager) 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 (administrator) 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. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2014-03-15 22:08 | Nikolaus Demmel | New Issue | |
2014-03-17 08:58 | Brad King | Relationship added | related to 0014809 |
2014-03-17 08:59 | Brad King | Note Added: 0035415 | |
2014-04-02 06:39 | Nikolaus Demmel | Note Added: 0035619 | |
2014-04-02 08:33 | Brad King | Note Added: 0035620 | |
2016-06-10 14:29 | Kitware Robot | Note Added: 0042508 | |
2016-06-10 14:29 | Kitware Robot | Status | new => resolved |
2016-06-10 14:29 | Kitware Robot | Resolution | open => moved |
2016-06-10 14:29 | Kitware Robot | Assigned To | => Kitware Robot |
2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |