MantisBT - CMake
View Issue Details
0012534CMakeCMakepublic2011-10-22 02:262016-06-10 14:31
Lars Viklund 
Kitware Robot 
normalfeatureN/A
closedmoved 
CMake 2.8.6 
 
0012534: Accumulate library paths from ld.so.conf
It was discussed on the list in January 2011 whether to add paths from /etc/ld.so.conf to the library search path, but no conclusion was made.

As Ubuntu 11.10 uses this functionality for rather common libraries (libGL.so), I've hacked up some rudimentary functionality for Platform/UnixPaths.cmake to traverse the includes in ld.so.conf and accumulate the paths there into CMAKE_SYSTEM_LIBRARY_PATH.

It's works-for-me grade code that probably needs better handling of comments, whitespace and missing entries.

This is needed eventually as ld.so.conf will not go away, and as you cannot enumerate all the locations all distros will put libraries in.
No tags attached.
txt ld.so.txt (742) 2011-10-22 02:26
https://public.kitware.com/Bug/file/4094/ld.so.txt
Issue History
2011-10-22 02:26Lars ViklundNew Issue
2011-10-22 02:26Lars ViklundFile Added: ld.so.txt
2011-10-22 02:30Lars ViklundNote Added: 0027612
2012-08-11 11:38David ColeStatusnew => backlog
2012-08-11 11:38David ColeNote Added: 0030317
2016-06-10 14:28Kitware RobotNote Added: 0041922
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
(0027612)
Lars Viklund   
2011-10-22 02:30   
I guess this should be under the Modules category and not CMake, but I don't seem to be able to change it.
(0030317)
David Cole   
2012-08-11 11:38   
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.
(0041922)
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.