MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013295CMakeCMakepublic2012-06-12 18:132016-06-10 14:31
ReporterSune Vuorela 
Assigned ToKitware Robot 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformLinuxOSDebianOS Versionunstable
Product VersionCMake 2.8.8 
Target VersionFixed in Version 
Summary0013295: find_package looks in wrong order of paths
DescriptionOn my system, I have among others
/usr/lib/libgettextpo.a
/usr/lib/x86_64-linux-gnu/libgettextpo.so

trying to do a find_library(GETTEXTPO_LIBRARY NAMES gettextpo)
gives me the static library, while I expected it to find the dynamic library.
Steps To Reproducetrying to build kdesdk master (or 4.9 prereleases) fails to build when trying to link libgettextpo.a into a shared library
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-06-12 18:13Sune VuorelaNew Issue
2012-06-12 18:14Sune VuorelaNote Added: 0029673
2012-06-13 08:20Brad KingNote Added: 0029675
2012-08-11 21:42David ColeStatusnew => backlog
2012-08-11 21:42David ColeNote Added: 0030437
2016-06-10 14:28Kitware RobotNote Added: 0042064
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
(0029673)
Sune Vuorela   
2012-06-12 18:14   
of course, building by 'hand' using -lgettextpo picks up the dynamic version in /usr/lib/TRIPLET/
(0029675)
Brad King   
2012-06-13 08:20   
What is the output of these commands:

 $ grep LIBRARY_ARCHITECTURE CMakeFiles/CMake*Compiler.cmake
 $ grep IMPLICIT_LINK CMakeFiles/CMake*Compiler.cmake

? When you later do

  target_link_libraries(my_exe_or_shared_lib ${GETTEXTPO_LIBRARY})

what does the final link line have?
(0030437)
David Cole   
2012-08-11 21:42   
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.
(0042064)
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.