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
Message-ID: <dcb629180509260139f2440c1@mail.gmail.com>
Date: Mon, 26 Sep 2005 09:39:02 +0100
From: Nick Glencross <nick DOT glencross AT gmail DOT com>
Reply-To: Nick Glencross <nick DOT glencross AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Visibility of compiler symbols between executables and DLLs
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j8Q8dMmP015854

Guys,

I've done some research on this and don't believe that it's a
perennial question that keeps coming up!

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?

Everything that I've seen indicates that this isn't possible, due to
limitations imposed by DLLs, but would appreciate believing this with
a bit more confidence,

Thanks in advance,

Nick

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