X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <497FCA86.8020101@etr-usa.com> Date: Tue, 27 Jan 2009 20:01:26 -0700 From: Warren Young User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Cygwin-L Subject: Re: RFD: cygwin + *native* MinGW compiler References: <497FC147 DOT 306 AT cwilson DOT fastmail DOT fm> In-Reply-To: <497FC147.306@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Charles Wilson wrote: > Pursuant to a discussion on the libtool list, I'm trying to get a feel > for how many cygwin users rely on the cygwin environment to drive the > *native* MinGW gcc compiler. I do half of what you're asking: use Cygwin's bash shell as an environment to drive mingw32-make on MinGW-specific Makefiles. I posted here how I manage the PATH issues and such that you touch on: http://www.cygwin.com/ml/cygwin/2008-05/msg00092.html I do this only for MySQL++, a library I maintain, which targets MinGW among many other platforms. I use the MinGW sub-environment described above only as long as I need to do some test or fix for MinGW, then pop back out into a normal Cygwin environment. MySQL++ uses Bakefile to build the MinGW makefile, however, so I don't know how relevant my experience is to you. Bakefile more or less replaces libtool and automake, allowing easier porting to non-POSIX platforms. Thus, my use of Cygwin to drive the MinGW toolchain is limited to using bash as an alternative to the MinGW Prompt you get on installing MinGW. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/