<br><br><div class="gmail_quote">On Wed, Jan 14, 2009 at 4:20 PM, Miguel A. Figueroa-Villanueva <span dir="ltr"><<a href="mailto:miguelf@ieee.org">miguelf@ieee.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Jan 14, 2009 at 5:54 PM, Andreas Pakulat wrote:<br>
> On 14.01.09 15:45:53, Robert Dailey wrote:<br>
</div><div class="Ih2E3d">>> On Wed, Jan 14, 2009 at 1:20 PM, Andreas Pakulat wrote:<br>
>><br>
>> > If you look at the cmake docs, then you'll find out that nothing in there<br>
>> > states that wildcards are allowed. Hence I'd assume that wildcards are not<br>
>> > supported.<br>
>> ><br>
>> > Also you only need to set one of the two for find_path to use the<br>
>> > directory.<br>
>><br>
>> Well if only the CMake documentation was that reliable. There's information<br>
>> that I have found to be inaccurate or missing from the docs.<br>
><br>
> So far I haven't found inaccurate information myself, missing yes<br>
> sometimes.<br>
><br>
>> For example, the documentation for find_package() no where mentions the<br>
>> variable created for the COMPONENTS parameter. Looking at FindBoost.cmake,<br>
>> it appears to be in the form of <prefix>_FIND_COMPONENTS. Is this correct?<br>
><br>
> Apparently yes, but no idea where I got that from :) Would be good to<br>
> file a bugreport at <a href="http://www.cmake.org" target="_blank">www.cmake.org</a> as this is indeed missing in the docs.<br>
<br>
</div>Well, you can find it in the Modules/readme.txt file. However, the<br>
module user doesn't need to know about the <prefix>_FIND_COMPONENTS<br>
variable. This is for the FindXXX module developer. Also, note that<br>
maybe you find inconsistent the information in the find_package<br>
documentation, because of old or poorly written find modules that do<br>
not work as they should. However, the documentation for CMake in<br>
general is very reliable (although sometimes missing some).<br>
<br>
In your case, it seems you need to generate the list of paths to be<br>
searched appropriately (no wildcard) and then use something like this:<br>
<br>
find_path(<VAR> NAMES name PATHS ${path_list} NO_DEFAULT_PATH)<br>
<br>
That is, if you don't want to search in the standard directories. Make<br>
sure you appropriately handle spaces in directory names and print the<br>
generated list of paths to see where you are searching.</blockquote></div><br>What do you mean by "print the generated list of paths to see where you are searching"? Do you mean to print ${path_list}? If not, could you explain?<br>
<br>You are right that there are inconsistencies in the Find modules, which is a primary source of confusion for me. A lot of the find modules that I write use libfind_process(), but a lot of things store found libraries in inconsistent variables. For example, some Find modules place libraries in <prefix>_LIBRARIES, and a few place them in <prefix>_LIBRARY (Like FindPNG.cmake).<br>
<br>Thanks for your help.<br>