Man page - fcft_log_init(3)
Packages contas this manual
- fcft_text_run_destroy(3)
- fcft_set_scaling_filter(3)
- fcft_rasterize_text_run_utf32(3)
- fcft_kerning(3)
- fcft_font_options_create(3)
- fcft_rasterize_char_utf32(3)
- fcft_init(3)
- fcft_font_options_destroy(3)
- fcft_precompose(3)
- fcft_from_name(3)
- fcft_log_init(3)
- fcft_clone(3)
- fcft_fini(3)
- fcft_from_name2(3)
- fcft_rasterize_grapheme_utf32(3)
- fcft_destroy(3)
- fcft_set_emoji_presentation(3)
- fcft_capabilities(3)
apt-get install libfcft-doc
Manual
| fcft_log_init(3) | fcft | fcft_log_init(3) |
NAME
fcft_log_init - configure logging in fcft
SYNOPSIS
#include <fcft/fcft.h>
void fcft_log_init(
DESCRIPTION
By default, fcft does not log anything; use fcft_log_init() to enable, and configure logging in fcft.
fcft_log_init() is typically called early, at program startup.
colorize is one of:
enum fcft_log_colorize {
FCFT_LOG_COLORIZE_NEVER,
FCFT_LOG_COLORIZE_ALWAYS,
FCFT_LOG_COLORIZE_AUTO
};
FCFT_LOG_COLORIZE_AUTO enables colors if stderr is a TTY.
if do_syslog is set, fcft will log to syslog, in addition to the regular logging on stderr.
Note that fcft does not call openlog(), even if do_syslog is set. Do this from the calling application. Before, or after calling fcft_log_init() does not matter, as long as it is done before calling any other fcft API functions.
Finally, log_level configures which types of log messages that will be shown.
enum fcft_log_class {
FCFT_LOG_CLASS_NONE,
FCFT_LOG_CLASS_ERROR,
FCFT_LOG_CLASS_WARNING,
FCFT_LOG_CLASS_INFO,
FCFT_LOG_CLASS_DEBUG
};
Note that this is not a bitmask; setting FCFT_LOG_CLASS_INFO, also enables FCFT_LOG_CLASS_WARNING and FCFT_LOG_CLASS_ERROR.
| 2025-03-22 | 3.3.1 |