DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D3EB6385800C
Message-ID: <b794f3d3-d197-80a2-c16a-00d1d61dd097@t-online.de>
Date: Sun, 15 Jan 2023 14:51:36 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
Subject: Re: GCC doesn't find relative includes when passed paths using
 backward-slashes
To: cygwin@cygwin.com
References: <c593e554-d8ac-a0e5-96c0-c54fe9db633e@grundis.de>
Content-Language: de-DE
In-Reply-To: <c593e554-d8ac-a0e5-96c0-c54fe9db633e@grundis.de>
Precedence: list
From: =?utf-8?q?Hans-Bernhard_Br=C3=B6ker_via_Cygwin?= <cygwin@cygwin.com>
Reply-To: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker@t-online.de>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

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.


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple