GitLab

As discussed on cmake-developers, this patch adds a macro
check_required_components() to the file configured via
configure_package_config_file(), so for proper handling
of components in Config.cmake files users can simply call

check_required_components(PackageName)

and this will do the right thing.

Alex

if the HANDLE_COMPONENTS is used, FPHSA() now also checks all required COMPONENTS,
i.e. all elements from <name>_FIND_COMPONENTS for which <name>_FIND_REQUIRED_<comp>
is true, and sets <name>_FOUND only to true if all have been found.
As discussed on cmake-developers.

Alex

This patch adds documentation for OPTIONAL_COMPONENTS to cmFindPackage.cxx,
and also extends Modules/readme.txt significantly with regard to how
components should be handled.

Alex

Alex

Add an OPTIONAL_COMPONENTS keyword to find_package() so we can have a
clear distinction between required and optional components.  Don't allow
a component to be both required and optional.

Alex

This patch adds a test which checks the error message, which is
produced in the case that a Config file has set Foo_FOUND to FALSE
by itself.

Alex

Alex

Before, find_package in Config mode always set Foo_FOUND to true if the
Config file has been found and could be executed.
If the Config file itself detected some problem, like a missing dependency,
it did not have a way to signal to the outside that the package is not working.
With this patch, if a Config file sets Foo_FOUND to FALSE, this is taken into
account and not overridden.

Alex

54604ee7 Document Fortran_MODULE_DIRECTORY as OUTPUT only (#13034)

55b2aa88 Use generalized RunCMake test infrastrucure for build_command test
eb33000d Use generalized RunCMake test infrastrucure for find_package test
42a81e71 Add stronger infrastructure for CMake-only tests

e390f87d WriteBasicConfigVersionFile: add test for ExactVersion mode
5d182239 write_basic_package_version_file: add ExactVersion mode
1c69cd8f write_basic_package_version_file(): improve documentation

289e5e60 Merge branch 'upstream-kwiml' into update-KWIML
f94ae0ec KWIML: Make test_INT robust to #define-d int#_t and INT#_C

05a76d53 CPack: Fix retry logic when calls to hdiutil fail

ea4416cf CTest: Match valgrind errors with "points to" (#12922)

c7da50da CTest: Detect Xcode error "Command ... failed with exit code"

0996f2a2 Hide Makefile local object info inside local generator
67734be8 VS: Simplify object name computation
4ae7f365 Remove unused partial OBJECT_FILES property implementation

b926cff1 Suppress warnings occurring on the dashboards using the PGI compiler.

a5561376 FindCxxTest: Add support for CxxTest 4 (#13022)

CMake does not automatically pass the Fortran module output directory
location to the module search path.  Add a note to the documentation
that the location must also be specified by INCLUDE_DIRECTORIES.

The CMakeCommands.build_command test performs output/error checking
so move it over to RunCMake to re-use the generalized infrastrucure.
This is the only test left using Tests/CMakeCommands/CMakeLists.txt
so remove it.

The CMakeOnly directory added by commit 9a20abf0 (Add infrastructure for
CMake-only tests, 2012-01-11) was sufficient only for tests that always
run CMake to successfully configure a project.  Later commit eeaaffcb
(find_package: Test error and warning messages in failure cases,
2012-02-28) added a sample test that covers failure cases.

Generalize the above to create new "RunCMake" test infrastructure that
can run CMake multiple times for a single project with different
variations and check for expected result/stdout/stderr.  Allow for both
successful and failing CMake project configuration cases.  This will be
useful to test error messages and failure behavior.

Alex

This mode is for packages which consider themselves only compatible if
exactly the same version is requested. The tweak version is ignored.

Alex

add notes when which mode should be used

Alex

Our TEST* macro calls pass arguments such as "int64_t" with the
expectation that the preprocessing token will be used literally.
Some platforms #define int64_t as "long long" which is not a valid
preprocessing token.  Perform preprocessor symbol concatenation
on the type names at the first level of macro evaluation to avoid
expanding the names.

The long-standing sporadic failures of CPack tests on the Mac dashboards
are caused by an occasional problem running hdiutil. To compensate for
this, a retry loop was added in the code in a previous commit: a9fa71a4
... but the logic for breaking out of the retry loop was flawed, breaking
out of the loop (and not retrying) when the hdiutil command returns an
error instead of when it returns success.

This commit fixes the flawed logic, bumps up the number of retries from
4 to 10, and adds a half-second delay in between retries.

The delay is specifically added in case a virus checker or spotlight indexer
is temporarily causing the hdiutil failure by hanging onto a newly created
file longer than hdiutil expects it to.

As with all sporadically occurring issues, we'll never know if this is
really fixed all the way. But I'll be happy even if we can only get it to
happen just a bit less often.

Teach CTest to match valgrind errors of the format
"Syscall param ... points to uninitialised byte(s)".

2c601c10 DeployQt4: Add path to Qt dlls on Windows.

c5ae7331 find_package: Test that REQUIRED aborts processing correctly
c91a54db find_package: error out if REQUIRED Config has not been found

6973e2d5 wrap write_basic_config_version_file as write_basic_package_version_file()
204f5d44 add CMakePackageConfigHelpers: configure_package_config_file()

b28e7fa1 VS6: Avoid SBCS test on VS6 (#12189)
df19b9ca VS6: Avoid _MBCS define when _SBCS is defined (#12189)
ba89e92b Visual Studio: Allow setting Single Byte Character Set (#12189)