Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <151f01c196fb$69c39e70$0200a8c0@lifelesswks> From: "Robert Collins" To: "J. Henning Schwentner" , References: Subject: Re: Compiling apps to Mingw32 with cygwin Date: Mon, 7 Jan 2002 08:45:08 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 06 Jan 2002 21:47:08.0535 (UTC) FILETIME=[B081F870:01C196FB] ----- Original Message ----- From: "J. Henning Schwentner" To: Sent: Monday, January 07, 2002 12:57 AM Subject: Re: Compiling apps to Mingw32 with cygwin > Thanks for your quick help, this works nice! > > But, it is a bit difficult. I think ideally configure should detect > --host=mingw32 --build=cygwin and in this case should add --mno-cygwin to > CFLAGS and CPPFLAGS (and do something to fix libtool). Why? That would prevent compiling with a cygwin target. --host and --build and --target are _user_ switches. configure should never alter those. As for detecting -mno-cygwin, you can use a variation of the AC_API_WIN32 Macros' I posted to the autoconf list some time back - but only do that when you've checked the host platform is actually mingw32. > I am not sure if this is a bit off topic, maybe this sould be posted to the > autoconf list. It's in the grey area, still related to cygwin, but heading to autoconf only pretty quickly. Rob -- 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/