<div class="gmail_quote">2011/7/7 Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Thursday 07 July 2011, David Cole wrote:<br>
...<br>
<div class="im">> Indeed, it would be preferable. Actually, I would prefer it if all of the<br>
> Find modules were installed as part of the project that they represent<br>
> rather than being in CMake itself.<br>
<br>
</div>You probably didn't mean that ;-)<br>
Projects themselves should install a FooConfig.cmake file, but not a<br>
FindFoo.cmake file, since then finding the FindFoo.cmake file is already the<br>
hard part, the project actually doesn't have to be found anymore then.<br>
<br>
Alex<br>
</blockquote></div><br>You're right. That's what I meant. I meant to say, projects should install a <project>Config.cmake file, as documented in the very detailed help text for the find_package command.<br>
<br>See the text beginning with "CMake constructs a set of possible installation prefixes" here:<br><br> <a href="http://cmake.org/cmake/help/cmake-2-8-docs.html#command:find_package">http://cmake.org/cmake/help/cmake-2-8-docs.html#command:find_package</a><br>
<br>Thanks for the correction!<br>David<br><br>