DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 574J6BLv1711112
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 574J6BLv1711112
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=aGa0jojn
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8E7E93857348
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1754334370;
	bh=VmiCrJaKab6KcT3N8SurnJMl2sA9+QrkEr2Z4qZzjK8=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=aGa0jojn4AX1R/bF5gRJ64YQATYsdx1kO02hRUemfhjrYayKTE6iaHdQA5mvWNBvE
	 LSthw3Sx3oZZ9IVNEu87gxZ9zJZjSE7BoKixB2SlpXZG5GcQL5/LL5kaHwXjsSiW2l
	 2H6Lz8FgllmS4g1C559aM063YWMQ9J0W2U0dGB2s=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8416E3858D1E
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8416E3858D1E
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754334304; cv=none;
 b=WstzjOJf9IirCEStUp0/UGJB/HORKNgzo53tSTSgkTcibGealC8IpBZRMSkJVuUEwzX9l4ay3NlGAtQHC4gqSUi9/cPbvJiQamO9RUrMGdUH5waaQX1ty24kw9n7npv6rutFDM7zWdmGc3KVeO8/oVX44hRjEJBvJ0e5mzAaEvc=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1754334304; c=relaxed/simple;
 bh=eaxiOxrN1FZk0VRcNE+AOqo07NLhrMZfB7CJi4Q1pvw=;
 h=DKIM-Signature:Date:From:Message-ID:To:Subject:MIME-Version;
 b=Q/nY51WeiwnsgiZ8FW+EChKkgQZ1AWNOlpYNm6Kzj0upPrsMPbZ5SSlGHBYq6hF1g3A564i43ZoeVPkHKj23mwUlDbLunziJ2wRMpSC7ov82sZjrcQ//dk4NjPXnk37cbQKBULU0K4S9Hy+oRBp3YleNdMLYTossYjYVmxWUedU=
ARC-Authentication-Results: i=1; server2.sourceware.org
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8416E3858D1E
X-Yandex-Fwd: 1
Date: Mon, 4 Aug 2025 21:51:03 +0300
X-Mailer: The Bat! (v9.3.4) Professional
Message-ID: <1489952594.20250804215103@yandex.ru>
To: "Old, Oliver" <Oliver DOT Old AT loewen DOT de>, cygwin AT cygwin DOT com
Subject: Re: Incorrect command line handling when launching Cygwin program
 from Windows
In-Reply-To: <AS8PR03MB75396CC142A61B34B50886648D23A@AS8PR03MB7539.eurprd03.prod.outlook.com>
References: <AS8PR03MB75397FE89A3DCFFC91CE69728D23A AT AS8PR03MB7539 DOT eurprd03 DOT prod DOT outlook DOT com>
 <87264da9-cc87-4a63-89cb-e30fc6c1126b AT emrich-ebersheim DOT de>
 <AS8PR03MB75396CC142A61B34B50886648D23A AT AS8PR03MB7539 DOT eurprd03 DOT prod DOT outlook DOT com>
MIME-Version: 1.0
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Andrey Repin via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Andrey Repin <anrdaemon AT yandex DOT ru>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

Greetings, Old, Oliver!

>> Why don't you use the cygwin cmake?

> We want to use VS Code to work with the project. It doesn't like
> Cygwin's CMake. It would also interfere with the clangd language server
> since that reads from CMake's compile_commands.json which contains the
> command line as it would be used within the shell.

Then do not mix environments.
I.e. use windows native tools with VS Code, and Cygwin with automation scripts.

> I know the next question: Why are you not using a MinGW toolchain if all
> you do is cross-compile for a different target anyways?

> Sorry for the long paragraph. TL;DR: Management.

> I didn't want to, but was forced to because, this is approximately the
> reasoning I was given, "we can't prove that the Cygwin GCC toolchain and
> the MinGW toolchain will produce the same code and we can't tolerate any
> differences between our currently 'maintained' Cygwin toolchain and the
> 'experimental and untested' MinGW toolchain". Indeed, for some reason,
> the layout of the binary contents, and consequently the addresses
> referencing them, differ. I'm guessing it's because of path ordering
> within archives or something like that. The generated instructions,
> unsurprisingly, are the same, at least for the functions I've diffed.
> Nothing I said could sway my manager, so I spent a week working on this,
> first having to track down a bug that livelocked GCC (it was the "Ninja
> 0-byte pipe" bug, that was fixed in Cygwin 3.6.1, but our checked in
> version was of course 3.6.0), then having to figure out why the command
> line is interpreted weirdly and working around that (custom launcher +
> undocumented CMake feature).

I think I've answered the question already.


-- 
With best regards,
Andrey Repin
Monday, August 4, 2025 21:49:29

Sorry for my terrible english...


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