public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: David Brown <david.brown@hesbynett.no>
Cc: gcc-help@gcc.gnu.org
Subject: Re: [GCC][Windows] header file inclusion on windows
Date: Sat, 28 Jan 2023 12:38:54 -0500	[thread overview]
Message-ID: <CAF1jjLvDNTsjV44kKLOVi-83-kCHuJQo544C4CX8wydWkGT3eg@mail.gmail.com> (raw)
In-Reply-To: <tr3a0p$fkl$1@ciao.gmane.io>

On Sat, Jan 28, 2023 at 9:04 AM David Brown <david.brown@hesbynett.no> wrote:

> Another possibility is to run the compilation using a Cygwin
> environment, rather than more common mingw gcc builds.  Under Cygwin,
> filenames are case sensitive.

I vaguely recall that years ago, Windows had an option to make an
entire volume case sensitive as part of its posix compatibility
efforts.  Googling only reveals results related to a newer w10 option
to turn it on at a per-directory level.  Either of those options might
be useful here for the user.

      reply	other threads:[~2023-01-28 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  3:57 Mena Makary
2023-01-28 14:04 ` David Brown
2023-01-28 17:38   ` NightStrike [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=CAF1jjLvDNTsjV44kKLOVi-83-kCHuJQo544C4CX8wydWkGT3eg@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=david.brown@hesbynett.no \
    --cc=gcc-help@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).