This is an automated email from the ASF dual-hosted git repository.

swebb2066 pushed a commit to branch improve_documentation
in repository https://gitbox.apache.org/repos/asf/logging-log4cxx.git

commit 3b336d1f1064341bc42166964d3b7b0d92360732
Author: Stephen Webb <[email protected]>
AuthorDate: Tue Apr 28 11:58:24 2026 +1000

    Clarify the roles of LOG4CXX_FORMAT_NAMESPACE and LOG4CXX_FORMAT_NS macros
---
 src/site/markdown/development/build-cmake.md.in | 2 +-
 src/site/markdown/macros-influencing-log4cxx.md | 9 +++++++--
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/src/site/markdown/development/build-cmake.md.in 
b/src/site/markdown/development/build-cmake.md.in
index d75e9954..e7271dc4 100644
--- a/src/site/markdown/development/build-cmake.md.in
+++ b/src/site/markdown/development/build-cmake.md.in
@@ -39,7 +39,7 @@ Building with CMake {#build-cmake}
 | PREFER_BOOST=on      | Prefer the Boost version of dependent libraries over 
standard library |
 | LOG4CXX_QT_SUPPORT=ON | Enable QString API and log4cxx::qt namespace 
methods, requires QtCore, choice of ON, OFF (default).                   |
 | LOG4CXX_EVENTS_AT_EXIT=ON | Prevent static data cleanup to allow event 
logging during application exit. |
-| LOG4CXX_FORMAT_NAMESPACE=std | Make the `LOG4CXX_[level]_FMT` macros use 
[std::format](https://en.cppreference.com/w/cpp/utility/format/format) by 
default.  |
+| LOG4CXX_FORMAT_NAMESPACE=std | Set LOG4CXX_FORMAT_NS=std when not provided 
in 
[target_compile_definitions](https://cmake.org/cmake/help/latest/command/target_compile_definitions.html).
 LOG4CXX_FORMAT_NS is used in `LOG4CXX_[level]_FMT` logging macros.  |
 
 # Examples
 
diff --git a/src/site/markdown/macros-influencing-log4cxx.md 
b/src/site/markdown/macros-influencing-log4cxx.md
index f85033ff..a84e0add 100644
--- a/src/site/markdown/macros-influencing-log4cxx.md
+++ b/src/site/markdown/macros-influencing-log4cxx.md
@@ -24,8 +24,13 @@ Preprocessor Macros Influencing Log4cxx 
{#macros-influencing-log4cxx}
 The following macros can be defined in client code to influence how log 
messages
 are set or not.
 
-These macros may be set on a per-file basis(in which case they must be before 
any
-Log4cxx includes), or they may be set globally via your build system.
+These macros may be set on a per-file basis
+(in which case they must be before any Log4cxx includes),
+or they may be set using your build system,
+for example, by using the
+[target_compile_definitions](https://cmake.org/cmake/help/latest/command/target_compile_definitions.html)
+cmake command.
+
 
 | Macro | Usage |
 | ----- | ----- |

Reply via email to