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
Date: Wed, 7 Jul 2004 18:35:19 +0200
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Reply-To: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Organization: Esse keine toten Tiere
Message-ID: <441249594902.20040707183519@familiehaase.de>
To: Maarten Boekhold <boekhold AT emirates DOT net DOT ae>
CC: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: Building DLL
In-Reply-To: <40EC1ECB.2010700@emirates.net.ae>
References: <40EC1ECB DOT 2010700 AT emirates DOT net DOT ae>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit

Maarten wrote:

> Hi all,

> Now that GTK2 is in the package tree, I thought I'd give building XFCE a
> try. This package depends on 'Disk based hashes' (dbh), which needs to
> be built as a shared library. Dbh uses libtool in its build process.

> Of course this complains with

>         libtool: link: warning: undefined symbols not allowed in
>         i686-pc-cygwin shared libraries

> As far as I know, to get this to build I need to create a .def file, and
> somehow include this in the libtool invocation.

> Are there some general hints to determine which functions/symbols need
> to be included in this .def file, and how to modify the libtool 
> invocation to use this file?

You don't need .def files on Cygwin.  Just add -no-undefined to
libxyz_LDFLAGS.


Gerrit
-- 
=^..^=                                     http://nyckelpiga.de/donate.html


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