kc3-lang/freetype/docs/DEBUG
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
32cb5390 | 2025-09-06 06:14:03 | Update all copyright notices. | |
 |
47574f7e | 2024-01-27 11:11:22 | Update all copyright notices. | |
|
66cc4619 | 2023-05-23 12:54:48 | docs/DEBUG: Formatting. | |
|
65f85237 | 2023-01-17 09:18:25 | Update all copyright notices. | |
|
d0cfb4e1 | 2022-01-11 10:54:10 | Update all copyright notices. | |
|
ff407765 | 2021-06-25 09:19:51 | [base] Add trace level to logging output. Some practical debugging work has shown that displaying level X of an `FT_TRACEX` macro in the output of `FT2_DEBUG="... -v"` would be very helpful to find out which trace level should be selected. As an example, we now get output like ``` [ttobjs:2] TTF driver [ttobjs:2] SFNT driver [sfobjs:2] not a font using the SFNT container format [t1objs:2] Type 1 driver [stream:7] FT_Stream_EnterFrame: 14 bytes ``` * include/freetype/internal/ftdebug.h (FT_LOGGING_TAGX): New macro. (FT_LOG): Use it to add the trace level to the logging tag. * include/freetype/internal/fttrace.h (FT_MAX_TRACE_LEVEL_LENGTH): Adjust. * docs/DEBUG: Updated. | |
|
324612ce | 2021-01-31 14:28:44 | Always provide logging API. It's easier to have stubs if FT_DEBUG_LOGGING is undefined than to modify `ftexport.sym` conditionally. Problem reported by Alexei. * src/base/ftdebug.c: Include `ftlogging.h`. (FT_Trace_Set_Level, FT_Trace_Set_Default_Level, FT_Set_Log_Handler, FT_Set_Default_Log_Handler) [!FT_DEBUG_LOGGING]: Provide stubs. | |
|
b6e8a712 | 2021-01-17 07:18:48 | Update all copyright notices. | |
|
015a9b8d | 2020-12-07 10:27:42 | */*: s/FT_LOGGING/FT_DEBUG_LOGGING/. | |
 |
ab0ea068 | 2020-08-28 11:28:17 | Update logging related documentation. * docs/DEBUG: Updates related to `FT_LOGGING`. * README.git: Updates related to logging. |