DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B131F3858D32
Message-ID: <573d1c7c-5b09-766e-3203-7fac7104376c@towo.net>
Date: Sun, 15 Jan 2023 15:21:39 +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>
 <b794f3d3-d197-80a2-c16a-00d1d61dd097@t-online.de>
In-Reply-To: <b794f3d3-d197-80a2-c16a-00d1d61dd097@t-online.de>
UI-OutboundReport: notjunk:1;M01:P0:ZnjZ1FVA+ug=;f6HtLavHHQDy0eVTkLtC/YqTl6D
 ge1YBmNIQJT6HZX8JtLjx/D4LWJV+rDENLMWwJthj2E7WVC1WWuK4nOVx1u09AzyhT6DcNvVR
 4IM8uiWhO7ZQEJHXPpjW3la5du2ZwS/j0jdlaAOEogRxSgSx/MaGbxbH1JA5gcEgFyo/qupKP
 xIDqyN1uVPBuhHTnSZtsKlSbWwvat8ZSo61qkVlpxGuyTnRd3KvDP5/NPg002Vh4rBrvTgwF/
 atf1b3+ye1M47FiB3RsgiPC+ctyB8GpGlH7+AFH19uztzatf5nKac6qMetWhXu7LAIGXkxNvt
 3wHq49/aWbrSus8Wn3jDwQ9Yaq+QiXcODyZwbhAK8XNsjVSQlkt8m4YM+UHXaJkiZ9i9se934
 KFOR2eNwtKMDdxtKx44g9bmNZZn4XTdwBuyrgfNFtwla7NWAqV40fca7HPo2jN0k2sKMx8n8u
 rP/c+4ZAGyZY5fK935JtZ8U2IpXUNra4gL3hCZN2OUqerhk1Q0XWr011YKnjHT2IPXVbJ5nMj
 pMWm9OHdjuKm7D5iJ2+eNZ6xxhtB2VohUKvnYoQHQQIKpOyVMlbRpbxCW6QbigtNx6ppsM1g1
 77eUgdPaNAR5DeiRdBv+12ydJhyP6lATZloz0hGw+F9qKCL3fivLrSMEHH1oQUCrV4QwBkLLM
 nR06NUADhEH6aQhW6L1JTcdnXyjiIuU3IqLu/jqJMw==
From: Thomas Wolff via Cygwin <cygwin@cygwin.com>
Reply-To: Thomas Wolff <towo@towo.net>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit


Am 15.01.2023 um 14:51 schrieb Hans-Bernhard Bröker via Cygwin:
> 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.
>
>
It also depends on how your application, in this case gcc or rather cpp, 
handles path names.
If it uses library functions dirname and basename, it should work as you 
expect, but maybe it looks for '/' itself, so you cannot expect all 
applications to be patched for cygwin/Windows pathname support.

-- 
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