MantisBT - CMake
View Issue Details
0012003CMakeCMakepublic2011-03-22 20:052016-06-10 14:31
Nick Devenish 
Kitware Robot 
normalminoralways
closedmoved 
MacOS X10.6
CMake 2.8.4 
 
0012003: find_package fails but reports success with case in sensitive filesystems
When using find_package (i.e. boost) on the mac, you can have a situation where you use (note the package case):
find_package(boost COMPONENTS thread)

And do not get a failure, because the "FindBoost.cmake" file has been run, because of the insensitivity of filename reads of the mac filesystem. However, this file expects it's variables to all be set in the form "${Boost_FIND_COMPONENTS}" - but the differently cased "${boost_FIND_COMPONENTS}" are the ones passed through.

The outcome is that the package is incorrectly configured, but no warnings or errors are reported. I would have at least expected a warning, because I can't imagine this behaviour ever being desired.
On Mac, CMakeList.txt:

find_package(boost 1.34 COMPONENTS thread )
message("Boost_LIBRARIES: " ${Boost_LIBRARIES})
No tags attached.
Issue History
2011-03-22 20:05Nick DevenishNew Issue
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030245
2016-06-10 14:28Kitware RobotNote Added: 0041823
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030245)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041823)
Kitware Robot   
2016-06-10 14:28   
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.