From 58f56950848bae9c90da3873090c7698e0128b12 Mon Sep 17 00:00:00 2001 From: Liang Qi Date: Wed, 14 Aug 2019 11:13:36 +0200 Subject: Update bundled Freetype to 2.10.1 [ChangeLog][Freetype] Upgraded bundled Freetype version to 2.10.1. Fixes: QTBUG-77466 Change-Id: I1de8b8b03e0ffd0b17eeafff1017df7c638c9279 Reviewed-by: Eskil Abrahamsen Blomfeldt --- src/3rdparty/freetype/docs/DEBUG | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) (limited to 'src/3rdparty/freetype/docs/DEBUG') diff --git a/src/3rdparty/freetype/docs/DEBUG b/src/3rdparty/freetype/docs/DEBUG index 751eaf028a..828f29434d 100644 --- a/src/3rdparty/freetype/docs/DEBUG +++ b/src/3rdparty/freetype/docs/DEBUG @@ -88,14 +88,13 @@ debugging its code: for example as in #undef FT_COMPONENT - #define FT_COMPONENT trace_io - - The value of the FT_COMPONENT macro is an enumeration named - `trace_XXXX' where `XXXX' is one of the component names defined in - the internal file `internal/fttrace.h'. If you modify FreeType - source and insert new `trace_XXXX' macro, you must register it in - `fttrace.h'. If you insert or remove many trace macros, you can - check the undefined or the unused trace macro by + #define FT_COMPONENT io + + The value of the FT_COMPONENT macro is one of the component + names defined in the internal file `internal/fttrace.h'. If you + modify FreeType source and insert new FT_COMPONENT macro, you must + register it in `fttrace.h'. If you insert or remove many trace + macros, you can check the undefined or the unused trace macro by `src/tools/chktrcmp.py'. Each such component is assigned a `debug level', ranging from 0 to @@ -138,8 +137,8 @@ behaviour of FreeType at runtime. component1:level1 component2:level2 component3:level3 ... where `componentX' is the name of a tracing component, as defined - in `fttrace.h', but without the `trace_' prefix. `levelX' is the - corresponding level to use at runtime. + in `fttrace.h'. `levelX' is the corresponding level to use at + runtime. `any' is a special component name that will be interpreted as `any/all components'. For example, the following definitions @@ -191,7 +190,7 @@ behaviour of FreeType at runtime. ------------------------------------------------------------------------ -Copyright 2002-2018 by +Copyright (C) 2002-2019 by David Turner, Robert Wilhelm, and Werner Lemberg. This file is part of the FreeType project, and may only be used, -- cgit v1.2.3