From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: GCC doesn't find relative includes when passed paths using backward-slashes
Date: Sun, 15 Jan 2023 14:51:36 +0100 [thread overview]
Message-ID: <b794f3d3-d197-80a2-c16a-00d1d61dd097@t-online.de> (raw)
In-Reply-To: <c593e554-d8ac-a0e5-96c0-c54fe9db633e@grundis.de>
Am 15.01.2023 um 13:38 schrieb Alexander Grund via Cygwin:
> The build system, finding it is running on Windows, will pass paths with
> backward slashes to the compiler.
And that's wrong. Cygwin is not, for practical intents and purposes,
Windows. It just runs on top of it.
Yes, backslashed path names do work in some cases on Cygwin (note that
in the case at hand, you did have to "" around the name for that to
work). But at some point that idea has to be given up to achieve the
primary goal of emulating a Unix-like environment.
The correct solution thus becomes "Don't do that, then." Fix the build
system detection to recognize Cygwin as a type of Unix, and things will
almost certainly just work.
next prev parent reply other threads:[~2023-01-15 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:38 Alexander Grund
2023-01-15 13:51 ` Hans-Bernhard Bröker [this message]
2023-01-15 14:21 ` Thomas Wolff
2023-01-15 16:23 ` Achim Gratz
2023-01-16 23:42 ` Dan Harkless
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=b794f3d3-d197-80a2-c16a-00d1d61dd097@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.com \
/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).