Re: [ft-devel] new FreeType release within a week

[suzuki toshiya]

Dear Markus,

It's difficult to say which of FreeType or HarfBuzz is the responsible
about this issue, but I've reported this to Behdad already on Aug/25.
Using uint32_t integer (HB_TAG) in enum definition can cause such
warning. It seems that no discussion is started in HarfBuzz mailing list.

Of course, FreeType2 build system can have some workaround (e.g. use
more "permissive" CFLAG to compile the related part), but I think we
should wait for some workarounds by HarfBuzz, because similar issue
might be found in other softwares.

Regards,
mpsuzuki


Markus Trippelsdorf wrote:
> On 2016.09.02 at 08:25 +0200, Werner LEMBERG wrote:
>> Folks,
>>
>>
>> I want to make a 2.7 FreeType release within a week, so please test
>> the current git version whether there are any serious issues!
> 
> Not a serious issue, but nevertheless I still get:
> 
> In file included from /usr/include/harfbuzz/hb-blob.h:34:0,
>                  from /usr/include/harfbuzz/hb.h:35,
>                  from /home/markus/freetype2/src/autofit/afshaper.h:29,
>                  from /home/markus/freetype2/src/autofit/afglobal.h:26,
>                  from /home/markus/freetype2/src/autofit/afpic.c:23,
>                  from /home/markus/freetype2/src/autofit/autofit.c:21:
> /usr/include/harfbuzz/hb-common.h:93:29: warning: ISO C restricts enumerator 
> values to range of ‘int’ [-Wpedantic]
>  #define HB_TAG(c1,c2,c3,c4) 
> ((hb_tag_t)((((uint8_t)(c1))<<24)|(((uint8_t)(c2))<<16)|(((uint8_t)(c3))<<8)|((uint8_t)(c4))))
>                              ^
> /usr/include/harfbuzz/hb-common.h:97:20: note: in expansion of macro ‘HB_TAG’
>  #define HB_TAG_MAX HB_TAG(0xff,0xff,0xff,0xff)
>                     ^~~~~~
> /usr/include/harfbuzz/hb-common.h:334:29: note: in expansion of macro 
> ‘HB_TAG_MAX’
>    _HB_SCRIPT_MAX_VALUE    = HB_TAG_MAX, /*< skip >*/
>                              ^~~~~~~~~~
>