public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ralph Hempel <rhempel@bmts.com>
To: cygwin@cygwin.com
Subject: Re: RFD: cygwin + *native* MinGW compiler
Date: Wed, 28 Jan 2009 15:15:00 -0000	[thread overview]
Message-ID: <49806DF7.9060606@bmts.com> (raw)
In-Reply-To: <497FC147.306@cwilson.fastmail.fm>

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:

<snip>

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/

  parent reply	other threads:[~2009-01-28 14:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  4:38 Charles Wilson
2009-01-28  5:29 ` Christopher Faylor
2009-01-28  6:14 ` Warren Young
2009-01-28  6:55 ` Greg Chicares
2009-01-28  7:18   ` Charles Wilson
2009-01-28  9:05     ` Yaakov (Cygwin/X)
2009-01-28 11:10       ` Charles Wilson
2009-01-28 11:21         ` Yaakov (Cygwin/X)
2009-01-28 15:19       ` Christopher Faylor
2009-01-28 23:08     ` Greg Chicares
2009-01-29  9:44       ` Charles Wilson
2009-02-11  2:34         ` Greg Chicares
2009-01-28 15:15 ` Ralph Hempel [this message]
2009-01-28 15:18   ` Vincent R.
2009-01-28 15:26     ` Christopher Faylor
2009-01-28 16:08 ` Roger Wells
2009-01-28 16:40 ` Claude Sylvain
2009-01-28 17:22 ` Reini Urban
2009-01-28 23:47 ` Kai Raphahn
2009-01-29  9:52 Danny Smith
2009-01-29 12:29 ` Charles Wilson
2009-01-29 15:13   ` Charles Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49806DF7.9060606@bmts.com \
    --to=rhempel@bmts.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).