Re: [ft] 64-bit compile warning in Visual Studio 2010

[suzuki toshiya]

Is this the output for 32-bit compilation?

Regards,
mpsuzuki

Wojciech Mamrak wrote:
> when compiling FT with Visual C++ 10.0 (32-bit) there are also few
> warnings. Here is the entire output:
> 
> 1>------ Rebuild All started: Project: freetype, Configuration:
> Release Win32 ------
> 1>  autofit.c
> 1>  bdf.c
> 1>  cff.c
> 1>  ftbase.c
> 1>  ftbitmap.c
> 1>  ftcache.c
> 1>  ftfstype.c
> 1>  ftgasp.c
> 1>freetype-2.4.11\src\bdf\bdflib.c(1162): warning C4100: 'lineno' :
> unreferenced formal parameter
> 1>  ftglyph.c
> 1>  ftgzip.c
> 1>freetype-2.4.11\src\bdf\bdflib.c(1295): warning C4100: 'lineno' :
> unreferenced formal parameter
> 1>  ftinit.c
> 1>  ftlzw.c
> 1>  ftstroke.c
> 1>  ftsystem.c
> 1>  smooth.c
> 1>  ftbbox.c
> 1>  ftmm.c
> 1>  ftpfr.c
> 1>  ftsynth.c
> 1>  fttype1.c
> 1>  ftwinfnt.c
> 1>  ftxf86.c
> 1>  ftlcdfil.c
> 1>freetype-2.4.11\src\smooth\ftsmooth.c(396): warning C4701:
> potentially uninitialized local variable 'bitmap' used
> 1>freetype-2.4.11\src\smooth\ftsmooth.c(396): warning C4701:
> potentially uninitialized local variable 'memory' used
> 1>freetype-2.4.11\src\smooth\ftsmooth.c(391): warning C4701:
> potentially uninitialized local variable 'x_shift' used
> 1>freetype-2.4.11\src\smooth\ftsmooth.c(391): warning C4701:
> potentially uninitialized local variable 'y_shift' used
> 1>  ftgxval.c
> 1>  ftotval.c
> 1>  ftpatent.c
> 1>..\..\..\src\base\ftlcdfil.c(79): warning C4146: unary minus
> operator applied to unsigned type, result still unsigned
> 1>..\..\..\src\base\ftlcdfil.c(88): warning C4146: unary minus
> operator applied to unsigned type, result still unsigned
> 1>..\..\..\src\base\ftlcdfil.c(92): warning C4146: unary minus
> operator applied to unsigned type, result still unsigned
> 1>..\..\..\src\base\ftlcdfil.c(140): warning C4146: unary minus
> operator applied to unsigned type, result still unsigned
> 1>..\..\..\src\base\ftlcdfil.c(150): warning C4146: unary minus
> operator applied to unsigned type, result still unsigned
> 1>..\..\..\src\base\ftlcdfil.c(154): warning C4146: unary minus
> operator applied to unsigned type, result still unsigned
> 1>  pcf.c
> 1>  pfr.c
> 1>  psaux.c
> 1>  pshinter.c
> 1>  psmodule.c
> 1>  raster.c
> 1>  sfnt.c
> 1>  truetype.c
> 1>  type1.c
> 1>  type1cid.c
> 1>  type42.c
> 1>  winfnt.c
> 1>freetype-2.4.11\src\type1\t1load.c(323): warning C4245: '=' :
> conversion from 'int' to 'FT_UInt', signed/unsigned mismatch
> 1>freetype-2.4.11\src\type1\t1load.c(336): warning C4245: '=' :
> conversion from 'int' to 'FT_UInt', signed/unsigned mismatch
> 1>freetype-2.4.11\src\type1\t1load.c(337): warning C4245: '=' :
> conversion from 'int' to 'FT_ULong', signed/unsigned mismatch
> 1>freetype-2.4.11\src\truetype\ttgxvar.c(706): warning C4245: '=' :
> conversion from 'int' to 'FT_UInt', signed/unsigned mismatch
> 1>  ftdebug.c
> 
> 2013/2/15 Werner LEMBERG <address@hidden>:
>>> I tried recompile FreeType for 64-bit in Visual Studio 2010. I get
>>> tons of warnings.  When I had compiled for 32-bit systems I got no
>>> wanings.  So my question is: "Can I safely ignore these warning when
>>> I compile FreeType for 64-bit systems (some of them looks like
>>> potential errors)?
>> Without seeing them it is hard to say.  Basically, there shouldn't be
>> warnings.
>>
>> Please download the current git and compile again, then send all
>> warnings to this list (probably compressed if necessary).
>>
>>
>>     Werner
>>
>> _______________________________________________
>> Freetype mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/freetype
> 
> _______________________________________________
> Freetype mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/freetype