[cmake-developers] fix-OSX-bundle-rpaths-and-Qt5 topic

[Clinton Stimpson]

On Thursday, October 09, 2014 10:27:32 AM Brad King wrote:
> On 10/09/2014 10:16 AM, clinton at elemtech.com wrote:
> > When I do the same message(), I don't see deletion of rpaths which do not
> > exist.
> I see them for libshared and libshared2 which have SKIP_BUILD_RPATH.
> 
> > But, I'm wondering if INSTALL_RPATH should only be effective on OS X
> > if MACOSX_RPATH is set.
> > Currently MACOSX_RPATH determines whether a target uses @rpath for
> > its id, which can result in rpaths for a consumer.
> > In other words, whether a target has rpaths is determined by the
> > use of @rpath in its dependencies.
> > What do you think about the case of INSTALL_RPATH?
> 
> If any dependencies have @rpath then the RPATH of a target is
> meaningful, and INSTALL_RPATH is how the actual search paths
> listed in the RPATH are to be set.  INSTALL_RPATH is orthogonal
> to MACOSX_RPATH.  The affect different fields of their target.
> 

Another justification for that is if a target does not link to any libraries 
with an @rpath id, it is still useful to have an rpath to support 
dlopen("@rpath/somelib").

Thanks,
Clint