Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Mon, 26 Sep 2005 21:38:45 +1200
From: Danny Smith <dannysmith@clear.net.nz>
Subject: Re; Visibility of compiler symbols between executables and DLLs
To: nick.glencross@gmail.com
Cc: Cygwin <cygwin@cygwin.com>
Reply-to: Danny Smith <dannysmith@users.sourceforge.net>
Message-id: <000f01c5c27e$181319e0$e66d65da@DANNY>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit

Nick Glencross wrote:

> On many platforms compilation symbols in an executable are not made
> visible to its Shared Library/DLLs by default, but this can often be
> overridden with a compiler flag to change the policy. My question in a
> nutshell then is whether cygwin has the ability to have a DLL access a
> global variable within the executable that loads it? As an obvious
> follow on, if yes, then how do you go about doing it?
>

http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/mingw/samples/dlltest/?c
vsroot=src

has an old example (ca 1998). You can find more recent examples, using
'gcc -shared' rather than dlltool, in
cygwin archives.
Danny



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

