tetris.obj : error LNK2019: unresolved external symbol "enum gamestate __cdecl runState(class Piece *,class Board *)" (?runState@@YA?AW4gamestate@@PAVPiece@@PAVBoard@@@Z) referenced in function "void __cdecl GameRun(struct HWND__ *)" (?GameRun@@YAXPAUHWND__@@@Z)
tetris.obj : error LNK2019: unresolved external symbol "enum gamestate __cdecl newpieceState(class Piece *,class Piece *)" (?newpieceState@@YA?AW4gamestate@@PAVPiece@@0@Z) referenced in function "void __cdecl GameRun(struct HWND__ *)" (?GameRun@@YAXPAUHWND__@@@Z)
question about compiler erro
ok so here is the error I M getting. msvc++ express beta 2
Generally means that the compiler didn't find a function body so it wasn't able to resolve it.
It means that the "unresolved" functions are missing. You wrote the declarations (because the compiler didn't complain, but you never wrote (or linked in) the functions themselves. Usually, this happens because the function doesn't match the declaration, for example a missing "const" or a missing parameter. Perhaps the function is static or in an anonymous namespace, or perhaps you simply forgot to add the source file to the project.
I think a list of compiler errors and ways to resolve them should be posted to the FAQ, since so many people seem to be confused about this...
Quote:Original post by Oberon_Command
I think a list of compiler errors and ways to resolve them should be posted to the FAQ, since so many people seem to be confused about this...
All the compilers errors for all compilers would be a bit too much to list. Maybe very common ones would be good to have.
A neat trick that works on visual c++ '03 (and presumable newer versions): select the error in the task list and then hit f1. It will bring you the documentation page explaining the error.
Quote:Original post by RaynoQuote:Original post by Oberon_Command
I think a list of compiler errors and ways to resolve them should be posted to the FAQ, since so many people seem to be confused about this...
All the compilers errors for all compilers would be a bit too much to list. Maybe very common ones would be good to have.
A neat trick that works on visual c++ '03 (and presumable newer versions): select the error in the task list and then hit f1. It will bring you the documentation page explaining the error.
Yes, that's what I mean. You can do the F1 trick in 6.0, too, but the problem is, that it isn't well documented in 6.0. Don't know about 2003, tho...
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement