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
Le mar. 8 oct. 2019 à 12:52, Cornelis Bockemühl 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
On Mon, Oct 7, 2019, at 11:25 AM, Eric Noulard wrote:
>
>
> Le lun. 7 oct. 2019 à 16:49, Cornelis Bockemühl a
> écrit :
>> Thanks to both you and J Decker: I would say that this is still the part
>> that I understood! So basically the word "install" in cmake language could
>> be replaced by
Le lun. 7 oct. 2019 à 16:49, Cornelis Bockemühl a
écrit :
> Thanks to both you and J Decker: I would say that this is still the part
> that I understood! So basically the word "install" in cmake language could
> be replaced by "copy" more or less in common human language - right?
>
Nope I
I'll try some answer.
In order to illustrate my words have a look at this figure:
https://raw.githubusercontent.com/dev-cafe/cmake-cookbook/master/figures/cmake-times/cmake-times.jpg
1) When cmake "runs" (both cmake and generation times) you get your build
tree configured and populated
2) At
Install steps are done with `cmake --build . --target install` (or
--target INSTALL on some generators)
It's done after the build is complete, if the build step fails, it will not
install. (Install depends on build automatically)
The install steps can also be used by --target package - which
Constantly I am stumbling over the word "install" in the context of cmake
scripts - while it is pretty clear that the word cannot mean what nowadays
people would understand by that term! But even reading the docs forwards and
backwards, studying examples and some generic cmake tutorials I
