Activity for Log library for C++
-
Alexander Perepelkin committed [31e5cd] on CodeGit
index.html, ChangeLog
-
fix type conversion warnings
-
Reformat source codebase automatically with clang-format-21
-
Adjust comments style for the fields, add missing
-
.clang-format, BasedOnStyle: LLVM, with only minor tweaks to stay closer to the most of the current files
-
index.html, v.1.1.5
-
FAQ answer for: Is log4cpp thread-safe?
-
log4cpp 1.1.5 released
-
Log library for C++ released /log4cpp-1.1.x (new)/log4cpp-1.1/log4cpp-1.1.5.tar.gz
-
index.html, styles.css
-
-
index.html
-
Cmake fixes, add RAD Studio 12 support
-
index.html, AUTHORS
-
DailyRollingFileAppender copyright
-
Tell autoreconf where to write aclocal macros
-
Tell autoreconf where to write aclocal macros
-
Added ACLOCAL_AMFLAGS in https://sourceforge.net/p/log4cpp/codegit/ci/1e61c8b67b4666e28e9b042aa5b01cda5536d82f/
-
CMake configuration update
-
-
Changelog, index.html
-
Cmake script update: support release and debug build types (defaults to release); build both static and shared libraries; pass necessary cpp macros for debug
-
Bump autoconf requirement to 2.59 only; have some fallbacks for modern macros; address bug #158;
-
Stop executing ./autogen.sh if any error happens
-
Please update outdated config.{guess,sub} in the release tarball
-
Files are updated in release log4cpp-1.1.5rc2
-
index.html
-
-
index.html
-
ChangeLog
-
Fix warnings given by gcc version 13.3.0
-
Fix spellings caught by Debian Patches
-
Autotools are updated with commit https://sourceforge.net/p/log4cpp/codegit/ci/99bf327fed032073cb6e3e5f5b19e4f8005a54b2/ , x86_64-pc-cygwin configuration is included. Passing the option explicitly like you mentioned: ./configure --build=x86_64-pc-cygwin is not required anymore This simple command should suffice: ./configure make
-
Hello @dinostray, Running the compilation with this change will cause the following warning issued for every source file when built on Ubuntu: ../include/log4cpp/threading/PThreads.hh:12: warning: "_GNU_SOURCE" redefined And that will introduce a lot of new warnings into compilation In details: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wall -Wno-unused -pedantic -MT AppenderSkeleton.lo -MD -MP -MF .deps/AppenderSkeleton.Tpo -c AppenderSkeleton.cpp -fPIC -DPIC -o .libs/AppenderSkeleton.o...
-
fix clang16 configure error
-
Hello @schievel1, Thanks a lot for your efforts in submitting this merge request! A similar fix for the same problem, implemented slightly differently, was committed a bit earlier here: https://sourceforge.net/p/log4cpp/codegit/ci/6448ecddc8d7fdf2179bbce574cec7341181295c/ and was released with the library version log4cpp-1.1.4 on 2023-05-01
-
ChangeLog
-
autoreconf -fi -I m4
-
autoupdate
-
Update .gitignore
-
Hello @andrewofc, Having the change suggested above in place causes the following error on at least system with uname Linux 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC after running ~/log4cpp-codegit$ cmake --build build CMake Error at CMakeLists.txt:89 (INSTALL): INSTALL DIRECTORY given no DESTINATION! The following amendment will fix the error: https://sourceforge.net/p/log4cpp/codegit/ci/8db27fdc27a3b992b53ff433e91f205990ac87de/ Could you ensure that this fix will also work for your...
-
Discussion 48226 further fix for clean cmake builds on x86 Ubuntu etc.
-
index.html
-
index.html
-
Ross Burton posted a comment on ticket #158
I've tested the change, it's essential for autoreconf to work out of the box, and the diff is simply adding that line to the top-level Makefile.am.
-
Hello Ross, thanks for noticing that. Would you mind getting a bit further with the contribution? * Have you tested the change already on some configuration? * Could you drop a diff for the change? * Could you give a brief description of the benefit gained with the update please?
-
Tell autoreconf where to write aclocal macros
-
The patch is released with log4cpp-1.1.5rc1 at https://sourceforge.net/projects/log4cpp/files/log4cpp-1.1.x%20%28new%29/log4cpp-1.1/log4cpp-1.1.5rc1.tar.gz/download
-
-
index.html
-
ChangeLog
-
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. After the patch /usr/local/include/log4cpp goes to /usr/local/include/aarch64-linux-gnu/log4cpp; /usr/local/lib/liblog4cpp.a goes to /usr/local/lib/aarch64-linux-gnu/liblog4cpp.a for arm64 toolchain.
-
Andrew E Page posted a comment on discussion Open Discussion
both runs configured for an arm64 toolchain root@a8b4e71c175e:/home/andrew/packages/log4cpp/build# make install Consolidate compiler generated dependencies of target log4cpp [100%] Built target log4cpp Install the project... -- Install configuration: "" -- Installing: /usr/local/include/log4cpp -- Installing: /usr/local/include/log4cpp/StringQueueAppender.hh ... -- Installing: /usr/local/include/log4cpp/BasicConfigurator.hh -- Installing: /usr/local/lib/liblog4cpp.a root@a8b4e71c175e:/home/andrew/packages/log4cpp/build#...
-
Andrew E Page, Thank you for this contribution. Could you elaborate a bit more please? Could you show what were the installation paths prior the fix (and after them, to compare them easily, and clearly see the clash)? For both x86/Arm64 compilations. -- Alexander
-
In the course of our development offirmware foran embedded device we build on Ubuntu 22.04 machinesfor native execution and cross-compile for our embedded device. When we install liblog4cpp-1.1.3 with apt for our host developmentand then install liblog4cpp for Arm64, we can no longer build for our x86 host and have toreinstall the x86 version, after which we can’tbuild for Arm64. We had a similar situationfor libyaml-cpp. That was solved by doing local CMakebuilds using our local CMAKE_TOOLCHAIN_FILE...
-
xctan created ticket #157
Please update outdated config.{guess,sub} in the release tarball
-
Pascal Jaeger created merge request #10 on CodeGit
fix clang16 configure error
-
mihai created ticket #36
Add bufferedIO support in FileAppender
-
Fix typos in index.html
-
-
Compilation error on tests with glibc >=2.31
-
Thanks for the patch! Merged into the repository at c383936fcb74f587ef529f618270b651a741859f (tag REL_1.1.4rc3_Mar_12_2023,), with the fallback to stime function where applicable. Available too as log4cpp-1.1.4rc3.tar.gz
-
index.html
-
-
Changelog
-
fix compilation warning
-
fix for bug 152: use timespec and clock_settime for c++11 and higher; use stime for glibc version lower than 2.31; none for other cases
-
Need to get rid of throw(...) specifications for C++17
-
Non-throwing dynamic exception specification throw() replaced with noexcept for modern compilers, version of the compiler determined by macro __cplusplus log4cpp-1.1.4rc2 Tag: REL_1.1.4rc2_Feb_10_2023, https://sourceforge.net/p/log4cpp/codegit/ci/231e96104cf739b03ca011c8b838ac834395e73d
-
Compilation warnings about std::auto_ptr<>
-
auto_ptr is replaced with unique_ptr conditionally, depending on the version of the compiler determined by macro __cplusplus REL_1.1.4rc2_Feb_10_2023, https://sourceforge.net/p/log4cpp/codegit/ci/231e96104cf739b03ca011c8b838ac834395e73d
-
-
* Replace obsolete auto_ptr removed in C++17 with newer unique_ptr since C++11
-
Replace obsolete auto_ptr removed in C++17 with newer unique_ptr since C++11
-
va_copy is here since c++11; fallback to simple copy if standard is not specified or is less than c++11
-
Replace obsolete auto_ptr removed in C++17 with newer unique_ptr since C++11
-
* Replace obsolete auto_ptr removed in C++17 with newer unique_ptr since C++11
-
Replace older Non-throwing dynamic exception specification throw() removed in C++20 with newer noexcept since C++11
-
Replace older Non-throwing dynamic exception specification throw() removed in C++20 with newer noexcept since C++11
-
C99 compatibility fix for snprintf configure check
-
https://sourceforge.net/p/log4cpp/codegit/ci/6448ecddc8d7fdf2179bbce574cec7341181295c/ log4cpp-1.1.4rc1
-
C99 compatibility fix for snprintf configure check
-
Thanks for the patch, Florian!
-
-
Patch #49 C99 compatibility fix for snprintf configure check. Do not call the undeclared exit function. This avoids an implicit function declaration, which future compilers may reject by default. (Florian Weimer, @fweimer)
-
Florian Weimer created ticket #49
C99 compatibility fix for snprintf configure check
-
Sanfour posted a comment on ticket #41
Hi Abhishek, am using VS 2019 and downloaded it with Nuget package. you need the winsock lib, either you put it by putting ws2_32.lib in Project properties -> Linker-> input -> additional dependys or just add pragma comment(lib,"ws2_32.lib") to your code.
-
Abhishek, Have you tried it before with earlier versions (like Visual Studio 2010)? I wonder whether it is the change in IDE version which causes the error or the fix above is insufficient.
-
Abhishek Mishra posted a comment on ticket #41
Hi Alexander, I am getting the same error on version 1.1.3 (using as a Nuget package). I am using VS2019 for the development. Can you please look into this, and if possible please provide any workaround or fix ? Thanks in advance.
-
NuGet package for VS2019 with vc142 toolset
-
Anton-V-K posted a comment on ticket #156
Yes, you're right. I've missed the point. The issue should be re-addressed to the NuGet package creator. It is built from https://github.com/MikeAirey/log4cpp , so I'll submit the issue there. This issue can now be closed.
-
Hello Anton, Log4cpp project is distributed in sources. Isn't this trouble related to the distribution of NuGet?
-
Though it is possible to copy \log4cpp.1.1.3\lib\native\v141 into \log4cpp.1.1.3\lib\native\v142 (or better create a link to save some space), the main problem is missing support of x64 configuration.
-
NuGet package for VS2019 with vc142 toolset
-
Adrien Destugues created ticket #155
Logging functions are not declared with printf-like "format" function attribute
-
builtin implementation of snprintf doesn't work
-
log4cpp Timestamp class does not seem year 2038 ready
-
Hello, Do you mind sharing the minimal project which I can run locally to reproduce the trouble? Thanks for the reminder.
-
Gang Li posted a comment on discussion Open Discussion
up
1 >
