DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 575JwI9R2239160
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 575JwI9R2239160
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=Kyfva59C
X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 163FF385843E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1754423897;
	bh=fDnIYhziWyOSVQ1o+e6PBhU0F+5TPyCQ+dIQCkRFjDE=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=Kyfva59CK/Sq7qeT8IhLjkIQiZp4QTOhcP6ti9XoW3uGEPDZNtlbs8MbS/qQYd1ju
	 dqdot7bUetKJraSZKJtVj95dS3kW1MzWCE5O7KFJWUm5REb9Wv3qx0ciz6enPU/gP/
	 hOSRPay6VWi3n1nLwwi5SREQEpBtdBfnaAQ84l0Y=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9E5B93858D29
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 9E5B93858D29
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754410139; cv=none;
 b=pA3RpisIxkhg2fpMIfg36Zk+QPBQYRqyrqWJ2XiMUo+y32j4kslYMJK2WMW+rQH/7sztEoOGtWJEXc8EZDP6U0VuSbfZv2gjH0JJZp1CZrqqLjAwlnGFsK9W3rT/UA2lGjbH2yvk49RQ1I4dqhPeB8s9ZA6EV+QuQqgxmiqBhMA=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1754410139; c=relaxed/simple;
 bh=Ly8/2rMpgSN6S4xxwoLUnbirEzKjCy/SeassbQ9otE8=;
 h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature;
 b=lkFfGfN0ZK1fnyItfnoqtmssuQYCy71oDYDmvJZ8ZaR/gt+V4Von5JcsOkpDo2SkGIZtMSzGYcdGJrEQwL1shraaS6nzYuglZbjD3m6CKWMUgtvwSJw+bLlMaAIu6/IosU4QWTGtWOGSrH8c9oQkF2KkMMcrU3VsyxP021gb7Qs=
ARC-Authentication-Results: i=1; server2.sourceware.org
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9E5B93858D29
Message-ID: <4ef0fbf6-8964-491b-984d-1f48bd1aa831@SystematicSW.ab.ca>
Date: Tue, 5 Aug 2025 10:08:56 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Incorrect command line handling when launching Cygwin program
 from Windows
Content-Language: en-CA
To: cygwin@cygwin.com
References: <AS8PR03MB75397FE89A3DCFFC91CE69728D23A@AS8PR03MB7539.eurprd03.prod.outlook.com>
 <87264da9-cc87-4a63-89cb-e30fc6c1126b@emrich-ebersheim.de>
 <AS8PR03MB75396CC142A61B34B50886648D23A@AS8PR03MB7539.eurprd03.prod.outlook.com>
 <1489952594.20250804215103@yandex.ru>
 <AS8PR03MB7539C5C01FEBF975EF6001578D22A@AS8PR03MB7539.eurprd03.prod.outlook.com>
Organization: Systematic Software
In-Reply-To: <AS8PR03MB7539C5C01FEBF975EF6001578D22A@AS8PR03MB7539.eurprd03.prod.outlook.com>
X-Rspamd-Queue-Id: 962892F
X-Stat-Signature: r3uyem4bhqqgcuwtjznoy6chuy4mzw58
X-Rspamd-Server: rspamout06
X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361
X-Session-ID: U2FsdGVkX1/CkaBH9G2FKWMu8pjouei3mjVwCX9/CzA=
X-HE-Tag: 1754410137-507701
X-HE-Meta: U2FsdGVkX1+TkCQcu+fFbSS0wUD7QJfZ8UQfCLfdMi5Prd6uURENBZhAkjGaEIVtRionREPSNXRJbjrI+yXT2dIZplZe6eWPX/39/tbXbltC6p28KL5Z2eQPOBA6vQl7DOVtq0vncH71y6uQhzD2FC/qAniJIFFI9Ujla0gALeUIADd1s7iPauHy6894cNHDmA19NXnE/8v3b55o9rdzbOnVoXVlPelZ2fdtyA3lroCldzGKfOp+YrFB12uULPsq5+WcD6t4Fdry5uG/k7E08PPCC7uob3KaJnfVow+cJm1Z7/TSapbJ3pY36g5qkXCBG/MuOTBFTDXnXhvsb8d0fCP6iT3A64A5Gr/Ycq2tIWfB6pM3hfsvbniH9R9Amn7tlsrPQxK1FCVH9Of1FaUEicBqzRm3I7/+2SSSHx7vS7oEuh8eKNAe0Q==
X-BeenThere: cygwin@cygwin.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@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Brian Inglis via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 575JwI9R2239160

On 2025-08-05 02:44, Old, Oliver via Cygwin wrote:
> Hello Andrey,
> 
>> Then do not mix environments.
> 
> That is not my choice, but rather my supervisor's choice. I began
> engineering our new CMake-based build system purely with MinGW
> toolchains in mind, statically linked ones even since I already know how
> well-received it would be if I required people to install a MinGW
> environment and had them add it to their PATH.
> 
> Then I was told we might have to abandon this new system if we can't
> keep using our Cygwin toolchains.
> 
> I know it is very unwise to attempt this and entirely unproductive.
> 
>> Cygwin with automation scripts.
> 
> I wish that was good enough, but I'm supposed to make it work with all
> the GUI and integrated debugging capabilities the other toolchains have.
> It is so very frustrating.
> 
> Back to the technical aspects: I just don't see why the current command
> line handling is supposed to be good. I find it to be very surprising as
> its entire purpose is interfacing with non-Cygwin software. Why should

NO - its entire purpose is interfacing with Cygwin and other POSIX sosftware, 
including on other systems, from MS cmd if users insist, but according to POSIX 
rules! We now have only limited support for some non-POSIX text files.

> the "non-Cygwin" software assume the command line to be parsed according
> to Bash's rules?

It allows us to use tools based on POSIX standards, like terminals, shells, and 
utilities, under Windows, without running under a VM like WSL or alternatives, 
and with access to Windows filesystems, without *each* of us having to buy 
pieces of software which would work together,(Borland, 386^Max), or find and 
install a working toolchain, and build *each* GNU or BSD utility from sources 
*ourselves* (like news:comp.sources.…), as we used to have to do.

	https://cygwin.com/faq.html

	https://cygwin.com/:

"Get that Linux feeling - on Windows

"What...

...is it?

"Cygwin is:

• a large collection of GNU and Open Source tools which provide functionality 
similar to a Linux distribution on Windows.
• a DLL (cygwin1.dll) which provides substantial POSIX API functionality.

...isn't it?

"Cygwin is not:

• a way to run native Linux apps on Windows. You must rebuild your application 
from source if you want it to run on Windows.
• a way to magically make native Windows apps aware of UNIX® functionality like 
signals, ptys, etc. Again, you need to build your apps from source if you want 
to take advantage of Cygwin functionality."

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

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

