Thread (2 messages) 2 messages, 2 authors, 2016-06-15

Re: Combining APPLE_COMMON_CRYPTO=1 and NO_OPENSSL=1 produces unexpected result

From: Eric Sunshine <hidden>
Date: 2016-06-15 23:07:47

On Fri, Jan 15, 2016 at 1:52 PM, Junio C Hamano [off-list ref] wrote:
David Aguilar [off-list ref] writes:
quoted
I'm curious to see what others think about dropping CommonCrypto.
It seems like a good choice from a maintenance POV.
Judging by a week-long silence, it seems nobody seems to have much
to say on this issue.  Let me summon the git_osx_installer
maintainer to hear from somebody who know a lot better than me about
things around OS X.
Dropping CommonCrypto seems reasonable to me. Since Apple's
CommonCrypto provides only a subset of the OpenSSL functionality Git
uses, we still end up bringing in OpenSSL anyhow in addition to
CommonCrypto, so CommonCrypto isn't buying us much (if anything).
Unfortunately, we'd still want to keep the ugly hack to suppress the
unavoidable "noise" Apple thrust upon us by populating the OpenSSL
headers with #warnings about unstable ABI.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help