X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Wed, 28 Jan 2009 16:05:55 +0100 From: "Vincent R." To: cygwin AT cygwin DOT com Subject: Re: RFD: cygwin + *native* MinGW compiler In-Reply-To: <49806DF7.9060606@bmts.com> References: <497FC147 DOT 306 AT cwilson DOT fastmail DOT fm> <49806DF7 DOT 9060606 AT bmts DOT com> Message-ID: X-Sender: forumer AT smartmobili DOT com User-Agent: RoundCube Webmail/0.2 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Wed, 28 Jan 2009 09:38:47 -0500, Ralph Hempel wrote: > 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. That is, incantations like this: > > > > I find myself bouncing around between cygwin and mingw because > each one helps me accomplish different tasks. > > I use the Cygwin environment (including vim) for the actual > software development of embedded systems, and to host the > different gcc flavours needed for each target processor. There's > lots of great tools ready to go, and it's now possible > to drive the install from the command line, which makes it > easy to reproduce a specific workstation configuration. > > Occasionally, I want to compile special tools that I can > redistribute without source, so I use mingw for that. > > I have a build framework for embedded systems that I use for > all my projects - even PC based ones. If I'm compiling third > party software that comes with a makefile or autoconf script > then I'll use that. > > Once you start designing makefiles that have to work with > multiple compiler versions and flags and include and library > paths, it gets complicated very quickly :-) > > One reason I have not tried to drive the native MinGW compiler > is because of the path issues for includes and libraries. I > was worried that Cygwin includes and libraries would accidentally > get referenced. > > Ralph > > -- > 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/ Actually I am using cygwin because there are many packages, adn a good installer but I will switch completely to mingw if I could get the same. Couldn't be possible to share more things between the two projects ? I mean for instance share the cywgin installer that could allow people to install cygwin and mingw on two different places to avoid lib/path issues. For instance : C:\gnu\cygwin C:\gnu\mingw C:\gnu\home They could share for instance the same home directory ... Last time I tried to compile something with cygwin targeting mingw it just failed... -- 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/