Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: kulack AT us DOT ibm DOT com
X-Lotus-FromDomain: IBMUS
To: Cygwin List <cygwin AT sourceware DOT cygnus DOT com>
Message-ID: <85256900.0077DECA.00@D51MTA04.pok.ibm.com>
Date: Fri, 16 Jun 2000 16:49:23 -0500
Subject: Re: Can't build a DLL using gcc
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

Thanks Carl,
This solved my problem wonderfully, and your presentation of it was exactly
the type of
'hello world' that lets people be most productive!

I don't need (and can't conceive that I will need) to manage the order of
my DLL exports, but I've
kept the .DEF / export ordinality discussion in mind. Thanks again!

>   http://sourceware.cygnus.com/ml/cygwin/2000-06/msg00688.html
> This method is not only easier, but also allows you to maintain your
symbol
> information in one place-- the header files where they belong.  You don't
> have to try to keep separate .def files in sync.




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com