<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div>On Mon, Oct 7, 2019, at 11:25 AM, Eric Noulard wrote:<br></div><blockquote type="cite" id="qt"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class="qt-gmail_quote"><div class="qt-gmail_attr" dir="ltr">Le lun. 7 oct. 2019 à 16:49, Cornelis Bockemühl <<a href="mailto:cornelis@bockemuehl.ch">cornelis@bockemuehl.ch</a>> a écrit :<br></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote">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?<br></blockquote><div><br></div><div>Nope I oversimplified.<br></div><div>This is not a bare copy, e.g. the runtime path (a.k.a. RPATH or RUNPATH) is updated as well.<br></div><div><br></div></div></div></blockquote><div><br></div><div>File permissions are also set according to what was specified in install() via <code class="docutils literal notranslate"><span class="pre">PERMISSIONS which can be different from the file permissions of the file in the build directory.</span></code><br></div><div><code class="docutils literal notranslate"><span class="pre">I think I saw that there was even a "make install/strip" feature that also stripped targets during installation.</span></code><br></div><div><br></div><div><code class="docutils literal notranslate"><span class="pre">I think that the word install is used consistently between GNU autotools and CMake:</span></code><br></div><div class="ds-list"><b>2. </b> <span class="hvr">(Computer</span> <span class="hvr">Science)</span> to <span class="hvr">transfer</span> <span class="hvr">(computer</span> <span class="hvr">software)</span> <span class="hvr">from</span> a <span class="hvr">distribution</span> <span class="hvr">file</span> to a <span class="hvr">permanent</span> <span class="hvr">location</span> on <span class="hvr">disk,</span> <span class="hvr">and</span> <span class="hvr">prepare</span> it <span class="hvr">for</span> <span class="hvr">its</span> <span class="hvr">particular</span> <span class="hvr">environment</span> <span class="hvr">and</span> <span class="hvr">application.</span><br></div><div class="ds-list"><br></div><div class="ds-list">It's that "prepare it for..." clause that makes it different from a straight up copy.<br></div><div class="ds-list"><br></div><div class="ds-list">I don't know what may be causing your issues. I do know that at least one person felt that CMake installation is too aggressive in that it is always installing files that it doesn't need to during the installation step.<br></div><div class="ds-list"><br></div><div><a href="https://stackoverflow.com/questions/58069372/does-cmake-always-evaluate-install-rules-even-for-up-to-date-targets#comment102540437_58069372">https://stackoverflow.com/questions/58069372/does-cmake-always-evaluate-install-rules-even-for-up-to-date-targets#comment102540437_58069372</a><br></div><div><br></div><div class="ds-list"><span class="hvr">--</span><br></div><div class="ds-list"><span class="hvr">Fred</span><br></div></body></html>