VS C++ 2010 problem

[ShadowDragon]

I'm in the process of trying to get my source files to properly compile in Visual Studio C++ 2010 Express and I hit something that makes no sense to me.

I'm getting the following errors from AccountServer:

9>ffl_dumpr.lib(ffl_module_info.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_file.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_dump_log.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_dump_mini.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_dump_common.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_text_file.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_dump_unexception_filter.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_date_time.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_c_string.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version
9>ffl_dumpr.lib(ffl_dump_report.obj) : error LNK2001: unresolved external symbol __check_commonlanguageruntime_version

Here's the line that calls that file in AccountServer.cpp:

#pragma comment( lib, "../__lib/win32/msvc71/ffl_dumpr.lib" )

The file is there, and everything should be working. I've tried adding the directory to VC++ Directories and I've tried directly changing that line in AccountServer.cpp (to a static path, instead of relative). Nothing is working though.

Anybody know why it's doing this?

 

[Mootie]

I don't see why this doesn't make sense... The lib is clearly MFC7.1 and wouldn't work with vs2010. Just remove it, you can add another debugging feature.

 

[Dawson]

Should probably get a basic understanding of what linker errors are, and what exactly MFC is, and how the development libraries/kits change each new Visual Studio release before you try and develop on a game's source code. Or else you're gonna get laff'd at a lot. No offense it's just the harsh reality. (and the aforementioned is just a start, you really need to know about programming in general to be a successful developer)

 

[ShadowDragon]

Don't you think you're a bit harsh Dawson? It's not that I don't know programming, it's more like I, and many others here, are relatively new to C++.

I haven't done anything with libraries really (I don't even know how to see what's inside them, although I haven't looked that up anyways). I also haven't done much with creating programs from scratch (a combination of procrastination and lazyness is to blame). I plan to learn all of this eventually, but I haven't had the time.

Anyways, thanks lethal for answering my question.

I had a feeling it was a version incompatibility, but the errors didn't mention anything about that and with my limited knowledge on C++, I had no way to be sure.

 

[Dawson]

Seeing Visual Studio tell you build failed is a lot more harsh than me giving you some tips on what to learn so you don't get failed builds

 

[ShadowDragon]

and yet you don't give these 'tips' to anybody else asking about source changes? even the people asking about things way simpler than what I'm trying?

 

[Dawson]

I don't usually post in the FlyFF section at all I just randomly clicked the thread with the newest post on the forum index.

 

[tikkaroe]

ShadowDragon42 you good.

it is very good that you try to switch vs2003 to vs2010.

I want it too, but my knowledge is very little to do that.

if flyff-source can switch to 2010 i think. it will be better.

graphics and mange.

sorry if i say wrong.

 

[ShadowDragon]

Yeah, that's exactly why I'm trying to do that. The other reason for it, is VS 2010 automatically checks the coding method for improper and unsafe methods, and tells you about them.

I'm getting "Unknown compiler version" errors now. I already found out this is caused by the boost libraries. I've already downloaded the latest version and added it to VC++ directories, but the errors are still there. I've also seen that it's okay to ignore these errors. Anybody have a second opinion on this?

 

[Dawson]

When all else fails /FORCE.

 

[ShadowDragon]

btw, 90% of people in this section of ragezone wouldn't know what you meant by that, but I did.

Also, just tried it and nothing changed.

 

[Xakzi]

wonder why u wanna update it to 2010, when 2005 is more then enough,
and no, the graphic does not magicly becomes better when using a newer version of visual studio, it is the coding for the game, I have improved the graphic of the game with 2003, you just need to know what to edit / add / remove

 

[ShadowDragon]

I didn't say anything about the graphics being better..

Anyways, I'm updating to 2010 simply because it's the most current.

 

[Langstra]

I didn't say anything about the graphics being better..

Anyways, I'm updating to 2010 simply because it's the most current.

And it also creates much smaller exe files, seems to me also that is would make them more stable but I am not sure.

 

[ShadowDragon]

I did not know about the smaller executables, although it's good to know. I'm also making the effort to change many functions to their secure versions (ie. sprintf to sprintf_s, strcpy to strcpy_s, etc.) and believe me, there are thousands of these. that might also make things more stable.

 

[Langstra]

Well I am getting the same errors as ShadowDragon is getting, does anybody know how to fix them, maybe replace the MFC 7.1 by MFC 10.0? In that case I need to know where to get MFC 10.0, as I could not find it by using google, or is it already on my pc, somewhere?

 

[ShadowDragon]

I think you misunderstood what xLethal said. The compiler can't load that library (ffl_dumpr.lib) because it was specifically built for MFC 7.1

It has something to do with debugging, although I don't know what exactly. Commenting everything related to it will let you compile, I've already gotten to that point on each of the projects, but attempting to open AccountServer always gives me an error in dbghook.c (I'm guessing because there's nothing to catch unhandled exceptions.

Edit: ok, Ignore that second paragraph. I just found the problem. I did something stupid lol.. which isn't all that surprising. Instead of using sizeof() for the extra parameters in the functions, use (strlen() + 1). That was causing my previous problems. I now have AccountServer running after converting to 2010 =)

 

[Langstra]

So I need to use (strlen(parameter1) + 1) and in the cases of strcat (strlen(parameter1) + strleng(parameter2) + 1)?
And you still have everything commented related to that MFC or is that not needed anymore?

 

[ShadowDragon]

for that first one, it's parameter 2 actually, but yeah, use those.

And yeah, I have all those commented. I'm pretty sure that's what does the minidump feature when the program crashes. If you get problems running it, compile in debug mode to see what caused the problem.

 

[Langstra]

for that first one, it's parameter 2 actually, but yeah, use those.

And yeah, I have all those commented. I'm pretty sure that's what does the minidump feature when the program crashes. If you get problems running it, compile in debug mode to see what caused the problem.

Well ok, I thought you said to use the first parameter last time, but ok. I will use the second parameter.