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
Subject:	Dynamic loading of cygwin dependent dlls
Date:	Thu, 5 Aug 2004 09:09:40 +0200
MIME-Version:	1.0
Message-ID:	<90459864DAD67D43BDD3D517DEFC2F7D7044@axon.Axentia.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Peter Ekberg" <peda AT axentia DOT se>
To:	<cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id i7579vJh023312

Hello!

I have read several messages stating that dlopen does not work for dlls
that depend on cygwin1.dll.
(e.g. http://sources.redhat.com/ml/cygwin/2004-06/msg01056.html).
I have also understood that this is due to some structures not being
initialized in that case.

Is this dlopen problem limited to non-cygwin apps? I.e. is it true
that an app that depends directly on the cygwin1.dll is incapable of
dlopening dlls that depend on cygwin1.dll?

Regards,
Peter Ekberg

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