What is wrong with explicitly specifying the non-standard locations up front so that FIND_PACKAGE has nothing to do?<div><br class="webkit-block-placeholder"></div><div>In other words, prime all the relevant cache variables with the non-standard locations.
</div><div><br class="webkit-block-placeholder"></div><div>There are many Find* scripts in the CMake Modules directory. I think it would be difficult to make a blanket recommendation concerning all of them that would be true 100% of the time with FIND_PACKAGE.
<br><br> </div><div>Are there specific packages you are having difficulty with?</div><div><br class="webkit-block-placeholder"></div><div><br><div><span class="gmail_quote">On 11/19/07, <b class="gmail_sendername">Stephen Collyer
</b> <<a href="mailto:scollyer@netspinner.co.uk">scollyer@netspinner.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">This would seem to be a very frequently asked question
<br>but I can't find it anywhere in the wiki or FAQ:<br>how do I tell FIND_PACKAGE to search on additional paths<br>to the default set, so I can work with packages installed<br>in non-standard locations ?<br><br>--<br>
Regards<br><br>Steve Collyer<br>Netspinner Ltd<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">
http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br> </div>