From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Mike Hommey <mh@glandium.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Jeff Hostetler <jeffhostetler@github.com>,
Johannes Sixt <j6t@kdbg.org>
Subject: Re: [PATCH] Use lowercase includes for some Windows headers
Date: Fri, 14 Jul 2023 10:07:19 -0700 [thread overview]
Message-ID: <xmqqv8empgl4.fsf@gitster.g> (raw)
In-Reply-To: <xmqqmt14a36k.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 12 Jun 2023 12:30:43 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Mike Hommey <mh@glandium.org> writes:
>
>> When cross-compiling with the mingw toolchain on a system with a case
>> sensitive filesystem, the mixed case (which is technically correct as
>> per the contents of MS Visual C++) doesn't work (the corresponding mingw
>> headers are all lowercase for some reason).
>>
>> Signed-off-by: Mike Hommey <mh@glandium.org>
>> ---
>> compat/win32/trace2_win32_process_info.c | 4 ++--
>> wrapper.c | 2 +-
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> ... The only possible breakage I can think of is if
> different versions of mingw toolchain have these header files in
> different cases---those who have been happily using header files
> like <tlHelp32.h> on their case sensitive filesystem now will find
> their build to fail. Theoretically, those who _corrected_ their
> header files to mixed case themselves (as it is "technically correct
> as per the contents of MS Visual C++") will be broken the same way,
> but they should be capable of diagnosing and recovering from such a
> breakage, so I'm not worried about that.
>
> Appreciate input from those who builds with mingw toolchain, but in
> the meantime let me queue it on 'seen' so that we won't forget.
And a month has passed. Unless I hear objections, I'll merge this
change to 'next' in a few days at most.
Thanks.
>
> Thanks.
>
>
>
>
>
>> diff --git a/compat/win32/trace2_win32_process_info.c b/compat/win32/trace2_win32_process_info.c
>> index a4e33768f4..438af8f818 100644
>> --- a/compat/win32/trace2_win32_process_info.c
>> +++ b/compat/win32/trace2_win32_process_info.c
>> @@ -3,8 +3,8 @@
>> #include "../../repository.h"
>> #include "../../trace2.h"
>> #include "lazyload.h"
>> -#include <Psapi.h>
>> -#include <tlHelp32.h>
>> +#include <psapi.h>
>> +#include <tlhelp32.h>
>>
>> /*
>> * An arbitrarily chosen value to limit the size of the ancestor
>> diff --git a/wrapper.c b/wrapper.c
>> index 67f5f5dbe1..5dc48e815a 100644
>> --- a/wrapper.c
>> +++ b/wrapper.c
>> @@ -17,7 +17,7 @@ static intmax_t count_fsync_hardware_flush;
>> #ifdef HAVE_RTLGENRANDOM
>> /* This is required to get access to RtlGenRandom. */
>> #define SystemFunction036 NTAPI SystemFunction036
>> -#include <NTSecAPI.h>
>> +#include <ntsecapi.h>
>> #undef SystemFunction036
>> #endif
prev parent reply other threads:[~2023-07-14 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 21:19 [PATCH] Use lowercase includes for some Windows headers Mike Hommey
2023-06-12 19:30 ` Junio C Hamano
2023-07-14 17:07 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqv8empgl4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=jeffhostetler@github.com \
--cc=johannes.schindelin@gmx.de \
--cc=mh@glandium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.