From: Emanuele ALIBERTI <ealiberti@hotmail.com>
To: khan@xraylith.wisc.EDU
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Dlls @n symbols
Date: Sat, 03 Jul 1999 05:29:00 -0000 [thread overview]
Message-ID: <19990703122816.46353.qmail@hotmail.com> (raw)
>From: Mumit Khan <khan@xraylith.wisc.EDU>
>To: Emanuele ALIBERTI <ealiberti@hotmail.com>
>CC: cygwin@sourceware.cygnus.com
>Subject: Re: Dlls @n symbols
>Date: Sun, 27 Jun 1999 14:23:58 -0500
(sorry for the late reply: I was off line because of work)
>The reason to have "clean" names in the export list is simple -- so you
>can use LoadLibrary. If you only need to use LoadLibrary, then you can
>use the clean names. So have both in the export list! What's the big deal?
Since I am rewriting an existing library, it is a big deal. Not in general.
>One way to achieve both is the following (and that's how MSVC developers
>do this in case you're interested): Have two different export def files,
>one for creating the DLL, and the other for creating the import library.
>When creating the DLL, use the aliasing mechanism to get only clean names;
>when creating the import library, using Foo@<n> etc and use -k to have
>@<n> linkable symbols that point to export symbol without the @<n>, ie.,
>the "clean" names.
I was going that way, but that seemed the last chance, because I would have
to maintain two files. Probably I will write a simple preprocessor that
generates the DEF with aliases from the traditional DEF. Thank you for the
explanation of the real use of the -k option.
>Let me ask the same question I had the last time -- can you do what you
>want with MSVC? If so, how?
I don't know if it is possible: I use it only from the IDE, but the dll I
build that way have a clean exports table.
>If you feel like it's not doing the right thing, please feel free to
>start digging into binutils sources and see if you can help improve
>it.
Who are the developers of dlltool? I don't know if I can contribute, but
there is also the names in the exports table as "symbolic link" problem that
still waits for a solution.
-e-
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Emanuele ALIBERTI <ealiberti@hotmail.com>
To: khan@xraylith.wisc.EDU
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Dlls @n symbols
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <19990703122816.46353.qmail@hotmail.com> (raw)
Message-ID: <19990731183400.0DdRhpk4kcu-q42MVnhOTKtjA1FEHI8uHxZuaus2XQI@z> (raw)
>From: Mumit Khan <khan@xraylith.wisc.EDU>
>To: Emanuele ALIBERTI <ealiberti@hotmail.com>
>CC: cygwin@sourceware.cygnus.com
>Subject: Re: Dlls @n symbols
>Date: Sun, 27 Jun 1999 14:23:58 -0500
(sorry for the late reply: I was off line because of work)
>The reason to have "clean" names in the export list is simple -- so you
>can use LoadLibrary. If you only need to use LoadLibrary, then you can
>use the clean names. So have both in the export list! What's the big deal?
Since I am rewriting an existing library, it is a big deal. Not in general.
>One way to achieve both is the following (and that's how MSVC developers
>do this in case you're interested): Have two different export def files,
>one for creating the DLL, and the other for creating the import library.
>When creating the DLL, use the aliasing mechanism to get only clean names;
>when creating the import library, using Foo@<n> etc and use -k to have
>@<n> linkable symbols that point to export symbol without the @<n>, ie.,
>the "clean" names.
I was going that way, but that seemed the last chance, because I would have
to maintain two files. Probably I will write a simple preprocessor that
generates the DEF with aliases from the traditional DEF. Thank you for the
explanation of the real use of the -k option.
>Let me ask the same question I had the last time -- can you do what you
>want with MSVC? If so, how?
I don't know if it is possible: I use it only from the IDE, but the dll I
build that way have a clean exports table.
>If you feel like it's not doing the right thing, please feel free to
>start digging into binutils sources and see if you can help improve
>it.
Who are the developers of dlltool? I don't know if I can contribute, but
there is also the names in the exports table as "symbolic link" problem that
still waits for a solution.
-e-
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-07-03 5:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-03 5:29 Emanuele ALIBERTI [this message]
1999-07-03 9:17 ` DJ Delorie
1999-07-31 18:34 ` DJ Delorie
1999-07-31 18:34 ` Emanuele ALIBERTI
-- strict thread matches above, loose matches on Subject: below --
1999-08-08 14:58 Emanuele ALIBERTI
1999-08-31 23:49 ` Emanuele ALIBERTI
1999-07-08 4:41 Emanuele ALIBERTI
1999-07-31 18:34 ` Emanuele ALIBERTI
1999-07-05 23:21 Emanuele ALIBERTI
1999-07-06 11:16 ` Mumit Khan
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Emanuele ALIBERTI
1999-06-27 8:57 Emanuele ALIBERTI
1999-06-27 12:24 ` Mumit Khan
1999-06-30 22:10 ` Mumit Khan
1999-06-30 22:10 ` Emanuele ALIBERTI
1999-06-24 10:54 Jim Roy
1999-06-24 11:17 ` Mumit Khan
1999-06-30 22:10 ` Mumit Khan
1999-06-30 22:10 ` Jim Roy
1999-06-24 0:15 Emanuele ALIBERTI
1999-06-24 11:23 ` Mumit Khan
1999-06-30 22:10 ` Mumit Khan
1999-06-30 22:10 ` Emanuele ALIBERTI
1999-06-23 0:09 Emanuele ALIBERTI
1999-06-23 9:08 ` Mumit Khan
1999-06-30 22:10 ` Mumit Khan
1999-06-30 22:10 ` Emanuele ALIBERTI
1999-06-22 13:42 Suhaib M. Siddiqi
1999-06-30 22:10 ` Suhaib M. Siddiqi
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=19990703122816.46353.qmail@hotmail.com \
--to=ealiberti@hotmail.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=khan@xraylith.wisc.EDU \
/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).