Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	<009e01c25759$494d3e20$0b01a8c0@Camelot>
From:	"Pierluigi 'Lanugo' Rolando" <lanugo AT ica-net DOT it>
To:	"Cygwin" <cygwin AT cygwin DOT com>
References:	<014a01c25575$188ca400$46ca09c0 AT aniraj>
Subject:	Re: Problem in Porting glib on cygwin
Date:	Sun, 8 Sep 2002 19:00:27 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

> has some utilities to load .so dynamically using module_open. As cygwin
does not support so library.
> How it can be achieved for the porgrams which uses dynamic module loading.

Are you sure about the lack of support for .so dynamic linking? The dl*()
call family (dlopen, dlclose, dlsym, dlerror) appears to be supported (they
are listed in the API documentation) and working (I've tried to port some
code of mine that makes use of them for a plug-in system and everything is
ok).
The only difference is that you don't need to link the dl library (it looks
like it doens't exists at all under cygwin, maybe those calls are
implemented elsewhere) and the -fPIC / -fpic options make cc1 emit a
warning.

HTH,
Lanugo of the Wandering Souls



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -