This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
linking gcc & vc++ object files
- To: gnu-win32 at cygnus dot com
- Subject: linking gcc & vc++ object files
- From: David Young <dyoung at vviuh221 dot vvi dot com>
- Date: Sat, 1 Aug 98 10:37:32 -0400
- Reply-To: dyoung at vviuh221 dot vvi dot com
gnu-win32:
We are linking object files generated by gcc and object files
generated by vc++ on Windows-NT. In order to get object files
generated by gcc to link with object files generated by VC++ we have
to append a "@n" suffix (n seems to be always a multiple of 4) to the
function names (in the gcc related source files) whos object
definition is in the files generated by VC++. That's because the VC++
generates function symbols in object files with a "@n" suffix. Note,
this has nothing to do with C++ name mangling, all function
definitions are wrapped in extern "C" {} ; this is an ANSI-C related
issue.
QUESTION: What is the "@n" all about?
>From the list archives, I see this question was asked on this mail
list before, but the responses were incongruent to say the least.
Your response is very welcome.
Please cc:: your response to dyoung@vvi.com as I do not want to miss
any input regarding this subject.
Thanks A Bunch!
David Young; vvi-dcs
dyoung@vvi.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".