Jump to content
  • Advertisement
Sign in to follow this  
hplus0603

Color me stumped (VC++.NET name mangling)

This topic is 4524 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I built a bunch of DLLs in one project, and am then trying to use them (by linking to the .lib link libraries, and including the appropriate headers) in another project. Normally, this works fine; I've done it many many times on different projects. However, this time, I get errors about missing symbols for almost all the referenced symbols. Taking one representative symbol, here's the symbol that it wants: ?NewErrorDetails@pit@@YAPAVPiValueHash@1@PBGH0@Z Here's the symbol that the DLL provides: ?NewErrorDetails@pit@@YAPAVPiValueHash@1@PB_WH0@Z So, PBGH0 means something different from PB_WH0. My guess is having to do with calling conventions, or exception handling, or whatnot, and the application project is not compatible with some setting in the DLL project. But which setting is this? Anyone have any idea?

Share this post


Link to post
Share on other sites
Advertisement
Answering my own question: "Treat wchar_t as built-in type" causes that name mangling change.

Meanwhile, other exotic options, such as /EHa, do not cause name manling to change. Go figure...

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!