Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 5 Aug 2004 07:24:42 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Dynamic loading of cygwin dependent dlls Message-ID: <20040805112442.GB30831@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <90459864DAD67D43BDD3D517DEFC2F7D7044 AT axon DOT Axentia DOT local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <90459864DAD67D43BDD3D517DEFC2F7D7044@axon.Axentia.local> User-Agent: Mutt/1.4.1i On Thu, Aug 05, 2004 at 09:09:40AM +0200, Peter Ekberg wrote: >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? No, it is not true. dlopen would be pretty worthless if it didn't work in a standard cygwin program. -- 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/