From: Mumit Khan <khan@xraylith.wisc.edu>
To: Christian Jullien <Eligis@wanadoo.fr>
Cc: "Gary V. Vaughan" <gvaughan@oranda.demon.co.uk>,
Geoffrey Noer <noer@cygnus.com>,
Jorrit Tyberghein <Jorrit.Tyberghein@uz.kuleuven.ac.be>,
gnu-win32@cygnus.com
Subject: RE: dlopen patch [was Re: dlopen]
Date: Sun, 15 Nov 1998 23:41:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.981116011414.24494A-101000@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <000001be0d4d$16835060$020039c1@young>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
"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
[-- Attachment #2: exp-exe.tar.gz --]
[-- Type: application/x-gzip, Size: 688 bytes --]
next prev parent reply other threads:[~1998-11-15 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-29 5:02 dlopen Jorrit Tyberghein
1998-10-30 5:08 ` dlopen Gary V. Vaughan
1998-10-30 16:19 ` dlopen Geoffrey Noer
1998-11-11 3:57 ` dlopen patch [was Re: dlopen] Gary V. Vaughan
1998-11-11 4:22 ` Christian Jullien
1998-11-15 23:41 ` Mumit Khan [this message]
1998-11-16 6:12 ` Christian Jullien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.3.93.981116011414.24494A-101000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=Eligis@wanadoo.fr \
--cc=Jorrit.Tyberghein@uz.kuleuven.ac.be \
--cc=gnu-win32@cygnus.com \
--cc=gvaughan@oranda.demon.co.uk \
--cc=noer@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).