git/hash.h

#ifndef HASH_H
#define HASH_H

#if defined(SHA1_PPC)
#include "ppc/sha1.h"
#elif defined(SHA1_APPLE)
#include <CommonCrypto/CommonDigest.h>
#elif defined(SHA1_OPENSSL)
#include <openssl/sha.h>
#else /* SHA1_BLK */
#include "block-sha1/sha1.h"
#endif

#endif
hash.h: move SHA-1 implementation selection into a header file Many developers use functionality in their editors that allows for quick syntax checks, including warning about questionable constructs. This functionality allows rapid development with fewer errors. However, such functionality generally does not allow the specification of project-specific defines or command-line options. Since the SHA1_HEADER include is not defined in such a case, developers see spurious errors when using these tools. Furthermore, there are known implementations of "cc" whose '#include' is unhappy with this construct. Instead of using SHA1_HEADER, create a hash.h header and use #if and #elif to select the desired header. Have the Makefile pass an appropriate option to help the header select the right implementation to use. [jc: make BLK_SHA1 the fallback default as discussed on list, e.g. <20170314201424.vccij5z2ortq4a4o@sigill.intra.peff.net>; also remove SHA1_HEADER and SHA1_HEADER_SQ that are no longer used]. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com> Reviewed-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2017-03-12 01:28:18 +03:00			`#ifndef HASH_H`
			`#define HASH_H`

			`#if defined(SHA1_PPC)`
			`#include "ppc/sha1.h"`
			`#elif defined(SHA1_APPLE)`
			`#include <CommonCrypto/CommonDigest.h>`
			`#elif defined(SHA1_OPENSSL)`
			`#include <openssl/sha.h>`
			`#else /* SHA1_BLK */`
			`#include "block-sha1/sha1.h"`
			`#endif`

			`#endif`