Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <19990703122816.46353.qmail@hotmail.com> X-Originating-IP: [212.52.67.175] From: Emanuele ALIBERTI To: khan AT xraylith DOT wisc DOT EDU Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Dlls @n symbols Date: Sat, 03 Jul 1999 05:28:16 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed >From: Mumit Khan >To: Emanuele ALIBERTI >CC: cygwin AT sourceware DOT cygnus DOT 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@ etc and use -k to have >@ linkable symbols that point to export symbol without the @, 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 AT sourceware DOT cygnus DOT com