diff options
| author | Patrick Steinhardt <ps@pks.im> | 2017-12-05 08:48:31 +0000 |
|---|---|---|
| committer | Patrick Steinhardt <ps@pks.im> | 2018-01-04 11:23:57 +0000 |
| commit | 70aa61460a4f33509aa06ed86ac3becc243ee5d6 (patch) | |
| tree | 09cc5fd47b2a6fe37f310db0885bffa2579203f3 /CMakeLists.txt | |
| parent | e7495ce6f4dee156b6a1d48a4d478c83d1053236 (diff) | |
| download | libgit2-70aa61460a4f33509aa06ed86ac3becc243ee5d6.tar.gz | |
cmake: allow explicitly choosing SHA1 backend
Right now, if SHA1DC is disabled, the SHA1 backend is mostly chosen
based on which system libgit2 is being compiled on and which libraries
have been found. To give developers and distributions more choice,
enable them to request specific backends by passing in a
`-DSHA1_BACKEND=<BACKEND>` option instead. This completely replaces the
previous auto-selection.
Diffstat (limited to 'CMakeLists.txt')
| -rw-r--r-- | CMakeLists.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CMakeLists.txt b/CMakeLists.txt index 32f8ac082..48a4d91a4 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -42,7 +42,7 @@ OPTION( PROFILE "Generate profiling information" OFF ) OPTION( ENABLE_TRACE "Enables tracing support" OFF ) OPTION( LIBGIT2_FILENAME "Name of the produced binary" OFF ) -OPTION( USE_SHA1DC "Use SHA-1 with collision detection" ON ) +SET(SHA1_BACKEND "CollisionDetection" CACHE STRING "Backend to use for SHA1. One of Generic, OpenSSL, Win32, CommonCrypto, CollisionDetection. ") OPTION( USE_SSH "Link with libssh to enable SSH support" ON ) OPTION( USE_HTTPS "Enable HTTPS support. Can be set to a specific backend" ON ) OPTION( USE_GSSAPI "Link with libgssapi for SPNEGO auth" OFF ) |