Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Jon Leichter" <jon AT symas DOT com>
To:	"Earnie Boyd" <earnie_boyd AT yahoo DOT com>
Cc:	<hschwentner AT yahoo DOT com>, <cygwin AT cygwin DOT com>,
	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Subject:	RE: Compiling apps to Mingw32 with cygwin
Date:	Mon, 14 Jan 2002 10:29:01 -0800
Message-ID:	<DLEBJKNCNLJEDKMKICHGAECICCAA.jon@symas.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To:	<3C42E078.779D2FAA@yahoo.com>
Importance:	Normal

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Earnie Boyd
> Sent: Monday, January 14, 2002 5:43 AM
> To: Robert Collins
> Cc: Jon Leichter; hschwentner AT yahoo DOT com; cygwin AT cygwin DOT com
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> You need to narrow your thinking to GCC and binutils the processes of
> consequence.  You only need to specify the triplet because config.guess
> guesses wrong based on the value of `uname -s'.  The cygwin binutils as
> named will produce executables that use MSVCRT.DLL instead of
> CYGWIN1.DLL without having to do anything special with their names or
> output.  So, my statement stands based on what happens with GCC, you're
> switching the build environment.
>

Earnie,

According to GNU documenation, the following utilities are a part of
binutils:

	ar, nm, objcopy, objdump, ranlib, readelf, size, strings,
	strip, c++filt, cxxfilt, nlmconv, windres, dlltool

Which of these utilities "produces executables that use MSVCRT.DLL"? I don't
think any of them do. The binutils package that distributes with Cygwin
(which is what I use) are Cygwin binaries; they are dependent on
CYGWIN1.DLL. They're also all quite happy to operate on MinGW binaries.

GCC, of course, is a suite of tools (the only set, I believe) that generates
MinGW binaries (if, of course, the -mno-cygwin switch is specified). All
Cygwin GCC tools are STILL Cygwin binaries themselves; they all depend on
CYGWIN1.DLL.

I tend to agree with Robert's point of view. It seems to me that the "build"
environment is Cygwin.

In my mind, the only compelling reason NOT to use Cygwin as the "build"
value is because (with an up-to-date autoconf), the configure script would
NOT test executables if it were set to Cygwin. This condition may or may not
hurt the project builder. Thus, it still comes down to whichever build value
works best for the project builder.

Jon


--
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/

- Raw text -