[PATCH 06/10] meson: require SecurityFramework when it's used as SHA1 backend
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Dec 30, 2024, 14:24 UTC
- Message-ID
- <20241230-pks-meson-sha1-unsafe-v1-6-efb276e171f5@pks.im>
- In-Reply-To
- <20241230-pks-meson-sha1-unsafe-v1-0-efb276e171f5@pks.im>
The Security framework is required when we use CommonCrypto either as HTTPS or SHA1 backend, but we only require it in case it is set up as HTTPS backend. Fix this.
Signed-off-by: Patrick Steinhardt <ps@pks.im> --- meson.build | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build index 6fa4d900ee02f0b80bc3c36d58a07a118ec3fb20..bc75ad954a4949342125b769d3d8d8362ef4e8a3 100644 --- a/meson.build +++ b/meson.build @@ -1329,7 +1329,7 @@ https_backend = get_option('https_backend') sha1_backend = get_option('sha1_backend') sha256_backend = get_option('sha256_backend') -security_framework = dependency('Security', required: https_backend == 'CommonCrypto') +security_framework = dependency('Security', required: https_backend == 'CommonCrypto' or sha1_backend == 'CommonCrypto') core_foundation_framework = dependency('CoreFoundation', required: security_framework.found()) if https_backend == 'auto' and security_framework.found() https_backend = 'CommonCrypto'
-- 2.48.0.rc0.311.gb6c66824c1.dirty