X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<48729DA8.A61ECE0E@dessent.net>
Date:	Mon, 07 Jul 2008 15:50:16 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: DEF files
References:	<E1KFyRX-000FYO-00 DOT assignator-mail-ru AT f168 DOT mail DOT ru>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Konstantin Gorskov wrote:

> Hi! I have build shared dll libs with cygwin , is there any command for auto-generating *.def files for them?

You can have the linker create the .def file as a side effect of linking
the DLL with --output-def (so, -Wl,--output-def,filename from gcc) just
as you can create the import lib in a similar way.  But really, what's
the point?  A def file is generally only useful when you want fine
grained control of what's being exported, and if you autogenerate it in
this way it's just duplicating existing information, it's not being used
to control what's exported.  And if you don't need fine grained control
then you certainly don't need .def files, i.e. creating a DLL is just a
matter of "gcc -shared foo.o bar.o -o filename".

Brian

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

- Raw text -