[Vm-dev] Problems with building a freetype plugin on linux

Andreas Raab andreas.raab at gmx.de
Wed Apr 28 01:15:31 UTC 2010


Just FYI, this include is just plain broken in FT2Plugin. The correct 
usage of Freetype is by using the macros, for example FT_FREETYPE_H and 
FT_OUTLINE_H. The correct macro to use here is:

	cg addHeaderFile: 'FT_TRUETYPE_TABLES_H'.

Instead of using either 'tttables.h' OR 'freetype/tttables.h' See the 
Freetype documentation about using the header files correctly:

http://freetype.sourceforge.net/freetype2/docs/tutorial/step1.html

The reason it works on Windows is that I'm going out of my way to add 
freetype/ to the include path (which is wrong too but it works).

Cheers,
   - Andreas


On 4/27/2010 5:59 PM, David T. Lewis wrote:
>
> On Wed, Apr 28, 2010 at 02:51:58AM +0300, Igor Stasenko wrote:
>>
>> gcc -g -O2 -fomit-frame-pointer -DLSB_FIRST=1 -DHAVE_CONFIG_H
>> -I/home/sig/squeak/src/build -I/home/sig/squeak/src/platforms/unix/vm
>> -I/home/sig/squeak/src/platforms/Cross/vm
>> -I/home/sig/squeak/src/src/vm -c
>> /home/sig/squeak/src/src/plugins/FT2Plugin/FT2Plugin.c  -fPIC -DPIC
>> -DPIC -o FT2Plugin.o
>>
>> In file included from /home/sig/squeak/src/src/plugins/FT2Plugin/FT2Plugin.c:30:
>> /usr/include/ft2build.h:56:38: error: freetype/config/ftheader.h: No
>> such file or directory
>>
>> and ftheader.h contents says:
>>
>>    /* `<prefix>/include/freetype2' must be in your current inclusion path */
>> #include<freetype/config/ftheader.h>
>>
>> So, it looks like a gcc flags missing the include option:
>>
>> -I/use/include/freetype2
>
> See platforms/unix/plugins/FT2Plugin/FT2PluginHeaderFix-ikp.1.cs for the
> patch that Ian used to address this. I cannot say if it works on Windows,
> if so Ian's patch should be included in the FT2Plugin. Otherwise it
> presumably should be addressed in CMake to get the include path right.
>
> I'm not sure who is the maintainer of FT2Plugin. I have the VMMaker
> configuration map pointing at source.impara.de/freetype, but I'm not
> sure if this is being actively maintained.
>
> Dave
>


More information about the Vm-dev mailing list