X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.7 required=5.0 tests=AWL,BAYES_05,URI_HEX
X-Spam-Check-By:	sourceware.org
Date:	Tue, 28 Aug 2012 23:07:42 -0700 (PDT)
From:	thoni56 <thomas AT junovagen DOT se>
To:	cygwin AT cygwin DOT com
Message-ID:	<1346220462071-92376.post@n5.nabble.com>
Subject:	mingw32-gcc and posix paths
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I'm in the process of going from gcc3 to gcc4. For one project I need to
build both cygwin and win32 executables so "-mno-cygwin" to "mingw32-gcc"
was an initial hurdle.

However that is now sorted out, but one thing puzzles me. If the mingw32 is
a cygwin cross-compiler why does it not accept paths in the host format
(meaning cygwin, posix)? To me this seems very natural. Maybe  I'm biased,
but I see no other tools do that, expecting the command line to have the
format of the *target*.

mingw32-gcc also produces .d files in its native format by the way.




--
View this message in context: http://cygwin.1069669.n5.nabble.com/mingw32-gcc-and-posix-paths-tp92376.html
Sent from the Cygwin list mailing list archive at Nabble.com.

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

- Raw text -