C++/CLI: linker gives "unresolved token" for win32 function

2
votes

Folks,

I just created my first C++/CLI project (Visual Studio 2008), it's a Library to allow my C# app access an point of sale tally printer.

My library builds well and trivial functions work when called from a C# exe.

However as soon as I include a WinGDI call (DeleteObject in this case), the linker complains with “unresolved token” errors.

Error 2 error LNK2028: unresolved token (0A000088) "extern "C" int __stdcall DeleteObject(void *)" (?DeleteObject@@$$J14YGHPAX@Z) referenced in function "private: __clrcall ReceiptPrinter::Epson::~Epson(void)" (??1Epson@ReceiptPrinter@@$$FA$AAM@XZ) ReceiptPrinter.obj ReceiptPrinter

I haven't done any serious C++ in the last 4 years, and I have precious little experience of MS C++ compilers, as such I don’t know what I’m looking for in the linker settings.

Any help will be greatfully received.

Thanks

3
.netvisual-studioc++-cli
Check if Gdi32.lib is there in the linker commandline(Properties > Linker > CommandLine). – dirkgently
Additional dependancies was "NoInherit", when I looked "under" the setting, there was a list of libs, gdi32.lib was in the list. I checked "Inherit from parent project" and it now works. Dirk, if you add all that as an answer I'll select it and give you the rep. Thanks mate :) – Binary Worrier

3 Answers

7
votes

Additional dependancies was "NoInherit", when I looked "under" the setting, there was a list of libs, gdi32.lib was in the list. I checked "Inherit from parent project" and it now works. Dirk, if you add all that as an answer I'll select it and give you the rep.

Check if Gdi32.lib is there in the linker commandline(Properties > Linker > CommandLine).

(There you go -- you have successfully appealed to the my selfish, rep seeking part of soul ;) )

3
votes

You should link your dll with Gdi32.lib.

You can either do it with a #pragma comment(lib, "gdi32.lib") or in your project's settings under Linker.

2
votes

The clue is in the __clrcall modifier on the function declarations. Your Windows Forms app uses pure Common Language Runtime code and calling conventions by default. Your external library, which you're linking to, does not. You need to change the Common Language Runtime support setting in your Project Defaults area of the project properties from /clr:pure to /clr. That worked for me.