[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] freetype compilation warnings
From: |
Werner LEMBERG |
Subject: |
Re: [ft-devel] freetype compilation warnings |
Date: |
Sun, 20 Dec 2009 18:20:30 +0100 (CET) |
>> Just getting rid of _debug_mem_dummy would cause a problem? Is
>> there another way to create a non-empty file? How about a useless
>> but harmless #include, like #include <string.h>?
>
> Ah, I haven't thought of that. Sounds like a good idea.
Well, after some thinking I now believe that this doesn't work: The
preprocessor removes everything and we thus still have an empty file
to compile.
I've now replaced it with a `typedef'.
>> FTC_GNode_Compare() has 2 parameters:
>>
>> FT_LOCAL( FT_Bool )
>> FTC_GNode_Compare( FTC_GNode gnode,
>> FTC_GQuery gquery );
>>
>> but it's being cast to FTC_Node_CompareFunc which is 3 parameters:
>>
>> typedef FT_Bool
>> (*FTC_Node_CompareFunc)( FTC_Node node,
>> FT_Pointer key,
>> FTC_Cache cache );
Yes, this seems to be the cause. However, fixing this is not easy
(except providing a new macro which is rather unelegant) -- at least
for me. Any idea how to work around the warning?
Werner
- [ft-devel] freetype compilation warnings, Sean McBride, 2009/12/14
- Re: [ft-devel] freetype compilation warnings, mpsuzuki, 2009/12/14
- Re: [ft-devel] freetype compilation warnings, Werner LEMBERG, 2009/12/15
- Re: [ft-devel] freetype compilation warnings, Sean McBride, 2009/12/15
- Re: [ft-devel] freetype compilation warnings, Sean McBride, 2009/12/16
- Re: [ft-devel] freetype compilation warnings, Werner LEMBERG, 2009/12/16
- Re: [ft-devel] freetype compilation warnings, Sean McBride, 2009/12/17
- Re: [ft-devel] freetype compilation warnings, Werner LEMBERG, 2009/12/17
- Re: [ft-devel] freetype compilation warnings,
Werner LEMBERG <=
- Re: [ft-devel] freetype compilation warnings, Sean McBride, 2009/12/21
- Re: [ft-devel] freetype compilation warnings, Werner LEMBERG, 2009/12/21