The following issue has been SUBMITTED. ====================================================================== http://cmake.org/Bug/view.php?id=13233 ====================================================================== Reported By: Mathieu Malaterre Assigned To: ====================================================================== Project: CMake Issue ID: 13233 Category: CMake Reproducibility: have not tried Severity: minor Priority: normal Status: new ====================================================================== Date Submitted: 2012-05-17 08:44 EDT Last Modified: 2012-05-17 08:44 EDT ====================================================================== Summary: add new behavior for find_library Description: Quoting Brad's suggestion:
CMake's design assumes that the dependencies don't move after a project is built. If one of VTK's dependencies is rebuilt and puts a library in a new location, VTK could be rebuilt to know about the new location. I guess Debian's packages can be rebuilt without rebuilding all their dependents so long as the ABI is compatible. This is necessary for a sane update path for clients because otherwise if one low-level library is rebuilt for a bugfix then the entire system would have to be updated. A solution on the CMake side would be to (optionally) change the behavior of find_library. Currently it reports the full path to a library, but when that full path is inside an implicit linker search path the generated link line ends up with the -l form anyway. We could teach find_library to optionally report the library by only its name if the full path found is in an implicit search path. If the behavior were controlled by a global setting then that setting could simply be added as a -D argument in Debian package build rules. Additional Information: ref: http://bugs.debian.org/672729#27 ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2012-05-17 08:44 Mathieu MalaterreNew Issue ====================================================================== -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
