Menu
▾
▴
[Log4cpp-commits] [git push]Log4cpp Git repository. branch master updated. REL_1.1.5rc1_Aug_23_2024-16-g7a6b6c8
|
From: <log...@li...> - 2025-11-08 22:10:39
|
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Log4cpp Git repository.".
The branch, master has been updated
via 7a6b6c83f1ce70f99ae39a752ed87e163c8825c4 (commit)
via 8f7b52632d8e7c3a00f514018acd0c7c3bcf910f (commit)
via 1e61c8b67b4666e28e9b042aa5b01cda5536d82f (commit)
via e51295bbfec32272e06051228ac16e3b18e3e288 (commit)
from 4958949bdb44cb2d4c71a2695faf53fd6c19ce0a (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://sourceforge.net/p/log4cpp/codegit/ci/
commit 7a6b6c83f1ce70f99ae39a752ed87e163c8825c4
Author: Alexander Perepelkin <san...@us...>
Date: Sat Nov 8 23:09:13 2025 +0100
Changelog, index.html
diff --git a/ChangeLog b/ChangeLog
index b0fc142..82fbbc1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2025-11-08 22:37 sanchouss_
+ * Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug
+ * MS Visual Studio 2022 can open log4cpp as CMake Project
+ * Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts
+
2025-10-30 13:15 sanchouss_
* Follow up with the fix for change from discussion 48226
* Update scripts for GNU Autotools shipped with the log4cpp distribution to their fresh versions
diff --git a/doc/html/index.html b/doc/html/index.html
index 7be880b..25a5177 100644
--- a/doc/html/index.html
+++ b/doc/html/index.html
@@ -15,7 +15,7 @@ for C++ Project
Page on Sourceforge</a>
</span> |
<span>Last Published:
-2025-10-30</span> |</div>
+2025-11-08</span> |</div>
<hr class="delimiter">
<div id="projectpage">
<div id="navigationpanel" class="lightbackground">
@@ -25,6 +25,12 @@ Page on Sourceforge</a>
is log4cpp?</a> </li>
<li> <a title="Download" href="#download">Download</a></li>
<li><a title="Building" href="#building">Building</a></li>
+ <ul>
+ <li><a title="Linux/*nix" href="#buildlinux">Linux/*nix, Autoconf</a> </li>
+ <li><a title="Linux/*nix" href="#buildcmake">Linux/*nix, CMake</a> </li>
+ <li><a title="Windows, prj files" href="#buildwindowsprj">Windows, prj files</a> </li>
+ <li><a title="Windows, CMake" href="#buildwindowscmake">Windows, CMake</a> </li>
+ </ul>
<li><a title="License" href="#license">License</a>
</li>
<li><a title="API Doxygen" href="#apidoxy">API Doxygen</a> </li>
@@ -38,10 +44,6 @@ is log4cpp?</a> </li>
example</a> </li>
<li><a title="Properties file example" href="#propfile">Properties
file example</a></li>
-<ul>
-<li> <a title="Linux/*nix" href="#buildlinux">Linux/*nix</a> </li>
-<li> <a title="Windows" href="#buildwindows">Windows</a> </li>
-</ul>
</ul>
<h5>Development</h5>
<ul>
@@ -92,7 +94,8 @@ the source tar-ball is as simple as
<div class="chapter">
<h2><a id="building">Building Log4cpp</a></h2>
<h3><a id="buildlinux">Autoconf</a></h3>
-<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system. CMake is secondary option.</p>
+<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system.
+ <a href="#buildcmake">CMake</a> is secondary option.</p>
<p>If file <code>./configure</code> is absent in project directory (as when the code is checked out from repository), run the following:</p>
<pre class="code">./autogen.sh<br></pre>
This will create <code>./configure</code> and the necessary <code>Makefile.in</code>'s. Then:
@@ -182,7 +185,7 @@ Also static libraries appear not to work. In short do:
</dd>
</dl>
<dl>
-<dt><a id="buildwindows">Win32 - VS2010</a></dt>
+<dt><a id="buildwindowsprj">Win32 - VS2010</a></dt>
<dd>Use the workspace and project files in subdirectory msvc10.
(You may need to adjust include/log4cpp/config-win32.h and the project
files to your particular needs)</dd>
@@ -225,7 +228,7 @@ only.
<dd>1) Copy the src and include directory (including all its
contents and subdirectories) onto your OpenVMS system.</dd>
<dd>2) Compile each source file (*.CPP and *.C in the src
-directory) one by one by the following command,
+directory) one by one with the following command,
<pre class="code">cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDER.CPP<br>cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDERSKELETON.CPP<br></pre>
...etc<br>
Please substitute a correct path for your include directory. A
@@ -246,6 +249,23 @@ A1$DKB0:[USER.TONY.PROJECT.LOG4CPP.REPOSITORY].<br>
</dd>
</dl>
</dl>
+
+<h3><a id="buildcmake">CMake</a></h3>
+ <p>Browse into the source code catalog (<code>log4cpp</code>) and run the following for Release build:</p>
+ <pre class="code">
+cmake -S . -B build_release -DCMAKE_BUILD_TYPE=Release<br>
+cmake --build build_release
+ </pre>
+ This will create <code>./build_release</code>, compile and build libraries into it.
+ <p>Debug build is analogous:</p>
+ <pre class="code">
+cmake -S . -B build_debug -DCMAKE_BUILD_TYPE=Debug<br>
+cmake --build build_debug
+ </pre>
+ <h3><a id="buildwindowscmake">Windows, CMake</a></h3>
+ <p>On Windows MS Visual Studio can open <code>log4cpp</code> catalog and detect that it is a CMake project.</p>
+ <p>Works since log4cpp 1.1.5. </p>
+
<a href="#begin">^</a>
</div>
@@ -605,7 +625,10 @@ WARNING: releases from the development branch are a 'work in progress' and may f
<small>
<dl>
-<dt>1.1.5rc2 - master branch (30 October 2025)</dt>
+<dt>1.1.5rc3 - master branch (08 November 2025)</dt>
+<dd>Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug</dd>
+<dd>MS Visual Studio 2022 can open log4cpp as CMake Project</dd>
+<dd>Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts</dd>
<dd>Discussion 48226 by Andrew E Page. Alter CMakeLists to allow installation paths for x86 and arm64 be different so that cross-compilation on single host is possible.</dd>
<dd>Update scripts for GNU Autotools shipped with the log4cpp distribution to their fresh versions</dd>
<dd>Fixes for compilation warnings and spellings caught by Debian Patch</dd>
http://sourceforge.net/p/log4cpp/codegit/ci/
commit 7a6b6c83f1ce70f99ae39a752ed87e163c8825c4
Author: Alexander Perepelkin <san...@us...>
Date: Sat Nov 8 23:09:13 2025 +0100
Changelog, index.html
diff --git a/ChangeLog b/ChangeLog
index b0fc142..82fbbc1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2025-11-08 22:37 sanchouss_
+ * Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug
+ * MS Visual Studio 2022 can open log4cpp as CMake Project
+ * Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts
+
2025-10-30 13:15 sanchouss_
* Follow up with the fix for change from discussion 48226
* Update scripts for GNU Autotools shipped with the log4cpp distribution to their fresh versions
diff --git a/doc/html/index.html b/doc/html/index.html
index 7be880b..25a5177 100644
--- a/doc/html/index.html
+++ b/doc/html/index.html
@@ -15,7 +15,7 @@ for C++ Project
Page on Sourceforge</a>
</span> |
<span>Last Published:
-2025-10-30</span> |</div>
+2025-11-08</span> |</div>
<hr class="delimiter">
<div id="projectpage">
<div id="navigationpanel" class="lightbackground">
@@ -25,6 +25,12 @@ Page on Sourceforge</a>
is log4cpp?</a> </li>
<li> <a title="Download" href="#download">Download</a></li>
<li><a title="Building" href="#building">Building</a></li>
+ <ul>
+ <li><a title="Linux/*nix" href="#buildlinux">Linux/*nix, Autoconf</a> </li>
+ <li><a title="Linux/*nix" href="#buildcmake">Linux/*nix, CMake</a> </li>
+ <li><a title="Windows, prj files" href="#buildwindowsprj">Windows, prj files</a> </li>
+ <li><a title="Windows, CMake" href="#buildwindowscmake">Windows, CMake</a> </li>
+ </ul>
<li><a title="License" href="#license">License</a>
</li>
<li><a title="API Doxygen" href="#apidoxy">API Doxygen</a> </li>
@@ -38,10 +44,6 @@ is log4cpp?</a> </li>
example</a> </li>
<li><a title="Properties file example" href="#propfile">Properties
file example</a></li>
-<ul>
-<li> <a title="Linux/*nix" href="#buildlinux">Linux/*nix</a> </li>
-<li> <a title="Windows" href="#buildwindows">Windows</a> </li>
-</ul>
</ul>
<h5>Development</h5>
<ul>
@@ -92,7 +94,8 @@ the source tar-ball is as simple as
<div class="chapter">
<h2><a id="building">Building Log4cpp</a></h2>
<h3><a id="buildlinux">Autoconf</a></h3>
-<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system. CMake is secondary option.</p>
+<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system.
+ <a href="#buildcmake">CMake</a> is secondary option.</p>
<p>If file <code>./configure</code> is absent in project directory (as when the code is checked out from repository), run the following:</p>
<pre class="code">./autogen.sh<br></pre>
This will create <code>./configure</code> and the necessary <code>Makefile.in</code>'s. Then:
@@ -182,7 +185,7 @@ Also static libraries appear not to work. In short do:
</dd>
</dl>
<dl>
-<dt><a id="buildwindows">Win32 - VS2010</a></dt>
+<dt><a id="buildwindowsprj">Win32 - VS2010</a></dt>
<dd>Use the workspace and project files in subdirectory msvc10.
(You may need to adjust include/log4cpp/config-win32.h and the project
files to your particular needs)</dd>
@@ -225,7 +228,7 @@ only.
<dd>1) Copy the src and include directory (including all its
contents and subdirectories) onto your OpenVMS system.</dd>
<dd>2) Compile each source file (*.CPP and *.C in the src
-directory) one by one by the following command,
+directory) one by one with the following command,
<pre class="code">cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDER.CPP<br>cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDERSKELETON.CPP<br></pre>
...etc<br>
Please substitute a correct path for your include directory. A
@@ -246,6 +249,23 @@ A1$DKB0:[USER.TONY.PROJECT.LOG4CPP.REPOSITORY].<br>
</dd>
</dl>
</dl>
+
+<h3><a id="buildcmake">CMake</a></h3>
+ <p>Browse into the source code catalog (<code>log4cpp</code>) and run the following for Release build:</p>
+ <pre class="code">
+cmake -S . -B build_release -DCMAKE_BUILD_TYPE=Release<br>
+cmake --build build_release
+ </pre>
+ This will create <code>./build_release</code>, compile and build libraries into it.
+ <p>Debug build is analogous:</p>
+ <pre class="code">
+cmake -S . -B build_debug -DCMAKE_BUILD_TYPE=Debug<br>
+cmake --build build_debug
+ </pre>
+ <h3><a id="buildwindowscmake">Windows, CMake</a></h3>
+ <p>On Windows MS Visual Studio can open <code>log4cpp</code> catalog and detect that it is a CMake project.</p>
+ <p>Works since log4cpp 1.1.5. </p>
+
<a href="#begin">^</a>
</div>
@@ -605,7 +625,10 @@ WARNING: releases from the development branch are a 'work in progress' and may f
<small>
<dl>
-<dt>1.1.5rc2 - master branch (30 October 2025)</dt>
+<dt>1.1.5rc3 - master branch (08 November 2025)</dt>
+<dd>Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug</dd>
+<dd>MS Visual Studio 2022 can open log4cpp as CMake Project</dd>
+<dd>Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts</dd>
<dd>Discussion 48226 by Andrew E Page. Alter CMakeLists to allow installation paths for x86 and arm64 be different so that cross-compilation on single host is possible.</dd>
<dd>Update scripts for GNU Autotools shipped with the log4cpp distribution to their fresh versions</dd>
<dd>Fixes for compilation warnings and spellings caught by Debian Patch</dd>
http://sourceforge.net/p/log4cpp/codegit/ci/
commit 7a6b6c83f1ce70f99ae39a752ed87e163c8825c4
Author: Alexander Perepelkin <san...@us...>
Date: Sat Nov 8 23:09:13 2025 +0100
Changelog, index.html
diff --git a/ChangeLog b/ChangeLog
index b0fc142..82fbbc1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2025-11-08 22:37 sanchouss_
+ * Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug
+ * MS Visual Studio 2022 can open log4cpp as CMake Project
+ * Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts
+
2025-10-30 13:15 sanchouss_
* Follow up with the fix for change from discussion 48226
* Update scripts for GNU Autotools shipped with the log4cpp distribution to their fresh versions
diff --git a/doc/html/index.html b/doc/html/index.html
index 7be880b..25a5177 100644
--- a/doc/html/index.html
+++ b/doc/html/index.html
@@ -15,7 +15,7 @@ for C++ Project
Page on Sourceforge</a>
</span> |
<span>Last Published:
-2025-10-30</span> |</div>
+2025-11-08</span> |</div>
<hr class="delimiter">
<div id="projectpage">
<div id="navigationpanel" class="lightbackground">
@@ -25,6 +25,12 @@ Page on Sourceforge</a>
is log4cpp?</a> </li>
<li> <a title="Download" href="#download">Download</a></li>
<li><a title="Building" href="#building">Building</a></li>
+ <ul>
+ <li><a title="Linux/*nix" href="#buildlinux">Linux/*nix, Autoconf</a> </li>
+ <li><a title="Linux/*nix" href="#buildcmake">Linux/*nix, CMake</a> </li>
+ <li><a title="Windows, prj files" href="#buildwindowsprj">Windows, prj files</a> </li>
+ <li><a title="Windows, CMake" href="#buildwindowscmake">Windows, CMake</a> </li>
+ </ul>
<li><a title="License" href="#license">License</a>
</li>
<li><a title="API Doxygen" href="#apidoxy">API Doxygen</a> </li>
@@ -38,10 +44,6 @@ is log4cpp?</a> </li>
example</a> </li>
<li><a title="Properties file example" href="#propfile">Properties
file example</a></li>
-<ul>
-<li> <a title="Linux/*nix" href="#buildlinux">Linux/*nix</a> </li>
-<li> <a title="Windows" href="#buildwindows">Windows</a> </li>
-</ul>
</ul>
<h5>Development</h5>
<ul>
@@ -92,7 +94,8 @@ the source tar-ball is as simple as
<div class="chapter">
<h2><a id="building">Building Log4cpp</a></h2>
<h3><a id="buildlinux">Autoconf</a></h3>
-<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system. CMake is secondary option.</p>
+<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system.
+ <a href="#buildcmake">CMake</a> is secondary option.</p>
<p>If file <code>./configure</code> is absent in project directory (as when the code is checked out from repository), run the following:</p>
<pre class="code">./autogen.sh<br></pre>
This will create <code>./configure</code> and the necessary <code>Makefile.in</code>'s. Then:
@@ -182,7 +185,7 @@ Also static libraries appear not to work. In short do:
</dd>
</dl>
<dl>
-<dt><a id="buildwindows">Win32 - VS2010</a></dt>
+<dt><a id="buildwindowsprj">Win32 - VS2010</a></dt>
<dd>Use the workspace and project files in subdirectory msvc10.
(You may need to adjust include/log4cpp/config-win32.h and the project
files to your particular needs)</dd>
@@ -225,7 +228,7 @@ only.
<dd>1) Copy the src and include directory (including all its
contents and subdirectories) onto your OpenVMS system.</dd>
<dd>2) Compile each source file (*.CPP and *.C in the src
-directory) one by one by the following command,
+directory) one by one with the following command,
<pre class="code">cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDER.CPP<br>cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDERSKELETON.CPP<br></pre>
...etc<br>
Please substitute a correct path for your include directory. A
@@ -246,6 +249,23 @@ A1$DKB0:[USER.TONY.PROJECT.LOG4CPP.REPOSITORY].<br>
</dd>
</dl>
</dl>
+
+<h3><a id="buildcmake">CMake</a></h3>
+ <p>Browse into the source code catalog (<code>log4cpp</code>) and run the following for Release build:</p>
+ <pre class="code">
+cmake -S . -B build_release -DCMAKE_BUILD_TYPE=Release<br>
+cmake --build build_release
+ </pre>
+ This will create <code>./build_release</code>, compile and build libraries into it.
+ <p>Debug build is analogous:</p>
+ <pre class="code">
+cmake -S . -B build_debug -DCMAKE_BUILD_TYPE=Debug<br>
+cmake --build build_debug
+ </pre>
+ <h3><a id="buildwindowscmake">Windows, CMake</a></h3>
+ <p>On Windows MS Visual Studio can open <code>log4cpp</code> catalog and detect that it is a CMake project.</p>
+ <p>Works since log4cpp 1.1.5. </p>
+
<a href="#begin">^</a>
</div>
@@ -605,7 +625,10 @@ WARNING: releases from the development branch are a 'work in progress' and may f
<small>
<dl>
-<dt>1.1.5rc2 - master branch (30 October 2025)</dt>
+<dt>1.1.5rc3 - master branch (08 November 2025)</dt>
+<dd>Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug</dd>
+<dd>MS Visual Studio 2022 can open log4cpp as CMake Project</dd>
+<dd>Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts</dd>
<dd>Discussion 48226 by Andrew E Page. Alter CMakeLists to allow installation paths for x86 and arm64 be different so that cross-compilation on single host is possible.</dd>
<dd>Update scripts for GNU Autotools shipped with the log4cpp distribution to their fresh versions</dd>
<dd>Fixes for compilation warnings and spellings caught by Debian Patch</dd>
http://sourceforge.net/p/log4cpp/codegit/ci/
commit 7a6b6c83f1ce70f99ae39a752ed87e163c8825c4
Author: Alexander Perepelkin <san...@us...>
Date: Sat Nov 8 23:09:13 2025 +0100
Changelog, index.html
diff --git a/ChangeLog b/ChangeLog
index b0fc142..82fbbc1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2025-11-08 22:37 sanchouss_
+ * Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug
+ * MS Visual Studio 2022 can open log4cpp as CMake Project
+ * Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts
+
2025-10-30 13:15 sanchouss_
* Follow up with the fix for change from discussion 48226
* Update scripts for GNU Autotools shipped with the log4cpp distribution to their fresh versions
diff --git a/doc/html/index.html b/doc/html/index.html
index 7be880b..25a5177 100644
--- a/doc/html/index.html
+++ b/doc/html/index.html
@@ -15,7 +15,7 @@ for C++ Project
Page on Sourceforge</a>
</span> |
<span>Last Published:
-2025-10-30</span> |</div>
+2025-11-08</span> |</div>
<hr class="delimiter">
<div id="projectpage">
<div id="navigationpanel" class="lightbackground">
@@ -25,6 +25,12 @@ Page on Sourceforge</a>
is log4cpp?</a> </li>
<li> <a title="Download" href="#download">Download</a></li>
<li><a title="Building" href="#building">Building</a></li>
+ <ul>
+ <li><a title="Linux/*nix" href="#buildlinux">Linux/*nix, Autoconf</a> </li>
+ <li><a title="Linux/*nix" href="#buildcmake">Linux/*nix, CMake</a> </li>
+ <li><a title="Windows, prj files" href="#buildwindowsprj">Windows, prj files</a> </li>
+ <li><a title="Windows, CMake" href="#buildwindowscmake">Windows, CMake</a> </li>
+ </ul>
<li><a title="License" href="#license">License</a>
</li>
<li><a title="API Doxygen" href="#apidoxy">API Doxygen</a> </li>
@@ -38,10 +44,6 @@ is log4cpp?</a> </li>
example</a> </li>
<li><a title="Properties file example" href="#propfile">Properties
file example</a></li>
-<ul>
-<li> <a title="Linux/*nix" href="#buildlinux">Linux/*nix</a> </li>
-<li> <a title="Windows" href="#buildwindows">Windows</a> </li>
-</ul>
</ul>
<h5>Development</h5>
<ul>
@@ -92,7 +94,8 @@ the source tar-ball is as simple as
<div class="chapter">
<h2><a id="building">Building Log4cpp</a></h2>
<h3><a id="buildlinux">Autoconf</a></h3>
-<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system. CMake is secondary option.</p>
+<p>The project uses <a href="https://www.gnu.org/software/automake/">GNU Autotools</a> as primary build system.
+ <a href="#buildcmake">CMake</a> is secondary option.</p>
<p>If file <code>./configure</code> is absent in project directory (as when the code is checked out from repository), run the following:</p>
<pre class="code">./autogen.sh<br></pre>
This will create <code>./configure</code> and the necessary <code>Makefile.in</code>'s. Then:
@@ -182,7 +185,7 @@ Also static libraries appear not to work. In short do:
</dd>
</dl>
<dl>
-<dt><a id="buildwindows">Win32 - VS2010</a></dt>
+<dt><a id="buildwindowsprj">Win32 - VS2010</a></dt>
<dd>Use the workspace and project files in subdirectory msvc10.
(You may need to adjust include/log4cpp/config-win32.h and the project
files to your particular needs)</dd>
@@ -225,7 +228,7 @@ only.
<dd>1) Copy the src and include directory (including all its
contents and subdirectories) onto your OpenVMS system.</dd>
<dd>2) Compile each source file (*.CPP and *.C in the src
-directory) one by one by the following command,
+directory) one by one with the following command,
<pre class="code">cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDER.CPP<br>cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) /repository=a1$dkb0:[user.tony.project.log4cpp.repository] APPENDERSKELETON.CPP<br></pre>
...etc<br>
Please substitute a correct path for your include directory. A
@@ -246,6 +249,23 @@ A1$DKB0:[USER.TONY.PROJECT.LOG4CPP.REPOSITORY].<br>
</dd>
</dl>
</dl>
+
+<h3><a id="buildcmake">CMake</a></h3>
+ <p>Browse into the source code catalog (<code>log4cpp</code>) and run the following for Release build:</p>
+ <pre class="code">
+cmake -S . -B build_release -DCMAKE_BUILD_TYPE=Release<br>
+cmake --build build_release
+ </pre>
+ This will create <code>./build_release</code>, compile and build libraries into it.
+ <p>Debug build is analogous:</p>
+ <pre class="code">
+cmake -S . -B build_debug -DCMAKE_BUILD_TYPE=Debug<br>
+cmake --build build_debug
+ </pre>
+ <h3><a id="buildwindowscmake">Windows, CMake</a></h3>
+ <p>On Windows MS Visual Studio can open <code>log4cpp</code> catalog and detect that it is a CMake project.</p>
+ <p>Works since log4cpp 1.1.5. </p>
+
<a href="#begin">^</a>
</div>
@@ -605,7 +625,10 @@ WARNING: releases from the development branch are a 'work in progress' and may f
<small>
<dl>
-<dt>1.1.5rc2 - master branch (30 October 2025)</dt>
+<dt>1.1.5rc3 - master branch (08 November 2025)</dt>
+<dd>Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug</dd>
+<dd>MS Visual Studio 2022 can open log4cpp as CMake Project</dd>
+<dd>Address bug #158; Add path to m4 macros for autoreconf in GNU Autotools scripts</dd>
<dd>Discussion 48226 by Andrew E Page. Alter CMakeLists to allow installation paths for x86 and arm64 be different so that cross-compilation on single host is possible.</dd>
... 13 lines suppressed ...
hooks/post-receive
--
Log4cpp Git repository.
|
