Unresolved external Symbol
-
Well, the point is that the software calls some other C modules. I did scan all sources for as far as I can see, but they are not all included in the VS2010 solution so I had to so that by hand. However, I would have expected to at least get rid of the linker's complaint by adding a variable _VERSION in my own source code. Possibly with a wrong type, but then I would expect another complaint from Microsoft somewhere....
How did you add the char* _VERSION? And how and where is it used in your code? Considering that the linker is complaining I'm guessing you added something like:
char* _VERSION;
Somewhere in a source file? The solution is to make it something like:
char* _VERSION = "1.0"
And add that to a source file. But what the actual type and contents have to be totally depends on what the original code intended with it.
-
Did you try doing a solution wide search for _VERSION?
I fully agree with you all. Point however is that I need to find-out where my code is using it anbd even more: when I simply introduce a global variable _VERSION, I would no longer expect an "unresolved external" for _VERSION.
-
Well, the point is that the software calls some other C modules. I did scan all sources for as far as I can see, but they are not all included in the VS2010 solution so I had to so that by hand. However, I would have expected to at least get rid of the linker's complaint by adding a variable _VERSION in my own source code. Possibly with a wrong type, but then I would expect another complaint from Microsoft somewhere....
By the way, if you don't know, the Studio search will work in any directory you ask it to. So you can search for a line of code through all your libraries and includes.
-
How did you add the char* _VERSION? And how and where is it used in your code? Considering that the linker is complaining I'm guessing you added something like:
char* _VERSION;
Somewhere in a source file? The solution is to make it something like:
char* _VERSION = "1.0"
And add that to a source file. But what the actual type and contents have to be totally depends on what the original code intended with it.
Yes, I tried that too (adding char *_VERSION = "x.x"; as a global variable) but it does not help a bit
-
I fully agree with you all. Point however is that I need to find-out where my code is using it anbd even more: when I simply introduce a global variable _VERSION, I would no longer expect an "unresolved external" for _VERSION.
...that's partially true... did the _VERSION name have name mangling (or decoration), if so, you must match the name exactly, including the mangling (in case its actually a structure name or such)...
-
...that's partially true... did the _VERSION name have name mangling (or decoration), if so, you must match the name exactly, including the mangling (in case its actually a structure name or such)...
Well you do have a point there. The linker complains about a straight _VERSION. As far as I know, it would complain about something including the name mangling normally. It does however mean that - if I introduce a variable named _VERSION - that will probably be called differently internally. I have been looking into a way to remove the name mangling from a particular variable, but have not yet found anything.
-
...that's partially true... did the _VERSION name have name mangling (or decoration), if so, you must match the name exactly, including the mangling (in case its actually a structure name or such)...
Good point, did you try:
char* VERSION = "1.0"
Or else, if above does not work:
extern "C" char* VERSION = "1.0"
Also, before you do this you really ought to use the search in files function to find out where VERSION (without the underscore) is being used and for what.
-
Well you do have a point there. The linker complains about a straight _VERSION. As far as I know, it would complain about something including the name mangling normally. It does however mean that - if I introduce a variable named _VERSION - that will probably be called differently internally. I have been looking into a way to remove the name mangling from a particular variable, but have not yet found anything.
the extern C removes name mangling... so there may be some definition that you need to wrap with that somewhere in your source... you just have to find it (on a related note, wish linkers gave better error information, lol)
-
Trying to convert a very old C program to Microsoft Visual Studio 2010. After some warnings, including some extern "C"'s and all that, everyting compiles. However, the linker keeps calling that is misses an external symbol "_VERSION". I have been looking through all code and can't find any reference to it. I included a char * _VERSION somewhere in my main source (within and outside the extern "C") Still complains. Does anyone have an idea how I could find out where the linker finds the call of this reference? Is there som option that can persuade the linker to provide me with much more information or something like that? This is getting extremely frustrating, since everything else seems to work as expected. Just this @!$@! _VERSION.... Thanks in advance.
-
What is the exact message that the Linker produces?
The best things in life are not things.
This is the exact message: "error LNK2001: unresolved external symbol _VERSION"
-
the extern C removes name mangling... so there may be some definition that you need to wrap with that somewhere in your source... you just have to find it (on a related note, wish linkers gave better error information, lol)
I didn't realise from the original post that the name _VERSION was the name given by the linker, and is mangled. The unmangled name is VERSION, so that's what we're looking for here. Also, see my other post.
-
This is the exact message: "error LNK2001: unresolved external symbol _VERSION"
This means that you have a statement of the form:
extern "C" VERSION;
and a reference to the variable
VERSIONsomewhere in your final program. However, if this is not anywhere in your source modules it could possibly be in an associated library, so you may need to check what external libraries are being added to your program. You could also try the/MAPand/or/VERBOSElinker options to see if you can narrow it down to the actual module where it occurs.The best things in life are not things.
-
I fully agree with you all. Point however is that I need to find-out where my code is using it anbd even more: when I simply introduce a global variable _VERSION, I would no longer expect an "unresolved external" for _VERSION.
William Engberts wrote:
...I need to find-out where my code is using it...
Doesn't the linker tell you this?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Some people are making such thorough preparation for rainy days that they aren't enjoying today's sunshine." - William Feather
-
William Engberts wrote:
...I need to find-out where my code is using it...
Doesn't the linker tell you this?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Some people are making such thorough preparation for rainy days that they aren't enjoying today's sunshine." - William Feather
Can't remember off the top of my head, but I don't think it does... remember that the linker works with the compiler output... so it doesn't necessarily have an association between an unfound object and where it was referenced in source (although it may, this is more of a linker design feature).
-
This means that you have a statement of the form:
extern "C" VERSION;
and a reference to the variable
VERSIONsomewhere in your final program. However, if this is not anywhere in your source modules it could possibly be in an associated library, so you may need to check what external libraries are being added to your program. You could also try the/MAPand/or/VERBOSElinker options to see if you can narrow it down to the actual module where it occurs.The best things in life are not things.
good tip about the linker options to play with... :thumbsup:
-
good tip about the linker options to play with... :thumbsup: