[CMake] [cmake-developers] Debugging find_package() search behavior?

[David Cole]

No, I was already promptly corrected by Brad, too. I was not
accounting for the fact that the other find_* calls used inside of
find modules also use CMAKE_PREFIX_PATH. I was thinking of its use to
find a project's config file from the find_package config mode.

I stand corrected. Again. ;-)

However, I stand by my assertion that find modules do what they want.
It's still a bit of a wild wild west, and people make their own find
modules that live inside their own project's source trees.

Config files should be the preferred/primary mechanism for
find_package calls (going on something like 5 or 6 years now...), but
still people write new find modules.


Thanks,
David C.




On Sun, Oct 1, 2017 at 11:52 AM, Alexander Neundorf
<a.neundorf-work at gmx.net> wrote:
> On 2017 M08 29, Tue 11:33:15 CEST David Cole via cmake-developers wrote:
>> That's correct:
>>
>> find modules do what they want, and most do not pay attention to
>> CMAKE_PREFIX_PATH.
>
> are you sure ?
> As long as NO_DEFAULT_PATH is not used in the find_*() calls, CMAKE_PREFIX_PATH
> is used automatically by them.
>
> Alex
>