GCC doesn't find relative includes when passed paths using backward-slashes
Hans-Bernhard Bröker
HBBroeker@t-online.de
Sun Jan 15 13:51:36 GMT 2023
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.
More information about the Cygwin
mailing list