Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com X-Authentication-Warning: rachel.vtab.com: jojo set sender to jojo@virtutech.se using -f To: "David Carter" Cc: Subject: Re: Up-to-date info on '-mno-cygwin' vs. Mingw32 References: <000501c13210$54396e40$6401a8c0@atl.mediaone.net> From: Jesper Eskilson Organization: Virtutech AB Date: 31 Aug 2001 16:34:43 +0200 In-Reply-To: <000501c13210$54396e40$6401a8c0@atl.mediaone.net> ("David Carter"'s message of "Fri, 31 Aug 2001 07:30:16 -0400") Message-ID: Lines: 18 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii "David Carter" writes: > While you could use the mingw compiler & linker with cygwin, as > recommended by some on the web, by placing them ahead of the cygwin > tools in your path, you are almost certain to run into issues with > dos/windows file paths vs. unix-style paths. Since our build-environment is already adapted to use other non-cygwin compilers (such as Visual C++ and Intel C), this is not a real problem. We wrap all non-cygwin programs in a script which does all the conversions for us. /Jesper -- ------------------------------------------------------------------------- Jesper Eskilson jojo@virtutech.se Virtutech http://www.virtutech.se ------------------------------------------------------------------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/