unresolved external symbol __imp_XXX error (VS2010 c++)

Question

5.00/5 (3 votes)

See more:

I have a program that links to a static library. This library has exported global variable.
This variable is defined in the .def file, but I get the following error:

C++

unresolved external symbol __imp_XXX (where XXX is the variable name).

Does anyone knows the reason for that?

Posted 21-Apr-13 9:10am

Michael Haephrati

Add a Solution

Comments

RedDk 21-Apr-13 15:24pm

Add the 8 characters "/VERBOSE" to the linker "Command Line"/"Additional Options". The next time you try to link a list of addresses the program is locating to search for that (assume) mangled variable name should make it clear that the where of the output you've compiled might not be there.

Michael Haephrati 21-Apr-13 15:26pm

I have done that, and the first time the variable is mentioned, is at the end, with the same error message:
unresolved external symbol __imp_XXX (where XXX is the variable name).

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Michael Haephrati · Accepted Answer · 2013-04-21T09:29:00

Solution 1

In my case, what solved the problem was making sure that I only use $(SolutionDir)$(Platform)\$(Configuration)\ at any place that libraries are imported. :)

Posted 21-Apr-13 9:29am

Michael Haephrati

Comments

RedDk 21-Apr-13 16:26pm

Well, the thing is this. The linker is looking for this symbol and it's going through all the .lib that it can find. If you don't have the path explicitly named somewhere then the linker doen't know to look there.

I'd say to you try experimenting with an example that you've knowingly excluded the "look-in" variable. Compare that result from the Output tell to the pattern you got back when this missing library symbol couldn't be found. Any similarities? Etc ...

Michael Haephrati 21-Apr-13 16:51pm

Correct