> As suggested by you I have used `setvbuf()` function in
> `FT_Message()` function for printing logs on stderr in Full
> buffering mode when FT_DEBUG_LEVEL_TRACE macro is enabled.  For
> FT2_DEBUG=any:7 and command:
>
>   main.exe arial.ttf *qwertyuiopasdfghjklzxcvbnm *
>
> I have got the following results:
>
>   FT_LOGGING:           8 sec
>   FT_DEBUG_LEVEL_TRACE: 9 sec (stderr logs redirected to a file)

This looks reasonable now, thanks.  I still think, however, that the
difference is mainly due to the redirection.  Theoretically,
`FT_LOGGING` should be a tiny bit slower than `FT_DEBUG_LEVEL_TRACE`
since the former has a larger overhead.

What do your GNU/Linux tests show?

> I have also updated the GitHub repo containing this example @ here
> <https://github.com/Priyeshkkumar/FreeTypeExamples/tree/master/Windows/main>

Alas, I don't use Windows so I can't check this.


    Werner

Reply via email to