Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BAE49E2.7080708@ece.gatech.edu>
Date: Sun, 23 Sep 2001 16:45:22 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: Stephen Dyke <sk DOT ml AT btinternet DOT com>
CC: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>,
        cygwin <cygwin AT cygwin DOT com>
Subject: Re: GetModuleHandleA AT 4
References: <3BAD12EA DOT 30290 DOT 3EA67560 AT localhost> <002c01c143ab$501470b0$0149a8c0 AT sknet01> <08f701c143f5$d8336560$0200a8c0 AT lifelesswks> <004401c1442e$93973830$0149a8c0 AT sknet01> <0b5701c14432$ff513450$0200a8c0 AT lifelesswks> <000b01c1443d$8aec99a0$0149a8c0 AT sknet01>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


 >>>> I'm a little confused here. What's so complex about gcc -o
 >>>> foo.dll -shared foo.c ?

 >
 > I am not planning on changing ld, but I am planning to release a set of
 >  script to build dlls, using nothing more than the available tools
 > and the source for the dll. Expect a beta soon! :)


If I may interject here, this @!#$^!$ pisses me
off.  I, along with DJ, Chris, Robert, Ralf, Paul, etc, have been
working for over a year now trying to make the process of building DLLs
on cygwin 'streamlined' -- so that you DON'T have to use wacky scripts
to build them.  It *ought* to just work like building shared libraries
onUnix.  We've been patching and testing and releasing new versions of
binutils and gcc since June 00 -- mostly aimed at improving the DLL
experience.

The "available tools" are NOT fixed in stone.  They are constantly 
changing -- there is room for additional patches if you've found 
problems in "the available tools".

If 'gcc -shared' doesn't build a proper DLL -- IT IS A BUG.  *Don't*
recommend workarounds, or scripts to avoid or otherwise step over these
BUGS.  Help us find them and squash them!

Personally, I will view your scripts as a bug report -- "here is what is
wrong -- I have to do X in order to get a working DLL"

--Chuck


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