[CMake] ?= Looking for an explanation: What exactly means "install" in cmake language

[cornelis]

Thanks for that hint! But for me the RPATH stuff is only a supplement, because in   the context of a Paraview based project, most of my shared libs are plugins, and for these PV comes with its own mechanism to find them.
  

  
But then all the more important is the question about actually copying the libs - to a specific location where the plugin finding procedure finds them!
  

  
Regards, Cornelis
  

  
  

  
  
  
  
  
>   
> On 08.10.2019 at 13:10, Eric Noulard  <eric.noulard at gmail.com>  wrote:
>   
>   
>   
>
>   
>   
>   
> Le   mar. 8 oct. 2019 à   12:52, Cornelis Bockemühl  <cornelis at bockemuehl.ch>  a écrit   :
>   
> >  One more finding: the "magic" that QtCreator does to start example also without any additional fiddling with the RPATH: it already contains a RUNPATH, and this points to the shared library libshlibbu.so in it's build tree location, not in the installed location - and the same with libshlibbu.so.
> >   
> >  And the "install" process indeed handles the RPATH/RUNPATH: it simply removes it!
> >   
> >  Meaning: it I want to end up what I initially expected, I have to do two additional things manually (or maybe there is an automatic way??):
> >   
> >  1) copy the shared libraries to the "example" install directory tree
> >  2) add some RPATH or RUNPATH setting to all the binaries that need it
>   
>
>   
> You should read how RPATH handling is done with CMake.
>   
> see:   https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/RPATH-handling
>   
>
>   
> As you already noted there is a build RPATH and an install RPATH.
>   
> The first is used when building the second replace the first after installation takes place.
>   
>   
>
>  --
>   
>   
>   
>   
>   
> Eric
>             
     
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20191008/7b537935/attachment-0001.html>