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:	<1529c46304100604132bced4d1@mail.gmail.com>
Date:	Wed, 6 Oct 2004 15:13:31 +0400
From:	Maarten Boekhold <boekhold AT gmail DOT com>
Reply-To:	Maarten Boekhold <boekhold AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Building plugin that is used from multiple executables
Cc:	boekhold AT emirates DOT net DOT ae
Mime-Version:	1.0

Hi,

Suppose I have a plugin library that contains calls that reside in the
executable that dlopen()'s that plugin. You can link such a plugin by
using a .def file that contains something like:

IMPORTS
symbol = executable.exe.symbol

Now if I need to be able to use the *same* plugin from *two*
executables, how do I resolve that??? Can I use a .def file that
contains:

IMPORTS
symbol = executable_1.exe.symbol
symbol = executable_2.exe.symbol

My gut feeling says 'no', but hope against hope...

Maarten

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

- Raw text -