|
|
@@ -79,15 +79,16 @@ If ``NO_DEFAULT_PATH`` is not specified, the search process is as follows:
|
|
|
|prefix_XXX_SUBDIR| for each ``<prefix>`` in
|
|
|
:variable:`CMAKE_SYSTEM_PREFIX_PATH`
|
|
|
|
|
|
-1. If called from within a find module loaded by
|
|
|
+1. If called from within a find module or any other script loaded by a call to
|
|
|
:command:`find_package(<PackageName>)`, search prefixes unique to the
|
|
|
- current package being found. Specifically look in the
|
|
|
+ current package being found. Specifically, look in the
|
|
|
:variable:`<PackageName>_ROOT` CMake variable and the
|
|
|
:envvar:`<PackageName>_ROOT` environment variable.
|
|
|
- The package root variables are maintained as a stack so if called from
|
|
|
- nested find modules, root paths from the parent's find module will be
|
|
|
- searched after paths from the current module,
|
|
|
- i.e. ``<CurrentPackage>_ROOT``, ``ENV{<CurrentPackage>_ROOT}``,
|
|
|
+ The package root variables are maintained as a stack, so if called from
|
|
|
+ nested find modules or config packages, root paths from the parent's find
|
|
|
+ module or config package will be searched after paths from the current
|
|
|
+ module or package. In other words, the search order would be
|
|
|
+ ``<CurrentPackage>_ROOT``, ``ENV{<CurrentPackage>_ROOT}``,
|
|
|
``<ParentPackage>_ROOT``, ``ENV{<ParentPackage>_ROOT}``, etc.
|
|
|
This can be skipped if ``NO_PACKAGE_ROOT_PATH`` is passed or by setting
|
|
|
the :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` to ``FALSE``.
|