tracking down linker errors
-
I there a way to track down the linker errors further than what`s being offered in the "Build output" window?
-
I there a way to track down the linker errors further than what`s being offered in the "Build output" window?
Not really. You can increase number of linker messages by changing the "Show Progress" option. The "Display all messages" is really verbose. Otherwise, sometimes they can be tricky to trace. Just yesterday I had one where an include directive was used after a
namespace blah_blah {
line. Linker was looking for a function definition inside the namespace when it was actually outside.
Mircea
-
I there a way to track down the linker errors further than what`s being offered in the "Build output" window?
-
I`m not sure what details you are expecting. All I have in the build output window is a one line message: 1>Tutorial07.obj : error LNK2001: unresolved external symbol "void __cdecl CheckCollisions(class std::vector > *,int,class contim *,int)" I know an error of this type means that some parameters don`t match in the function definition, declaration and the place where the function is being used. I did a search for the function name within the code file, everything seems to be fine in the function header (return type, function name and parameters) everywhere. I need more details to know what exactly doesn`t match.
void CheckCollisions(vector * GAllElements, int UnitCount, contim* OldNewTable,int frame);
never mind I found the error, it was a parameter mismatch, you have to be extra careful with those.
