<div dir="ltr">Is it not feasible to just let the build system do whatever it is going to and use "chrpath" or "patchelf" to change the rpath after-the-fact?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 9, 2019 at 11:48 AM DIXON, MARK C. <<a href="mailto:mark.c.dixon@durham.ac.uk">mark.c.dixon@durham.ac.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, 9 Oct 2019, Craig Scott wrote:<br>
...<br>
>>> Is there a way to reliably add to, or at least override, the developer's<br>
>>> rpath in any cmake-built software?<br>
>><br>
>> Short of editing the build system scripts? I doubt...<br>
><br>
> The CMAKE_INSTALL_RPATH variable is used to initialise the INSTALL_RPATH<br>
> property of a target when that target is created. If you are pulling in<br>
> these other projects via add_subdirectory() rather than building them<br>
> standalone, you could modify the INSTALL_RPATH property of the targets you<br>
> want to change from within your own top level project after<br>
> add_subdirectory() returns.<br>
...<br>
<br>
Thanks for this. My knowledge of cmake is pretty poor - I assume it uses <br>
the same definition of target as make. So you're saying I'd need to know <br>
the project's interesting targets first.<br>
<br>
My choices are: maintain a patch to the software's build system files or <br>
maintain a patch to encaspulate the software's build system files and <br>
drive with a config file. Right?<br>
<br>
Thanks,<br>
<br>
Mark<br>
-- <br>
<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" rel="noreferrer" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Kitware offers various services to support the CMake community. For more information on each offering, please visit:<br>
<br>
CMake Support: <a href="http://cmake.org/cmake/help/support.html" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/support.html</a><br>
CMake Consulting: <a href="http://cmake.org/cmake/help/consulting.html" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/consulting.html</a><br>
CMake Training Courses: <a href="http://cmake.org/cmake/help/training.html" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/training.html</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="https://cmake.org/mailman/listinfo/cmake" rel="noreferrer" target="_blank">https://cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div>