Really? I've never had any issue with this. What errors do you have?
When I try to create a debug build with the included 2.0 version of freetype.lib, I get a linker error message stating that the debug information is corrupt. This does not happen on a release build, or if I use the 1.6 supplied version of this file. My best guess is that the freetype.lib file was built with VS 2008, and my VS 2005 cannot read the debug information. Using the 1.6 supplied version does not seem to create any problem.
Again, which errors?
Whenever this file is loaded on behalf of music, I get errors around or about mutex(.h?). I use sounds, and that does not seem to present problems for .wav files (very small). When I try to use an .ogg file for music, I am told that it is a valid file type, but an invalid format. No music of course. The access violation occurs when the shutdown happens. Probably the original exception left something around that did not get cleaned up when exiting. If I can get it to play a music file without errors, the rest will probably take care of itself.
No, why do you ask this question?
Reasons listed above.
I have one question for you: are you sure that you don't somehow mix 1.6 and 2.0? These external libs errors that you're describing seem to be really weird. Do you link to dyanmic or static SFML libs? Have you tried the other way?
I updated the paths, and believe I have them living separately well enough. Except freetype.lib when I rebuilt the graphics dll for debug mode. I wanted to avoid static libs and prefer DLLs in my local directory, since in theory I would not update them as often to anyone testing the application.