Trolltech Home \| Qt-interest Home \| Recent Threads \| All Threads \| Author \| Date
All threads index page 4

Qt-interest Archive, March 2002
MSVC++ name mangling?

Message 1 in thread

Subject: MSVC++ name mangling?
From: Eric Smith <eric@xxxxxxxxxxxx>
Date: Mon, 11 Mar 2002 21:40:57 -0500
To: qt-interest@xxxxxxxxxxxxx

Greetings,

Does anybody know where I can find a document which describes how MSVC++ mangles symbol names?  I just downloaded the Qt/Windows evaluation version, and I'm trying to build some of the samples using Metrowerks CodeWarrior (yes, I know it's not supported).  I get most of the way there, but the link fails with the following undefined symbol:

__imp_?new_metaobject@QMetaObject@@SAPAV1@PBDPAV1@PBUQMetaData@@H2HPBVQMetaProperty@@HPBUQMetaEnum@@HPBUQClassInfo@@H@Z

I dug through the qt-mteval301.lib file, and turned up the following symbol:

__imp_?new_metaobject@QMetaObject@@SAPAV1@PBDPAV1@QBUQMetaData@@H2HQBVQMetaProperty@@HQBUQMetaEnum@@HQBUQClassInfo@@H@Z

If you look carefully, the two symbols are almost identical, except that four of the 'P's have been replaced by 'Q's.  It looks like CodeWarrior is mangling things slightly differently from MSVC++, but I would like to find out for sure.  Anybody know where this nonsense is documented?

Thanks,

Eric Smith
Tarkvara Design Inc.

Qt-interest Archive, March 2002MSVC++ name mangling?

Qt-interest Archive, March 2002
MSVC++ name mangling?