eb8facd396 macOS: Avoid relying on sw_vers when cross-compiling from another OS
476b2a386f macOS: Remove outdated condition for CMAKE_OSX_DEPLOYMENT_TARGET
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !10721
We have a few code paths needed only to support builds hosted on
macOS 10.4. Update the conditions to work when cross-compiling
to macOS from another platform.
Fixes: #26814
Revert commit 2853326e7a (BUG: Only set CMAKE_OSX_DEPLOYMENT_TARGET on
Mac OSX 10.4 or later, 2009-01-27, v2.8.0~1169). AFAIK no one is using
macOS versions older than 10.4 anymore.
Record `find_` command events in the configure log, except
`find_package` as it is far more complicated (and will have its own
event kind).
Note that testing only generates the events of interest, there is no
verification. Also note that testing that the "found" to "notfound"
transition causes an event is not testable because a truthy value in the
variable skips any kind of verification or other logic beyond
normalization.
Co-Authored-by: Ryan Krattiger <ryan.krattiger@kitware.com>
See: #24833
When logging a `WriteFindBaseEvent`, one of the triggers to log is the
change in the "found" status of a `find_` command. Track the difference
between "undefined", "found", and "tried before, but not found" so that
the transition can be detected reliably.
Co-Authored-by: Ryan Krattiger <ryan.krattiger@kitware.com>
FindMFC:
- Synced module documentation with other similar find modules.
- Added examples section.
- Added reference link to CMAKE_MFC_FLAG variable.
CMAKE_MFC_FLAG:
- Added separate examples section.
- Mentioned FindMFC module.
- Used target_compile_definitions() instead of add_definitions().
- Module documentation synced with other similar find modules.
- Added examples section.
- Added note about Swift Testing framework, which supersedes the XCTest.
- Added note about the XCTEST target property and synced docs a bit.
- Used word "commands" instead of "macros" or "functions".
- Updated module documentation.
- Added "Examples" section showing some basic usage.
- Added "See Also" section in FindGTK to reference the FindGTK2.
- Added usage of pkg-config in examples for newer GTK versions.
Issues: #15888, #22693
36d96ce044 ci: Drop outdated HDF5 Fortran compiler wrapper patch from Fedora jobs
5b21de16a0 ci: use Fedora 42 images and environments
efa818f661 ci: update Fedora base images to Fedora 42
585e1655c2 ci: Update cppdap in extdeps jobs
01d0f037b6 ci: Remove superuser tools from PATH in Linux jobs
8b1b201154 clang-tidy: suppress misc-redundant-expression lint on macro expansion
3d0ac2dafa clang-tidy: fix bugprone-unhandled-self-assignment lint
16455374cf Source: Suppress gcc 15 -Wmaybe-uninitialized in std::function
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !10711
- Extended examples section and changed example to use a locally created
imported target showing how to add usage requirements to project.
- Mention of CMake 2.x removed as these version notes are now being
cleaned in the CMake 4 documentation (CMake docs are at this point
considering the 2.8.12.2 as the initial state upon which new and
changed items are documented through versions).
- Extended components section.
- Added See Also section.
- Removed internal comment about naming conventions. Find modules
distributed with CMake ideally should follow standard find modules
naming conventions for variables and to have it synced with
other find modules shipped with CMake.
- Used the OpenSceneGraph_FOUND variable (CMake 3.3). The uppercased
OPENSCENEGRAPH_FOUND is also set to the same value.
- Added note in introduction how to include headers.
Drop the patch step from commit 919de8785b (ci: Patch HDF5 Fortran
compiler wrappers in Fedora jobs, 2023-03-30, v3.27.0-rc1~242^2~1).
Fedora 42's HDF5 packages fixed the problem.
Our Linux CI jobs incidentally run as `root` in their containers, but
do not need any superuser tools. Drop `sbin` entries from the `PATH`.
This also avoids finding user tools through Fedora 42's `sbin -> bin`
symbolic links.
In a project that has enabled C or CXX, we bias ASM and Fortran compiler
selection to match. Propagate this bias into the `check_language` test
project so that if it succeeds, we will select the same compiler when
enabling the tested language in the calling project.
Fixes: #19350
