Internal, generic logging API which you can use in any Babeltrace
subproject. This is the translation of `zf_log.h`.
Internal, generic logging API which you can use in any Babeltrace
subproject. This is the translation of `zf_log.h`.
Specific internal header to use within the library. This header
defines `BT_LOG_OUTPUT_LEVEL` to a custom, library-wide hidden
symbol which is the library's current log level before including
Specific internal header to use within the library. This header
defines `BT_LOG_OUTPUT_LEVEL` to a custom, library-wide hidden
symbol which is the library's current log level before including
-Do not include `<babeltrace2/logging-internal.h>` or
-`<babeltrace2/lib-logging-internal.h>` in a header which contains logging
+Do not include `<logging/log.h>` or
+`<lib/lib-logging.h>` in a header which contains logging
statements: this header could be included in source files which define a
different <<choose-a-tag,tag>>, for example. See
<<logging-instrument-header, Instrument a C header file>>.
statements: this header could be included in source files which define a
different <<choose-a-tag,tag>>, for example. See
<<logging-instrument-header, Instrument a C header file>>.
`_bt_log_global_output_lvl` symbol. In practice, we never use this
symbol, and always make sure that `BT_LOG_OUTPUT_LEVEL` is defined to a
module-wise or subproject-wise hidden symbol before including
`_bt_log_global_output_lvl` symbol. In practice, we never use this
symbol, and always make sure that `BT_LOG_OUTPUT_LEVEL` is defined to a
module-wise or subproject-wise hidden symbol before including
-`<babeltrace2/logging-internal.h>`. In the library,
-`<babeltrace2/lib-logging-internal.h>` does this job: just include this
+`<logging/log.h>`. In the library,
+`<lib/lib-logging.h>` does this job: just include this
example, there is one log level per component class, which makes log
filtering easier during execution.
+
example, there is one log level per component class, which makes log
filtering easier during execution.
+