diff options
author | Craig Scott <craig.scott@crascit.com> | 2023-04-27 13:12:03 (GMT) |
---|---|---|
committer | Kitware Robot <kwrobot@kitware.com> | 2023-04-27 13:12:26 (GMT) |
commit | 0ca98beb5747de97040227695732f660b7b91fc0 (patch) | |
tree | f97d62a34b926e8464bf1d60c8f969b059202211 /Help/policy | |
parent | 2fbcc81440343bdb1bca4e164fdefec98eaa1196 (diff) | |
parent | 550f63447d4c7d2db6ccbeaf1f6378aa6f7af4ed (diff) | |
download | CMake-0ca98beb5747de97040227695732f660b7b91fc0.zip CMake-0ca98beb5747de97040227695732f660b7b91fc0.tar.gz CMake-0ca98beb5747de97040227695732f660b7b91fc0.tar.bz2 |
Merge topic 'ExternalProject-relative-git-urls'
550f63447d ExternalProject/FetchContent: Support relative remote URLs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7988
Diffstat (limited to 'Help/policy')
-rw-r--r-- | Help/policy/CMP0150.rst | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/Help/policy/CMP0150.rst b/Help/policy/CMP0150.rst new file mode 100644 index 0000000..fe646d9 --- /dev/null +++ b/Help/policy/CMP0150.rst @@ -0,0 +1,39 @@ +CMP0150 +------- + +.. versionadded:: 3.27 + +:command:`ExternalProject_Add` and :command:`FetchContent_Declare` commands +treat relative ``GIT_REPOSITORY`` paths as being relative to the parent +project's remote. + +Earlier versions of these commands always treated relative paths in +``GIT_REPOSITORY`` as local paths, but the base directory it was treated +as relative to was both undocumented and unintuitive. The ``OLD`` behavior +for this policy is to interpret relative paths used for ``GIT_REPOSITORY`` +as local paths relative to the following: + +* The parent directory of ``SOURCE_DIR`` for :command:`ExternalProject_Add`. +* ``FETCHCONTENT_BASE_DIR`` for :command:`FetchContent_Declare`. + +The ``NEW`` behavior is to determine the remote from the parent project and +interpret the path relative to that remote. The value of +:variable:`CMAKE_CURRENT_SOURCE_DIR` when :command:`ExternalProject_Add` or +:command:`FetchContent_Declare` is called determines the parent project. +The remote is selected according to the following (the first match is used): + +* If the parent project is checked out on a branch with an upstream remote + defined, use that remote. +* If only one remote is defined, use that remote. +* If multiple remotes are defined and one of them is named ``origin``, use + ``origin``'s remote but also issue a warning. + +If an appropriate remote cannot be determined from the above, a fatal error +will be raised. + +This policy was introduced in CMake version 3.27. CMake version |release| +warns when a relative path is encountered and the policy is not set, +falling back to using ``OLD`` behavior. Use the :command:`cmake_policy` +command to set it to ``OLD`` or ``NEW`` explicitly. + +.. include:: DEPRECATED.txt |