MantisBT - CMake
View Issue Details
0013244CMakeCMakepublic2012-05-23 05:032016-06-10 14:31
dam 
Philip Lowman 
highminoralways
closedmoved 
CMake 2.8.8 
 
0013244: components are append to Boost_LIBRARIES
When using FindBoost in the same CMakeLists.txt and with different components, the variable Boost_LIBRARIES contains the union of the components.

I think that Boost_LIBRARIES variable should be cleared when each time find_package(Boost ...) is invoked, or perhaps the doc should mentioned this behavior.
cmake_minimum_required(VERSION 2.8 FATAL_ERROR)

project(foo)

find_package(Boost COMPONENTS thread)
message("boost libs: ${Boost_LIBRARIES}")

find_package(Boost COMPONENTS date_time)
message("\nboost libs: ${Boost_LIBRARIES}")

# the result is:
# boost libs: /usr/lib/libboost_thread-mt.so
#
# boost libs: /usr/lib/libboost_thread-mt.so;/usr/lib/libboost_date_time-mt.so

# but I think it should be:
# boost libs: /usr/lib/libboost_date_time-mt.so
No tags attached.
Issue History
2012-05-23 05:03damNew Issue
2012-05-24 08:19damNote Added: 0029554
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030425
2012-08-18 15:29Philip LowmanStatusbacklog => assigned
2012-08-18 15:29Philip LowmanAssigned To => Philip Lowman
2016-06-10 14:28Kitware RobotNote Added: 0042053
2016-06-10 14:28Kitware RobotStatusassigned => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0029554)
dam   
2012-05-24 08:19   
Please close this bug because it is a misunderstanding about how cmake works.
(0030425)
David Cole   
2012-08-11 21:35   
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.
(0042053)
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.