X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org AD9973898032
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=cs.umass.edu
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=moss AT cs DOT umass DOT edu
Subject:	Re: g++ and c++17 filesystem
References:	<861bc601-876b-e16d-d4f7-0bb543d61d8e AT cs DOT umass DOT edu>
	<FD1969EA-9204-4986-BE5E-0C9F45D256B7 AT gmail DOT com>
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID:	<d3a237ab-d237-bc16-ca1c-48337dc6bff8@cs.umass.edu>
Date:	Wed, 18 Nov 2020 18:47:05 -0500
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.12.1
MIME-Version:	1.0
In-Reply-To:	<FD1969EA-9204-4986-BE5E-0C9F45D256B7@gmail.com>
X-Spam-Status:	No, score=-2.4 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
	KAM_DMARC_STATUS, MISSING_HEADERS, NICE_REPLY_A, RCVD_IN_DNSWL_LOW,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
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>
Reply-To:	moss AT cs DOT umass DOT edu
Cc:	cygwin AT cygwin DOT com, =?UTF-8?Q?Ren=c3=a9_Berber?= <rene DOT berber AT gmail DOT com>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 0AINlcTl020902

On 11/18/2020 4:18 PM, Kristian Ivarsson wrote:
> 
>> I would agree that if you want an executable that acts and feels more like a Windows native application, then mingw is probably what you want.  Cygwin is if you want something that acts and feels more like a Posix thing ... which means it will be oriented to Posix style paths.
> To be able to use mingw all the code have to be ported to use Windows native mechanisms and then we might just use MSVC instead
> 
> We don’t want (either) Windows-style-paths or Posix-style-paths, we want A path and expect it to work equally regardless of what platform is used in regards to std::filesystem
> 
> As far as I see, very few applications do form their own - and/or have hard-coded absolute paths and instead they are usually input data (through UI, configuration, OS, environment or such)

IN this context, I would say "Which std::filesystem?  The Cygwin Posix-like one or the mingw 
Windows-like one?"  If you want uniformity, I'd go with Cygwin; it you want platform-like behavior, 
then mingw.

Best wishes - EM
--
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

- Raw text -