Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <42004CBC.2050408@cwilson.fastmail.fm>
Date: Tue, 01 Feb 2005 22:45:00 -0500
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Problems creating "-mno-cygwin" DLLs with libtool.
References: <030801c50873$a0dd3500$e6ec6f83 AT robinson DOT cam DOT ac DOT uk> <NUTMEG3H9Fouml2dx88000003dc AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <20050201172639 DOT GH4911 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20050201172639.GH4911@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:

> Has it been established that the cygwin version of libtool is *supposed*
> to handle mingw?  I'd be rather surprised if that was a goal.

DING! We HAVE a winner!

The installed libtool has been configured -- by virtue of the fact that 
I ran the build in a cygwin environment -- to understand cygwin's 
minutia.  It is not intended to work with mingwgcc OR with 'cygwingcc 
-mno-cygin'.

If you want an out-of-box libtool that works with mingwgcc, then use the 
libtool package distributed by the msys/mingw project.

AFAIK, it is not supported to build-your-own libtool with CC=cygwingcc 
-mno-cygwin ... but it might work.  You'd need to do one of the following:

(1) download the whole libtool source package, and 
configure/build/install with CC=...-mno-cygwin, CXX=...-mno-cygwin, etc. 
  Then try to use THAT libtool from your project.

or

(2) don't call libtool yourself as a platform build tool; instead 
"libtoolize" your project so that as part of your own project's build 
process it creates its own local libtool (benefit: this local libtool 
will use EXACTLY the same settings the rest of your project's build does)

If you're already doing #2, see note above concerning "-mno-cygwin not 
supported".

 >
 > OTOH, I never have understood why tools insist on including such 
things as
 > "-lcygwin" or "-lc" on a linker command line.

There's a good reason for libtool to do so, but it escapes me at the 
moment.  Trust Me(tm).

--
Chuck

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