Windows: use BLK_SHA1 again
Since NO_OPENSSL is no longer defined on Windows, BLK_SHA1 is not defined anymore implicitly. Define it explicitly. As a nice side-effect, we no longer link against libcrypto.dll, which has non-trivial startup costs because it depends on 6 otherwise unneeded DLLs. Signed-off-by: Johannes Sixt <j6t@kdbg.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Sixt committed
Oct 22, 2009 at 20:26 UTC
9bccfcdbff3b11e11a69d05c50c8bc1a9a6dbb5f
1 file changed
+2
Makefile
+2
@@ -911,6 +911,7 @@ ifdef MSVC
911
NO_REGEX = YesPlease
912
NO_CURL = YesPlease
913
NO_PTHREADS = YesPlease
914
+ BLK_SHA1 = YesPlease
915
916
CC = compat/vcbuild/scripts/clink.pl
917
AR = compat/vcbuild/scripts/lib.pl
@@ -960,6 +961,7 @@ ifneq (,$(findstring MINGW,$(uname_S)))
961
UNRELIABLE_FSTAT = UnfortunatelyYes
962
OBJECT_CREATION_USES_RENAMES = UnfortunatelyNeedsTo
963
NO_REGEX = YesPlease
964
+ BLK_SHA1 = YesPlease
965
COMPAT_CFLAGS += -D__USE_MINGW_ACCESS -DNOGDI -Icompat -Icompat/fnmatch
966
COMPAT_CFLAGS += -DSTRIP_EXTENSION=\".exe\"
967
COMPAT_OBJS += compat/mingw.o compat/fnmatch/fnmatch.o compat/winansi.o