mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-10-05 01:49:02 +00:00
Merge topic 'allow-backward-compatibility' into release-2.1
b2997bcbe Support backward compatibility in CMake package Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Vicente Bolea <vicente.bolea@kitware.com> Merge-request: !3234
This commit is contained in:
commit
cac8baa055
@ -337,7 +337,7 @@ configure_package_config_file(
|
||||
write_basic_package_version_file(
|
||||
${VTKm_BUILD_CMAKE_BASE_DIR}/${VTKm_INSTALL_CONFIG_DIR}/VTKmConfigVersion.cmake
|
||||
VERSION ${VTKm_VERSION}
|
||||
COMPATIBILITY ExactVersion )
|
||||
COMPATIBILITY SameMajorVersion )
|
||||
|
||||
#-----------------------------------------------------------------------------
|
||||
# Create makefile/package files for projects not using CMake
|
||||
|
17
docs/changelog/allow-backward-compatibility.md
Normal file
17
docs/changelog/allow-backward-compatibility.md
Normal file
@ -0,0 +1,17 @@
|
||||
# Support backward compatibility in CMake package
|
||||
|
||||
VTK-m development is in a mode where backward compatibility should be
|
||||
maintained between minor versions of the software. (You may get deprecation
|
||||
warnings, but things should still work.) To match this behavior, the
|
||||
generated CMake package now supports finding versions with the same major
|
||||
release and the same or newer minor release. For example, if an external
|
||||
program does this
|
||||
|
||||
``` cmake
|
||||
find_package(VTKm 2.1 REQUIRED)
|
||||
```
|
||||
|
||||
then CMake will link to 2.1 (of course) as well as newer minor releases
|
||||
(e.g., 2.2, 2.3, etc.). It will not, however, match older versions (e.g.,
|
||||
2.0, 1.9), nor will it match any version after the next major release
|
||||
(e.g., 3.0).
|
Loading…
Reference in New Issue
Block a user