| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Alex
|
|
|
|
|
|
|
|
| |
Isolation of policy changes inside scripts is important for protecting
the including context. This teaches include() and find_package() to
imply a cmake_policy(PUSH) and cmake_policy(POP) around the scripts they
load, with a NO_POLICY_SCOPE option to disable the behavior. This also
creates CMake Policy CMP0011 to provide compatibility. See issue #8192.
|
|
|
|
|
| |
This converts the variable and policy scope protection find_package()
uses when loading version files to use automatic variables.
|
|
|
|
|
|
| |
Recently we taught find_package to re-find a package configuration file
if it is given a wrong answer. This fixes the documentation to reflect
the change.
|
|
|
|
|
|
|
|
|
|
| |
to by the Foo_DIR variable there is no FooConfig.cmake file, then instead of
abort and complain that the user should set or clear the Foo_DIR variables,
just search for the file and discard the old Foo_DIR contents
The tests succeed, ok by Brad.
Alex
|
|
|
|
|
|
|
|
|
|
|
|
| |
We now search in
<prefix>/<name>*/
<prefix>/<name>*/(cmake|CMake)
when looking for package configuration files. This is useful on Windows
since the Program Files folder is in CMAKE_SYSTEM_PREFIX_PATH. These
paths are the Windows equivalent to the Apple convention application and
framework paths we already search. See issue #8264.
|
|
|
|
|
|
|
| |
When the find_package command loads a <name>-version.cmake file to test
the package version it must prevent the version file from affecting
policy settings. Therefore the policy settings must be pushed and
popped.
|
|
|
|
|
|
|
|
|
|
| |
This teaches find_package to search
<prefix>/(share|lib)/cmake/<name>*/
for package configuration files. Packages that do not already have
files in a <prefix>/lib/<name>* directory can use this location to avoid
cluttering the lib directory.
|
|
|
|
|
| |
Versioning has been introduced to find_package, so the comment about it
is out of date.
|
|
|
|
|
|
|
|
|
| |
When the find_package command loads a module it sets several
<pkg>_FIND_XXX variables to communicate information about the command
invocation to the module. This restores the original state of the
variables when the command returns. This behavior is useful when a
find-module recursively calls find_package with NO_MODULE so that the
inner call does not change the values in the find-module.
|
|
|
|
|
|
|
|
|
| |
Recently we taught find_package that the NO_MODULE option is implied
when it is recursively invoked in a find-module. This behavior may be
confusing because two identical calls may enter different modes
depending on context. It also disallows the possibility that one
find-module defers to another find-module by changing CMAKE_MODULE_PATH
and recursively invoking find_package. This change reverts the feature.
|
|
|
|
|
|
|
| |
Package version test files may now declare that they are unsuitable for
use with the project testing them. This is important when the version
being tested does not provide a compatible ABI with the project target
environment.
|
|
|
|
|
|
|
| |
These changes teach find_package to behave nicely when invoked
recursively inside a find-module for the same package. The module will
never be recursively loaded again. Version arguments are automatically
forwarded.
|
|
|
|
|
| |
If the find_package command is invoked with the EXACT option but without
a version, warn and ignore the option.
|
|
|
|
|
|
|
|
| |
Make the number of version components specified explicitly available.
Set variables for unspecified version components to "0" instead of
leaving them unset. This simplifies version number handling for find-
and config-modules. Also support a fourth "tweak" version component
since some packages use them.
|
|
|
|
|
|
| |
Use the new-style error reporting mechanism to provide more context
information for a find_package call with a bad package name. When the
package is not required, issue a warning instead of an error.
|
|
|
|
| |
Alex
|
|
|
|
|
|
|
|
|
| |
variables
also in Config mode, so the xxxConfig.cmake files can e.g. test the QUIETLY
parameter and print something or not
Alex
|
|
|
|
|
| |
When find_package is about to look in <prefix>/lib, search first in
<prefix>/lib64 in cases that find_library would use lib64 paths.
|
|
|
|
|
|
|
|
| |
- The CMAKE_PREFIX_PATH and similar variables have both
environment and CMake cache versions.
- Previously the environment value was checked before the
cache value.
- Now the cache value is favored because it is more specific.
|
|
|
|
|
|
| |
- Hints are searched after user locations but before system locations
- The HINTS option should have paths provided by system introspection
- The PATHS option should have paths that are hard-coded guesses
|
|
|
|
|
|
| |
- Create cmFindCommon::AddTrailingSlashes
- Use it in cmFindBase and cmFindPackageCommand
- Remove duplication from other find commands
|
|
|
|
|
|
|
|
|
|
|
| |
- Add each part of the search order in a separate method.
- Collect added paths in an ivar in cmFindCommon.
- Move user path storage up to cmFindCommon and share
between cmFindBase and cmFindPackageCommand.
- Expand user path registry values up in cmFindCommon
- Enables 32-/64-bit registry view for find_package
- Disables registry expansion for paths not specified
with the PATHS argument, which is not expected.
|
|
|
|
| |
multiple versions.
|
|
|
|
|
|
| |
- Added EXACT option to request an exact version.
- Enforce version using check provided by package.
- Updated FindPackageTest to test versioning in config mode.
|
|
|
|
| |
invocation signature to be able to return extra informaiton via the cmExecutionStatus class
|
| |
|
| |
|
|
|
|
| |
Version numbers provided to the command are converted to variable settings to tell the FindXXX.cmake module what version is requested. This addresses issue #1645.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Use CMAKE_PREFIX_PATH and CMAKE_SYSTEM_PREFIX_PATH among other means
to locate package configuration files.
- Create cmFindCommon as base for cmFindBase and cmFindPackageCommand
- Move common functionality up to cmFindCommon
- Improve documentation of FIND_* commands.
- Fix FIND_* commands to not add framework/app paths in wrong place.
|
| |
|
|
|
|
|
|
| |
FooConfig.cmake were found
Alex
|
|
|
|
| |
Alex
|
|
|
|
|
|
|
| |
feature summary, which needs to check for both the upper case and original
case _FOUND variables
Alex
|
|
|
|
|
|
|
|
|
|
|
|
| |
the cmake run and add macros print_enabled/disabled_features() and
set_feature_info(), so projects can get a nice overview at the end of the
cmake run what has been found and what hasn't
FIND_PACKAGE() automatically adds the packages to these global properties,
except when used with QUIET
Maybe this can also be useful for packagers to find out dependencies of
projects.
Alex
|
| |
|
|
|
|
| |
command. Re-implemented argument parsing to be simpler and more robust.
|
|
|
|
| |
with REQUIRED option. This addresses the feature request in bug#3494.
|
| |
|
| |
|
|
|
|
| |
FIND_PACKAGE command. This addresses bug#2771.
|
|
|
|
| |
of inherited commands, makefiles no longer read in the parent makefiles but instead inherit thier parent makefiles current settings
|
|
|
|
| |
smaller and faster
|
| |
|
| |
|
|
|
|
| |
the cmake configure step if the package is not found.
|
| |
|