www.delorie.com/archives/browse.cgi | search |
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: | <19990514095506.54657.qmail@hotmail.com> |
X-Originating-IP: | [193.207.88.144] |
From: | "Emanuele ALIBERTI" <ealiberti AT hotmail DOT com> |
To: | TMH AT mic DOT dtu DOT dk, cygwin AT sourceware DOT cygnus DOT com |
Subject: | Re: Linking to STDCALL-functions without '@xx' appended |
Date: | Fri, 14 May 1999 02:55:05 PDT |
Mime-Version: | 1.0 |
>It appears that the export table of the DLL does not have the '@xx' >appended to the function names. (In fact using Quick View is seems that >the DLL has no export table). > >My question is then is it possible to make links to STDCALL-functions >without the '@xx' being appended to the function name. > >It is not a problem to produce a library-file with appropriate names. I have a similar problem: I want a clean exports table in my DLLs (no stdcall mangled names), so I use the aliasing in the .DEF file: EXPORTS AlphaBeta=AlphaBeta AT 12 but that .DEF file does not put mangled names in the import library, so programs can not link. How could generate a clean exports table and make my programs link? -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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |