[logging-log4cxx] branch next_stable updated: Fix compilation errors when the cmake LOG4CXX_UNICHAR option is enabled

[swebb2066]

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

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


The following commit(s) were added to refs/heads/next_stable by this push:
     new b58d5df5 Fix compilation errors when the cmake LOG4CXX_UNICHAR option 
is enabled
b58d5df5 is described below

commit b58d5df52029c0439e500ae15a96508022e92cef
Author: Stephen Webb <stephen.w...@sabreautonomous.com.au>
AuthorDate: Mon Oct 10 21:03:14 2022 +1100

    Fix compilation errors when the cmake LOG4CXX_UNICHAR option is enabled
---
 src/main/cpp/messagebuffer.cpp | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/main/cpp/messagebuffer.cpp b/src/main/cpp/messagebuffer.cpp
index 7314fd83..e8244bf8 100644
--- a/src/main/cpp/messagebuffer.cpp
+++ b/src/main/cpp/messagebuffer.cpp
@@ -597,8 +597,10 @@ const std::basic_string<log4cxx::UniChar>& 
MessageBuffer::str(std::basic_ostream
 {
        return m_priv->ubuf->str(os);
 }
+#endif //LOG4CXX_UNICHAR_API || LOG4CXX_CFSTRING_API
 #endif // LOG4CXX_WCHAR_T_API
 
+#if LOG4CXX_UNICHAR_API || LOG4CXX_CFSTRING_API
 struct UniCharMessageBuffer::UniCharMessageBufferPrivate {
        UniCharMessageBufferPrivate() :
                stream(nullptr){}