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: <4166DB2D.CAC35F2C@dessent.net>
Date: Fri, 08 Oct 2004 11:23:41 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Plugins and referencing *variables* in the loading program
References: <41667322 DOT 8040706 AT emirates DOT net DOT ae>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Maarten Boekhold wrote:

> suppose I have application A, that loads (gmodule_open) a module B. 'A'
> contains a variable:
> 
>         A.c:
>         G_MODULE_EXPORT int var = 1;
> 
> B refers to that variable:
> 
>         B.c:
>         G_MODULE_IMPORT int var;
> 
> B is linked with a A.def file:
> 
>         A.def:
>         IMPORTS
>         var = A.exe.var
> 
> When I use 'var' in B, it has a completely wrong value.
> 
> Can the windows linker resolve references to external variables when
> loading a library with gmodule_open/dlopen?

You might want to read this thread:
<http://sources.redhat.com/ml/cygwin/2004-10/msg00339.html>

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/