diff options
author | Alex Neundorf <neundorf@kde.org> | 2012-02-16 23:36:18 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2012-03-07 16:23:18 (GMT) |
commit | 6973e2d5a8be4d19aeb26fa67c0ed501ed81364e (patch) | |
tree | f01b6b5ecabbe560915171bd30cdd2a7eb355abf /Modules/WriteBasicConfigVersionFile.cmake | |
parent | 204f5d443c68317b8a24439035bf1f6c39cc001c (diff) | |
download | CMake-6973e2d5a8be4d19aeb26fa67c0ed501ed81364e.zip CMake-6973e2d5a8be4d19aeb26fa67c0ed501ed81364e.tar.gz CMake-6973e2d5a8be4d19aeb26fa67c0ed501ed81364e.tar.bz2 |
wrap write_basic_config_version_file as write_basic_package_version_file()
So the name fits better with configure_package_config_file(), as
discussed on the mailing list. Adapt the documentation accordingly.
Alex
Diffstat (limited to 'Modules/WriteBasicConfigVersionFile.cmake')
-rw-r--r-- | Modules/WriteBasicConfigVersionFile.cmake | 27 |
1 files changed, 1 insertions, 26 deletions
diff --git a/Modules/WriteBasicConfigVersionFile.cmake b/Modules/WriteBasicConfigVersionFile.cmake index 0b6519d..038cb57 100644 --- a/Modules/WriteBasicConfigVersionFile.cmake +++ b/Modules/WriteBasicConfigVersionFile.cmake @@ -1,31 +1,6 @@ # WRITE_BASIC_CONFIG_VERSION_FILE( filename VERSION major.minor.patch COMPATIBILITY (AnyNewerVersion|SameMajorVersion) ) # -# Writes a file for use as <package>ConfigVersion.cmake file to <filename>. -# See the documentation of FIND_PACKAGE() for details on this. -# filename is the output filename, it should be in the build tree. -# major.minor.patch is the version number of the project to be installed -# The COMPATIBILITY mode AnyNewerVersion means that the installed package version -# will be considered compatible if it is newer or exactly the same as the requested version. -# If SameMajorVersion is used instead, then the behaviour differs from AnyNewerVersion -# in that the major version number must be the same as requested, e.g. version 2.0 will -# not be considered compatible if 1.0 is requested. -# If your project has more elaborated version matching rules, you will need to write your -# own custom ConfigVersion.cmake file instead of using this macro. -# -# Example: -# write_basic_config_version_file(${CMAKE_CURRENT_BINARY_DIR}/FooConfigVersion.cmake -# VERSION 1.2.3 -# COMPATIBILITY SameMajorVersion ) -# install(FILES ${CMAKE_CURRENT_BINARY_DIR}/FooConfigVersion.cmake -# ${CMAKE_CURRENT_BINARY_DIR}/FooConfig.cmake -# DESTINATION lib/cmake/Foo ) -# -# Internally, this macro executes configure_file() to create the resulting -# version file. Depending on the COMPATIBLITY, either the file -# BasicConfigVersion-SameMajorVersion.cmake.in or BasicConfigVersion-AnyNewerVersion.cmake.in -# is used. Please note that these two files are internal to CMake and you should -# not call configure_file() on them yourself, but they can be used as starting -# point to create more sophisticted custom ConfigVersion.cmake files. +# Deprecated, see WRITE_BASIC_PACKAGE_VERSION_FILE(), it is identical. #============================================================================= # Copyright 2008-2011 Alexander Neundorf, <neundorf@kde.org> |