[cmake-developers] [CMake 0015966]: BundleUtilities unconditionally removes RPATH in copy_resolved_item_into_bundle

Mantis Bug Tracker mantis at public.kitware.com
Wed Feb 10 08:53:59 EST 2016


The following issue has been SUBMITTED. 
====================================================================== 
https://cmake.org/Bug/view.php?id=15966 
====================================================================== 
Reported By:                Florian Apolloner
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   15966
Category:                   CCMake
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2016-02-10 08:53 EST
Last Modified:              2016-02-10 08:53 EST
====================================================================== 
Summary:                    BundleUtilities unconditionally removes RPATH in
copy_resolved_item_into_bundle
Description: 
copy_resolved_item_into_bundle always removes the RPATH for libraries copied
into the bundle:
https://github.com/Kitware/CMake/blob/0def7e6e70d809958cb605e93dbe3d02baf05265/Modules/BundleUtilities.cmake#L625


This is often fine, but if your libraries depend on other libraries which are
not available on the system, this will prevent the from getting found.

In my case it was app -> libQt5Core.so.5 -> libicu.so whereas libQt5Core.so.5
from the precompiled SDK has $ORIGIN as RPATH since libicu is shipped along with
it.

Could be just drop that check or make it configurable? 
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2016-02-10 08:53 Florian ApollonerNew Issue                                    
======================================================================



More information about the cmake-developers mailing list