This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: dlopen patch [was Re: dlopen]
- To: Christian Jullien <Eligis at wanadoo dot fr>
- Subject: RE: dlopen patch [was Re: dlopen]
- From: Mumit Khan <khan at xraylith dot wisc dot edu>
- Date: Mon, 16 Nov 1998 01:16:03 -0600 (CST)
- Cc: "Gary V. Vaughan" <gvaughan at oranda dot demon dot co dot uk>, Geoffrey Noer <noer at cygnus dot com>, Jorrit Tyberghein <Jorrit dot Tyberghein at uz dot kuleuven dot ac dot be>, gnu-win32 at cygnus dot com
"Christian Jullien" <Eligis@wanadoo.fr> writes:
>
> But it does not work since all symbols MUST be exported (am I right ?). In
> my special case I can't export all symbols,
> I've also a lot (>= 50000) generated assembler lines.
That's correct. Of course, the solution is simple since all you need to
do is to link with an export file (dlltool can create that easily), and
with Gary's patch you can dlopen/dlsym the function quite easily.
> If you have a better solution I will be happy to test it (and/or to improve
> it).
I'm attaching a trivial example (to run this, you have to have Gary's
patch or wait for b20.1). Please let me know if this doesn't work for
your application.
btw, a good example for this is in Perl's configuration, where perl is
built as an exportable executable. You can also use dllwrap (with a
few extra semi-documented flags), but it's just as easy doing it using
the simple Makefile included in my example.
Regards,
Mumit
exportable executable example