Kitware/CMake
1
0
Fork 0
mirror of https://github.com/Kitware/CMake.git synced 2025-10-14 02:08:27 +08:00
Code Issues Projects Releases Wiki Activity

export: Increase maximum policy version in exported files to 4.0

Browse Source 
The files generated by `install(EXPORT)`, `export()`, and
`install_jar_exports()` commands are known to work with policies
as of CMake 4.0, so enable them in sufficiently new CMake versions.
This commit is contained in:
Brad King
2025-07-02 09:41:30 -04:00
parent 94ff184a63
commit f7380d8c4a
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Modules/UseJava/javaTargets.cmake.in
View File

@@ -1,5 +1,5 @@
cmake_policy(PUSH)
cmake_policy(VERSION 2.8.12...3.31)
cmake_policy(VERSION 2.8.12...4.0)
#----------------------------------------------------------------
# Generated CMake Java target import file.

4
Source/cmExportCMakeConfigGenerator.cxx
View File

@@ -173,7 +173,7 @@ void cmExportCMakeConfigGenerator::GeneratePolicyHeaderCode(std::ostream& os)
// Isolate the file policy level.
// Support CMake versions as far back as the
// RequiredCMakeVersion{Major,Minor,Patch}, but also support using NEW
// policy settings for up to CMake 3.31 (this upper limit may be reviewed
// policy settings for up to CMake 4.0 (this upper limit may be reviewed
// and increased from time to time). This reduces the opportunity for CMake
// warnings when an older export file is later used with newer CMake
// versions.
@@ -182,7 +182,7 @@ void cmExportCMakeConfigGenerator::GeneratePolicyHeaderCode(std::ostream& os)
"cmake_policy(VERSION "
<< this->RequiredCMakeVersionMajor << '.'
<< this->RequiredCMakeVersionMinor << '.'
<< this->RequiredCMakeVersionPatch << "...3.31)\n";
<< this->RequiredCMakeVersionPatch << "...4.0)\n";
/* clang-format on */
}