delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=0.6 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,URI_HEX |
X-Spam-Check-By: | sourceware.org |
Date: | Tue, 28 Aug 2012 23:15:56 -0700 (PDT) |
From: | thoni56 <thomas AT junovagen DOT se> |
To: | cygwin AT cygwin DOT com |
Message-ID: | <1346220956451-92378.post@n5.nabble.com> |
In-Reply-To: | <1346220462071-92376.post@n5.nabble.com> |
References: | <1346220462071-92376 DOT post AT n5 DOT nabble DOT com> |
Subject: | Re: 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-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 |
thoni56 wrote > > 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. > I forgot to add that it is really this .d thing that makes it problematic. The makefiles generate separate subdirectories for various targets and also sets CFLAGS, CC, LINK et al. differently to allow different settings (and compilers, was my theory) for the different targets. Since mingw32-gcc and gcc generates .d files in incompatible formats (gcc really doesn't like "c:\..." in its .d files...) and those are included in the make file, even using different make:s does not solve the problem for me. Any ideas? -- View this message in context: http://cygwin.1069669.n5.nabble.com/mingw32-gcc-and-posix-paths-tp92376p92378.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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |