From: pete AT horus DOT cix DOT co DOT uk (Pete Jordan)
Subject: Re: linking gcc & vc++ object files
4 Aug 1998 03:23:17 -0700
Message-ID: <memo.19980803204616.341B.cygnus.gnu-win32@horus.horus.cix.co.uk>
References: <9808011437 DOT AA01661 AT vviuh221 DOT vvi DOT com>
Reply-To: gnu-win32 AT cygnus DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: gnu-win32 AT cygnus DOT com
Cc: dyoung AT vviuh221 DOT vvi DOT com

David Young <dyoung AT vviuh221 DOT vvi DOT com> wrote:

> In order to get object files generated by gcc to link with object files
> generated by VC++ we have to append a "@n" suffix
 [...]
> QUESTION: What is the "@n" all about?

It's a parameter count (x4) for STDCALL functions. Why x4 I have no 
idea...

As per your backsearches in the list, I've sorted this when linking to an 
egcs DLL from VC++ by putting EXPORTS entries like:

	Exec=Exec AT 4

in my DLL .def file. I haven't (yet) found a way of direct linking VC++ 
DLL entries into my egcs code, but a combination of LoadLibrary() and 
calls to ImportProc() does what I need.

HTH,

Pete Jordan ~ Horus Communications Ltd ~ http://www.horus.cix.co.uk/

"As soon as we have defined something, we have ipso facto created
 three things: whatever is included in our definition, whatever is
 not included in our definition, and the relationship between them."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".