You are not being stupid. It does need to be used at installation time to be useful.<div><br></div><div>The intent is to analyze a given built executable to determine the required set of (possibly 3rd-party, possibly built elsewhere on the build machine) libraries that it needs to run. Then, given that set, you need to make sure that you have install rules to cover all of those libraries.<br>
<br></div><div>The first working example of its use is in the ParaView code base where it is used to copy libraries into ParaView's Mac bundle application. It is used in conjunction with BundleUtilities.cmake to "fix up" the bundle app so that it is standalone and contains all of its referenced libraries in the bundle directory structure. Then the bundle can be copied to any directory or to another Mac and it should all "just work."</div>
<div><br></div><div>Having said that, there is more work to be done to make this a genuinely easy to use feature of CMake. I envision being able to do the same thing at make install time for Linux and Win32 builds, but according to the conventions of those platforms. Dlls copied into the same dir with the exe on Win32 and "whatever's appropriate" on Linux builds... (Feel free to make suggestions.)</div>
<div><br></div><div>So... ideally it would all just work automatically and all you would have to do in CMake is add an install rule for your executable and call a post-install script that copies/fixes up libraries appropriately in a platform-independent manner.</div>
<div><br></div><div>Thanks for asking questions / contributing to the discussion / improving this development feature of CMake.....</div><div><br></div><div> David</div><div><br></div><div><br></div><div><div class="gmail_quote">
On Tue, Oct 28, 2008 at 7:36 AM, Mike Arthur <span dir="ltr"><<a href="mailto:mike@mikearthur.co.uk">mike@mikearthur.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Perhaps I'm just being stupid but I can't see how this can be used as it needs<br>
to be called at installation time and I'm not aware that modules can be?<br>
<br>
Does anyone have a working example of how to install its outputted libraries?<br>
<font color="#888888">--<br>
Cheers,<br>
Mike Arthur<br>
<a href="http://mikearthur.co.uk/" target="_blank">http://mikearthur.co.uk/</a><br>
_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</font></blockquote></div><br></div>