Re: [ft-devel] Builind for windows Re: Freetype-devel Digest, Vol 131, Issue 16

[Hin-Tak Leung]

What is the exact message for the unresolved symbol?

It might be an obvious question, but you know that there are
different versions of the window platform SDKs, right? I have win 7,
and there is a win 7.1, and the two are different. The platform SDKs are
separate downloads from visual studio express. - sorry I am a cheap skate and
I only have vs express, but I suppose the paid visual studio would auto-install
the platform SDK for the current OS you are on, and maybe not anything else.
You may need to install an earlier platform SDK in addition.

going dlltool with mingw/msys/cygwin might be better if you have multiple
versions of windows to support, as they tend to support the
oldest...

Good luck.

Hin-Tak 

--------------------------------------------
On Wed, 23/12/15, Warton, James <address@hidden> wrote:
 
 Thanks for the
 response.  I have solved this problem. I don't fully
 understand why, but when building the .lib files from VS,
 system platform, freetype's project properties were set
 to Windows 8.1, without an option to roll back to 7.  The
 resulting library would cause an unresolved external symbol
 error when linked to my project.  Ultimately. I ported my
 project over to a Windows 8 machine to test whether this
 would solve the error.  As predicted the library is now
 implemented in my project without error.  
 
 I'm sure there's a way
 to solve this without upgrading my OS on other machines, but
 at the moment this may be the route I follow.  Apparently
 the VS approach isn't viable for me to stay with my
 current OS.
 
 Thanks,
 JW