SFML 2.0 - Freetype library linking in graphics module

[EatMyShorts]

Hello,

I have started using SFML 2.0 in my application. Recently I have added 2 new libraries to it zlib and zziplib to be able to read zip archives. Once I linked them as static libraries I received couple of linker errors

1>LIBCMT.lib(dosmap.obj) : error LNK2005: __errno already defined in MSVCRTD.lib(MSVCR90D.dll)

All my projects are supposed to link Multithreaded Runtime libs from DLL (/MD option in VS2008), but from what I saw in dumpbin.exe reports sfml2-graphics-s-d.lib uses freetype.lib which is compiled with /MT Runtime Library option and this is not good.

Is it going to be changed in near future ?

//EDIT:

I have more problems with my application now. I cannot compile it even if i have recompiled FreeType library.

Can you tell me what version of freetype lib are you using. Maybe I have compiled wrong wersion.

//EDIT 2

I have managed to compile it correctly. I have downloaded lates version of Freetype lib. Compile it it /MD[d] option and recompile SFML 2.0

I think this issue should be fixed in SFML 2.0.[/b]

[Laurent]

I'll check this ASAP, thanks for your feedback.

[Laurent]

Done finally

[EatMyShorts]

Sorry for my late reply. I have checked new version of SFML 2 and it works perfect only in Release version in Debug build it crashes. Last time I did some research about this problem and managed to compile whole SFML 2.0 project.

Here's what I had to do in order to link SFML 2.0 with my project in both configurations. (BTW: if you need a project that shows this problem let me know i will try to spare some time to prepare a sample mini project)

1. FreetypeLib  recompilation with /MD adn /MDd option
From what i saw in the latest SVN branch you are using the same freetype.lib for Release and Debug configs. This causes problem in Debug builds. There is a confilct between MSVCRT.LIB and MSVCRTD.LIB (as a result program craches ). I think you will have to include debug libs for FreetypeLib

2. JPEGLib
Here is similar problem to previous one. You have to include debug version of lib

Check this site: http://leptonica.org/vs2008doc/building-zlib-libjpeg-libpng.html. Here you can read about building this library. There is a problem because the library does not have Debug config so you have to add it yourself.

3. GLEW
Similar situation to FreetypeLib problem. You will have to include also Debug libs.

Hope this helps

[Laurent]

I've never needed debug builds of C libraries before. It has always worked, so the problem really comes from your application. What exactly do you do?

[EatMyShorts]

Everything worked fine until i linked zlib and zziplib libraries. Before that i had no linker problems, even with LIBCMT conflict.

I think the second problem (MSVCRT and MSVCRTD conflict) is not so important as the first one with LIBCMT at least for now, because it affects only Debug config and I can still run my program by switching from debug zlib and zziplib to release dependencies.

[Laurent]

So the problem is that you end up with both debug and release versions of zlib linked to the same executable? Why do you use the debug version of zlib?

[EatMyShorts]

No, I ended up with linking both Debug and Release Runtime libs to one exec. It is caused by linking SFML (using release runtime libs) and debug zlib and zziplib (using debug runtime libs).

I am using Debug version of zlib just to be able to debug it. It is useful sometimes, but rarely.

[Laurent]

You need to debug zlib? Really?

I don't think there's an easy solution here, because if I apply your fix (linking to debug zlib in debug SFML libraries), users linking to release zlib in debug mode will face the same problem again.

[EatMyShorts]

I agree with you. I will reconfigure my project as posted earlier and everything should be fine.

Thanks for fixing previous problem