This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Plugins and referencing *variables* in the loading program




Hi Brian,

Don't know if you noticed, but the thread you are referring to was started by me as well :) All the material discussed in there I managed to apply just fine.

However, that thread deals with importing *functions*, not variables. I created a stand-alone test in which the plugin is trying to reference a *variable* in the loading program, and that *fails*.

I can post my test program if anybody is interested...

Maarten

Brian Dessent wrote:
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>

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]