| commit | bb0e43d8a1ae8489071573c5323c28ed2935a354 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Thu, 4 Jun 2020 21:09:56 +0000 (4 21:09 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 4 Jun 2020 22:52:21 +0000 (4 15:52 -0700) | ||
| tree | 1162c924c1dc136f3bbaa173c4a66ffd0a57a476 | treesnapshot (tar.gz zip) |
| parent | 0573831950d02db0c2932708eadd9f765e5773a6 | commitdiff |
msvc: fix "REG_STARTEND" issue
In 897d68e7af82 (Makefile: use curl-config --cflags, 2020-03-26), we
taught the build process to use `curl-config --cflags` to make sure that
it can find cURL's headers.
In the MSVC build, this is completely bogus because we're running in a
Git for Windows SDK whose `curl-config` supports the _GCC_ build.
Let's just ignore each and every `-I<path>` option where `<path>` points
to GCC/Clang specific headers.
Reported by Jeff Hostetler in
https://github.com/microsoft/git/issues/275.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
In 897d68e7af82 (Makefile: use curl-config --cflags, 2020-03-26), we
taught the build process to use `curl-config --cflags` to make sure that
it can find cURL's headers.
In the MSVC build, this is completely bogus because we're running in a
Git for Windows SDK whose `curl-config` supports the _GCC_ build.
Let's just ignore each and every `-I<path>` option where `<path>` points
to GCC/Clang specific headers.
Reported by Jeff Hostetler in
https://github.com/microsoft/git/issues/275.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| compat/vcbuild/scripts/clink.pl | diffblobblamehistory |