ExternalProject: Revise wording of TLS_VERIFY documentation

This commit is contained in:
Brad King
2024-02-28 09:36:22 -05:00
parent fe5e6c27bd
commit e39c37ab29
+6 -7
View File
@@ -227,8 +227,8 @@ URL
``TLS_VERIFY <bool>`` ``TLS_VERIFY <bool>``
Specifies whether certificate verification should be performed for Specifies whether certificate verification should be performed for
https URLs. If this option is not provided, the default behavior is ``https://`` URLs. If this option is not provided, the default behavior
determined by the :variable:`CMAKE_TLS_VERIFY` variable (see is determined by the :variable:`CMAKE_TLS_VERIFY` variable (see
:command:`file(DOWNLOAD)`). If that is also not set, certificate :command:`file(DOWNLOAD)`). If that is also not set, certificate
verification will not be performed. In situations where ``URL_HASH`` verification will not be performed. In situations where ``URL_HASH``
cannot be provided, this option can be an alternative verification cannot be provided, this option can be an alternative verification
@@ -236,11 +236,10 @@ URL
.. versionchanged:: 3.6 .. versionchanged:: 3.6
This option also applies to ``git clone`` invocations, although the This option also applies to ``git clone`` invocations, although the
default behavior is different. If ``TLS_VERIFY`` is not given and default behavior is different. If neither the ``TLS_VERIFY`` option
:variable:`CMAKE_TLS_VERIFY` is not set, the behavior will be or :variable:`CMAKE_TLS_VERIFY` variable is specified, the behavior
determined by git's defaults. Normally, the ``sslVerify`` git will be determined by git's default (true) or a ``http.sslVerify``
config setting defaults to true, but the user may have overridden git config option the user may have set at a global level.
this at a global level.
``TLS_CAINFO <file>`` ``TLS_CAINFO <file>``
Specify a custom certificate authority file to use if ``TLS_VERIFY`` Specify a custom certificate authority file to use if ``TLS_VERIFY``