Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
To:	cygwin AT cygwin DOT com
Subject:	Re: Problems exporting my DLL functions...
References:	<3D62A993 DOT AC202DD5 AT gmx DOT net>
From:	Andreas Ames <andreas DOT ames AT Tenovis DOT com>
In-Reply-To:	<3D62A993.AC202DD5@gmx.net>
Date:	21 Aug 2002 10:44:47 +0200
Message-ID:	<un0rgtxc0.fsf@tenovis.com>
Lines:	21
User-Agent:	Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version:	1.0

Hi,

Lostmind <lostmind AT gmx DOT net> writes:

> 2. How do I tell the compiler/linker which functions I want to export (I
> marked them with EXPORT in the file already, but they didn't seem to be
> available in the created DLL)

an alternative way to EXPORT and --export-all-symbols is to create a
.def file with all the functionnames you want to expose to your users
and link this .def file as the very first file before any .o and .a;
see the ld-docu for command line option 'shared' for more details.

The only thing I can't figure out is how to prevent ld from
additionaly exporting all global variables in the .o an .a files.  Can
anyone more knowledgable give me a hint?


TIA,

andreas

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

- Raw text -