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. ;-)
Howev
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 automaticall
On 2017 M08 24, Thu 13:36:45 CEST Robert Dailey wrote:
> So I have a "super build" CMake script that runs a series of
> ExternalProject_Add() functions to execute builds of various third
> party libraries and install them to a path relative to the parent
> project's CMAKE_BINARY_DIR.
>
> Once the
