Menu
▾
▴
[Log4cpp-commits] [git push]Log4cpp Git repository. branch master updated. REL_1.1.4rc3_Mar_12_2023-1-g4d83926
|
From: <log...@li...> - 2023-03-12 17:30:57
|
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 4d839263f6dad9df3e725c339d1c9b5a3e60850c (commit)
from 81e062c018c4642ab2e416084b4d43391ac087f4 (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 4d839263f6dad9df3e725c339d1c9b5a3e60850c
Author: Alexander Perepelkin <san...@us...>
Date: Sun Mar 12 20:30:31 2023 +0300
index.html
diff --git a/doc/html/index.html b/doc/html/index.html
index 36500c2..fc193af 100644
--- a/doc/html/index.html
+++ b/doc/html/index.html
@@ -1,320 +1,320 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html><head>
-<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"><title>Log for C++ Project</title>
-
-<link rel="stylesheet" type="text/css" href="styles.css">
-</head>
-<body>
-<div id="headerdiv">
-<h1><a id="begin">Log for C++ Project</a></h1>
+<html><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"><title>Log for C++ Project</title>
+
+<link rel="stylesheet" type="text/css" href="styles.css">
+</head>
+<body>
+<div id="headerdiv">
+<h1><a id="begin">Log for C++ Project</a></h1>
<!-- <a style="float: right;" href="http://sourceforge.net/"><img alt="Sourceforge" src="http://log4cpp.sourceforge.net/sflogo.png"> </a> -->
-<hr class="delimiter"></div>
-<div class="briefline">
- | <span> <a href="http://log4cpp.sourceforge.net/">Log
-for C++ Project
-Page on Sourceforge</a>
-</span> |
-<span>Last Published:
-2012-11-29</span> |</div>
-<hr class="delimiter">
-<div id="projectpage">
-<div id="navigationpanel" class="lightbackground">
-<h5>About log4cpp</h5>
-<ul>
-<li> <a title="What is log4cpp?" href="#whatis">What
-is log4cpp?</a> </li>
-<li> <a title="Download" href="#download">Download</a></li>
-<li =""><a title="License" href="#license">License</a>
-</li>
-<li =""><a title="API Documentation" href="#apidoc">API Documentation</a> </li>
-<li><a title="FAQ" href="#faq">FAQ</a>
-</li>
-</ul>
-<h5>How to use</h5>
-<ul>
-<li><a title="Simple example" href="#simpleexample">Simple
-example</a> </li>
-<li><a title="Properties file example" href="#propfile">Properties
-file example</a></li>
-<li><a title="Building" href="#building">Building</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>
-<li><a title="Git Repository" href="#git">Git
-Repository</a> </li>
-<li><a title="Releases" href="#releases">Releases</a>
-</li>
-<li><a title="Status" href="#status">Status</a>
-</li>
-<li><a title="People" href="#people">People</a>
-</li>
-<li> <a title="Other projects" href="#other">Other
-projects</a> </li>
-</ul>
-</div>
-<div id="contentpanel">
-<div class="chapter"><a id="whatis">
-<h2>What is log4cpp?</h2>
-</a>
-<p>Log4cpp is library of C++ classes for flexible logging to
-files, syslog, IDSA and other destinations.
-It is modeled after the <a href="http://jakarta.apache.org/log4j">Log4j</a>
-Java library, staying as close to their API as is reasonable.
-</p>
-<div class="chapter">
-<a id="download">
-<h2>Download</h2>
-</a>
-<p>Sources are available from SourceForges <a href="http://sourceforge.net/project/showfiles.php?group_id=15190">download
-page</a>.<br>
-We do not supply binaries, because of the numerous incompatible ABIs
-(e.g. g++ 2.95 vs 2.96 vs 3.0 vs 3.2) and different package
-formats.<br>
-A stable but older version of log4cpp is available in Debian stable,
-see <a href="http://packages.debian.org/stable/libs/">http://packages.debian.org/stable/libs/</a>.<br>
-FreeBSD users can find log4cpp in the ports collection,
-see <a href="http://www.freebsd.org/ports/devel.html">http://www.freebsd.org/ports/devel.html</a><br>
-Log4cpp includes support for building RPMs, so building your own from
-the source tar-ball is as simple as
-</p>
-<pre class="code">rpm -ta log4cpp-x.y.z.tar.gz<br></pre>
-<p></p>
+<hr class="delimiter"></div>
+<div class="briefline">
+ | <span> <a href="http://log4cpp.sourceforge.net/">Log
+for C++ Project
+Page on Sourceforge</a>
+</span> |
+<span>Last Published:
+2023-03-12</span> |</div>
+<hr class="delimiter">
+<div id="projectpage">
+<div id="navigationpanel" class="lightbackground">
+<h5>About log4cpp</h5>
+<ul>
+<li> <a title="What is log4cpp?" href="#whatis">What
+is log4cpp?</a> </li>
+<li> <a title="Download" href="#download">Download</a></li>
+<li =""><a title="License" href="#license">License</a>
+</li>
+<li =""><a title="API Documentation" href="#apidoc">API Documentation</a> </li>
+<li><a title="FAQ" href="#faq">FAQ</a>
+</li>
+</ul>
+<h5>How to use</h5>
+<ul>
+<li><a title="Simple example" href="#simpleexample">Simple
+example</a> </li>
+<li><a title="Properties file example" href="#propfile">Properties
+file example</a></li>
+<li><a title="Building" href="#building">Building</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>
+<li><a title="Git Repository" href="#git">Git
+Repository</a> </li>
+<li><a title="Releases" href="#releases">Releases</a>
+</li>
+<li><a title="Status" href="#status">Status</a>
+</li>
+<li><a title="People" href="#people">People</a>
+</li>
+<li> <a title="Other projects" href="#other">Other
+projects</a> </li>
+</ul>
+</div>
+<div id="contentpanel">
+<div class="chapter"><a id="whatis">
+<h2>What is log4cpp?</h2>
+</a>
+<p>Log4cpp is library of C++ classes for flexible logging to
+files, syslog, IDSA and other destinations.
+It is modeled after the <a href="http://jakarta.apache.org/log4j">Log4j</a>
+Java library, staying as close to their API as is reasonable.
+</p>
+<div class="chapter">
+<a id="download">
+<h2>Download</h2>
+</a>
+<p>Sources are available from SourceForges <a href="http://sourceforge.net/project/showfiles.php?group_id=15190">download
+page</a>.<br>
+We do not supply binaries, because of the numerous incompatible ABIs
+(e.g. g++ 2.95 vs 2.96 vs 3.0 vs 3.2) and different package
+formats.<br>
+A stable but older version of log4cpp is available in Debian stable,
+see <a href="http://packages.debian.org/stable/libs/">http://packages.debian.org/stable/libs/</a>.<br>
+FreeBSD users can find log4cpp in the ports collection,
+see <a href="http://www.freebsd.org/ports/devel.html">http://www.freebsd.org/ports/devel.html</a><br>
+Log4cpp includes support for building RPMs, so building your own from
+the source tar-ball is as simple as
+</p>
+<pre class="code">rpm -ta log4cpp-x.y.z.tar.gz<br></pre>
+<p></p>
<a href="#begin">^</a>
-</div>
-
-<div class="chapter">
-<h2><a id="building">Building Log4cpp</a></h2>
-<h3><a id="buildlinux">Autoconf</a></h3>
-<p>As of version 0.2.0 log4cpp can be build using autoconf on
-platforms
-that support it. Simply do:
-</p>
-<pre class="code">./configure<br>make<br>make check<br>make install<br></pre>
-<p>This will install log4cpp under /usr/local. To install in
-another localation specify --prefix=<location> when
-running configure.
-</p>
-<h3>Options for ./configure</h3>
-Besides the usual ./configure options like --prefix a few others are
-available:
-<dl>
-<dt>--with-idsa</dt>
-<dd>Include support for logging to IDSA (<a href="http://jade.cs.uct.ac.za/idsa/index.html">http://jade.cs.uct.ac.za/idsa/index.html</a>).
-This will give you an IdsaAppender Appender class.</dd>
-</dl>
-<dl>
-<dt>--with-omnithreads[=<path-to-omniORB>]</dt>
-<dd>Enable multi-threading support using omniORB4's omniThreads
-MT abstraction library (http://www.omniorb.org).
-configure expects the omnithread header files to reside in
-<path-to-omniORB>/include and the library in
-<path-to-omniORB</lib, i.e. not in a platform specific
-subdirectory. Create symlinks where necessary.<br>
-NB. omniORB4 is required: omniORB3 will not suffice as it lacks
-sufficient support for thread specific data.
-At the moment (August 2002) omniORB4 is in beta, however most parts and
-specifically the threading
-library appear to be quite stable.
-</dd>
-</dl>
-<dl>
-<dt>--with-pthreads</dt>
-<dd>Enable multi-threading support using the 'pthread' POSIX
-threads library.
-This option is mutually exclusive with --with-omnithreads.</dd>
-<dd></dd>
-</dl>
-<dl>
-<dt>--enable-doxyen</dt>
-<dd>Enables generation of API documentation by Dimitri van
-Heeschs Doxygen tool
-(http://www.doxygen.org/). Defaults to yes if doxygen can be found in
-the
-search path.</dd>
-</dl>
-<dl>
-<dt>--enable-html-docs</dt>
-<dd>If doxygen is enabled, have it generate HTML formatted
-documentation.</dd>
-</dl>
-<dl>
-<dt>--enable-latex-docs</dt>
-<dd>If doxygen is enabled, have it generate LaTeX formatted
-documentation.</dd>
-</dl>
-<dl>
-<dt> --enable-dot</dt>
-<dd>Let Doxygen use the 'dot' tool of GraphViz (<a href="http://www.graphviz.org/">http://www.graphviz.org</a>)
-todraw its graphs.</dd>
-</dl>
-<dl>
-<dt>--disable-remote-syslog </dt>
-<dd>Exclude RemoteSyslogAppender from build (included by default)</dd>
-</dl>
-<dl>
-<dt>--disable-smtp</dt>
-<dd>Exclude SmtpAppender from build (included by default)</dd>
-</dl>
-
-<p></p>
-<h3>Build notes for specific platforms</h3>
-<dl>
-<dt>*nix - g++ compiler</dt>
-<dd>Log4cpp should build whitout modification on any decent
-*nix system with g++ and GNU make. The primary development platform is
-RedHat Linux 7.3, which has g++ 2.96-rh, but the aim is to be
-compatible with from g++ 2.95 and up. When g++ 3.x has been widely
-adopted we may drop support for older g++ versions.</dd>
-</dl>
-<dl>
-<dt>Solaris - Sun CC compiler</dt>
-<dd>Compilation with Suns CC compiler requires setting some
-enviroment variables.
-Also static libraries appear not to work. In short do:
-<pre class="code">CC=CC CXX=CC LD="CC -KPIC" ./configure --disable-static<br></pre>
-</dd>
-</dl>
+</div>
+
+<div class="chapter">
+<h2><a id="building">Building Log4cpp</a></h2>
+<h3><a id="buildlinux">Autoconf</a></h3>
+<p>As of version 0.2.0 log4cpp can be build using autoconf on
+platforms
+that support it. Simply do:
+</p>
+<pre class="code">./configure<br>make<br>make check<br>make install<br></pre>
+<p>This will install log4cpp under /usr/local. To install in
+another localation specify --prefix=<location> when
+running configure.
+</p>
+<h3>Options for ./configure</h3>
+Besides the usual ./configure options like --prefix a few others are
+available:
+<dl>
+<dt>--with-idsa</dt>
+<dd>Include support for logging to IDSA (<a href="http://jade.cs.uct.ac.za/idsa/index.html">http://jade.cs.uct.ac.za/idsa/index.html</a>).
+This will give you an IdsaAppender Appender class.</dd>
+</dl>
+<dl>
+<dt>--with-omnithreads[=<path-to-omniORB>]</dt>
+<dd>Enable multi-threading support using omniORB4's omniThreads
+MT abstraction library (http://www.omniorb.org).
+configure expects the omnithread header files to reside in
+<path-to-omniORB>/include and the library in
+<path-to-omniORB</lib, i.e. not in a platform specific
+subdirectory. Create symlinks where necessary.<br>
+NB. omniORB4 is required: omniORB3 will not suffice as it lacks
+sufficient support for thread specific data.
+At the moment (August 2002) omniORB4 is in beta, however most parts and
+specifically the threading
+library appear to be quite stable.
+</dd>
+</dl>
+<dl>
+<dt>--with-pthreads</dt>
+<dd>Enable multi-threading support using the 'pthread' POSIX
+threads library.
+This option is mutually exclusive with --with-omnithreads.</dd>
+<dd></dd>
+</dl>
+<dl>
+<dt>--enable-doxyen</dt>
+<dd>Enables generation of API documentation by Dimitri van
+Heeschs Doxygen tool
+(http://www.doxygen.org/). Defaults to yes if doxygen can be found in
+the
+search path.</dd>
+</dl>
+<dl>
+<dt>--enable-html-docs</dt>
+<dd>If doxygen is enabled, have it generate HTML formatted
+documentation.</dd>
+</dl>
+<dl>
+<dt>--enable-latex-docs</dt>
+<dd>If doxygen is enabled, have it generate LaTeX formatted
+documentation.</dd>
+</dl>
+<dl>
+<dt> --enable-dot</dt>
+<dd>Let Doxygen use the 'dot' tool of GraphViz (<a href="http://www.graphviz.org/">http://www.graphviz.org</a>)
+todraw its graphs.</dd>
+</dl>
+<dl>
+<dt>--disable-remote-syslog </dt>
+<dd>Exclude RemoteSyslogAppender from build (included by default)</dd>
+</dl>
+<dl>
+<dt>--disable-smtp</dt>
+<dd>Exclude SmtpAppender from build (included by default)</dd>
+</dl>
+
+<p></p>
+<h3>Build notes for specific platforms</h3>
+<dl>
+<dt>*nix - g++ compiler</dt>
+<dd>Log4cpp should build whitout modification on any decent
+*nix system with g++ and GNU make. The primary development platform is
+RedHat Linux 7.3, which has g++ 2.96-rh, but the aim is to be
+compatible with from g++ 2.95 and up. When g++ 3.x has been widely
+adopted we may drop support for older g++ versions.</dd>
+</dl>
+<dl>
+<dt>Solaris - Sun CC compiler</dt>
+<dd>Compilation with Suns CC compiler requires setting some
+enviroment variables.
+Also static libraries appear not to work. In short do:
+<pre class="code">CC=CC CXX=CC LD="CC -KPIC" ./configure --disable-static<br></pre>
+</dd>
+</dl>
<dl>
<dt><a id="buildwindows">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>
</dl>
-<dl>
-<dt>Win32 - MSVC++ 6</dt>
-<dd>Use the workspace and project files in subdirectory msvc6.
-You may need to adjust include/log4cpp/config-win32.h and the project
-files to your particular needs.</dd>
-</dl>
-
-<dl>
-<dt>Win32 - MSVC++ 5</dt>
-<dd>Building log4cpp with MSVC++ 5 is not supported and will
-not be,
-unless someone can find a way to do so without mutilating the source
-code.</dd>
-</dl>
-<dl>
-<dt>Win32 - Borland C++ Builder 5</dt>
-<dd>Use the project and make files in subdirectory bcb5.</dd>
-</dl>
-<dl>
-<dt>Win32 - Cygwin</dt>
-<dd>Use './configure; make; make install'.<br>
-Be warned that there have been very few success or failure reports for
-this platform,
-so either it works very smoothly or noone actively uses log4cpp with
-Cygwin :-)
-</dd>
-</dl>
-<dl>
-<dt>OpenVMS</dt>
-<dt></dt>
-<dd>Edit include/log4cpp/config-openvms.h if you need
-different settings.<br>
-This has been tested on OpenVMS Alpha v7.3 and Compaq C++ V6.3-020
-only.
-</dd>
-<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,
-<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
-unix-style directory name is requied in the /include parameter.
-In this example, the pathis A1$DKBO:[USER.TONY.PROJECT.LOG4CPP.INCLUDE]<br>
-A repository directory is also specified here as
-A1$DKB0:[USER.TONY.PROJECT.LOG4CPP.REPOSITORY].<br>
-</dd>
-<dd>3) Create a static library, LOG4CPP.OLB
-<pre class="code">lib/create log4cpp<br></pre>
-</dd>
-<dd>4) Put all compiled OBJ files into the LOG4CPP.OLB
-<pre class="code">lib/insert log4cpp appender<br>lib/insert log4cpp appenderskeleton<br></pre>
-...etc<br>
-</dd>
-<dd>5) Link a program with log4cpp.olb. e.g:
-<pre class="code">cxx /include=("/a1\$dkb0/user/tony/project/log4cpp/include") /define=(__USE_STD_IOSTREAM,__OPENVMS__) testlog4cpp.cxx<br>cxxlink /repository=a1$dkb0:[user.tony.project.log4cpp.repository] testlog4cpp,log4cpp/library<br></pre>
-</dd>
-</dl>
-</dl>
+<dl>
+<dt>Win32 - MSVC++ 6</dt>
+<dd>Use the workspace and project files in subdirectory msvc6.
+You may need to adjust include/log4cpp/config-win32.h and the project
+files to your particular needs.</dd>
+</dl>
+
+<dl>
+<dt>Win32 - MSVC++ 5</dt>
+<dd>Building log4cpp with MSVC++ 5 is not supported and will
+not be,
+unless someone can find a way to do so without mutilating the source
+code.</dd>
+</dl>
+<dl>
+<dt>Win32 - Borland C++ Builder 5</dt>
+<dd>Use the project and make files in subdirectory bcb5.</dd>
+</dl>
+<dl>
+<dt>Win32 - Cygwin</dt>
+<dd>Use './configure; make; make install'.<br>
+Be warned that there have been very few success or failure reports for
+this platform,
+so either it works very smoothly or noone actively uses log4cpp with
+Cygwin :-)
+</dd>
+</dl>
+<dl>
+<dt>OpenVMS</dt>
+<dt></dt>
+<dd>Edit include/log4cpp/config-openvms.h if you need
+different settings.<br>
+This has been tested on OpenVMS Alpha v7.3 and Compaq C++ V6.3-020
+only.
+</dd>
+<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,
+<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
+unix-style directory name is requied in the /include parameter.
+In this example, the pathis A1$DKBO:[USER.TONY.PROJECT.LOG4CPP.INCLUDE]<br>
+A repository directory is also specified here as
+A1$DKB0:[USER.TONY.PROJECT.LOG4CPP.REPOSITORY].<br>
+</dd>
+<dd>3) Create a static library, LOG4CPP.OLB
+<pre class="code">lib/create log4cpp<br></pre>
+</dd>
+<dd>4) Put all compiled OBJ files into the LOG4CPP.OLB
+<pre class="code">lib/insert log4cpp appender<br>lib/insert log4cpp appenderskeleton<br></pre>
+...etc<br>
+</dd>
+<dd>5) Link a program with log4cpp.olb. e.g:
... 339 lines suppressed ...
hooks/post-receive
--
Log4cpp Git repository.
|
![http://log4cpp.sourceforge.net/sflogo.png">](http://log4cpp.sourceforge.net/sflogo.png">){kind=link}