freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [ft-devel] FreeType2 2.3.5 Visual Studio Solution Warnings


From: Graham Asher
Subject: RE: [ft-devel] FreeType2 2.3.5 Visual Studio Solution Warnings
Date: Thu, 8 Nov 2007 11:28:56 -0000

This worked for me a while ago when compiling FreeType into a Windows DLL:

#define FT_EXPORT(return_type) __declspec(dllexport) return_type
#define FT_EXPORT_DEF(return_type) __declspec(dllexport) return_type

Graham

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Werner LEMBERG
Sent: 08 November 2007 08:51
To: address@hidden
Cc: address@hidden
Subject: Re: [ft-devel] FreeType2 2.3.5 Visual Studio Solution Warnings


> I tried to compile the solution bundled with 2.3.5. The solution built
> without error, but with dozens of warnings such as the following:
>
> 1>c:\development\build\gnuwin32\src\freetype\2.3.5\freetype-2.3.5\src\tr
> uetype\ttinterp.c(772) : warning C4273: 'TT_New_Context' : inconsistent
> dll linkage
>
> 1>
> c:\development\build\gnuwin32\src\freetype\2.3.5\freetype-2.3.5\src\true
> type\ttinterp.h(262) : see previous definition of 'TT_New_Context'

You properly have to redefine FT_EXPORT and FT_EXPORT_DEF, I think, to
pass `__declspec(dllexport)' or something like this to the compiler.
However, I can't give any precise recipe since I don't use this
platform.

It would be great if the visual studio files could be updated to
handle this automatically.  However, I got the impression that this
already works...

Can someone shed light on this?


    Werner


_______________________________________________
Freetype-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/freetype-devel





reply via email to

[Prev in Thread] Current Thread [Next in Thread]