log4cplus
spdlog
| log4cplus | spdlog | |
|---|---|---|
| - | 48 | |
| 1,705 | 27,157 | |
| 0.2% | 0.9% | |
| 8.1 | 8.7 | |
| 13 days ago | 25 days ago | |
| C++ | C++ | |
| GNU General Public License v3.0 or later | MIT |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
log4cplus
We haven't tracked posts mentioning log4cplus yet.
Tracking mentions began in Dec 2020.
spdlog
-
Show HN: CXXStateTree – A modern C++ library for hierarchical state machines
You'll see a fairly even split amongst S-tier, "possibly headed for standardization" level libraries. I'd say there's a skew for `#ifndef` in projects that are more "aspires to the standard library" and for `#pragma once` in projects that are more focused on like a very specific vertical.
`#pragma once` seems to be far preferred for internal code, there's an argument for being strictly conforming if you're putting out a library. I've converted stuff to `#ifndef` before sharing it, but I think heavy C++ people usually type `#pragma once` in the privacy of their own little repository.
- `spdlog`: `#pragma once` https://github.com/gabime/spdlog/blob/v1.x/include/spdlog/as...
- `absl`: `#ifndef` https://github.com/abseil/abseil-cpp/blob/master/absl/base/a...
- `zpp_bits`: `#ifndef` https://github.com/eyalz800/zpp_bits/blob/main/zpp_bits.h
- `stringzilla` `#ifndef` https://github.com/ashvardanian/StringZilla/blob/main/includ...
-
🚀 Zyn 1.0.2 Released — Smarter Builds, Powerful Debugging, Cleaner Workflow
📦 Add Dependencies with zyn add You can now easily add Git-based dependencies to your project using a simple command: zyn add https://github.com/gabime/spdlog
-
Starting Up The Engine - Nikola Game Engine Devlog 1
Well, I wouldn't call it much of a "logger", per se. It is more like a collection of useful macros that print to the console using some pretty colors. I did have in mind to use the spdlog library since I do know that it is quite fast and has a lot of useful functionalities. But if you have read my previous devlog, you would know I do not like to use a lot of dependencies. I felt like logging was something that I could handle on my own without adding another dependency. And so I did. With a lot of help, though.
- Making a performant audio capture system⚡🚀💨
-
Show HN: Logfmtxx – Header only C++23 structured logging library using logfmt
Why a new lib instead of using or contributing to an existing one as spdlog?
https://github.com/gabime/spdlog
-
C++ Game Utility Libraries: for Game Dev Rustaceans
GitHub repo: gabime/spdlog
-
Easy logging A logging system for c++20
SpdLog https://github.com/gabime/spdlog
- Blackbox library for embedded systems
- cpp macros
-
Compiled logging library suggestion(s)?
The usual recommendation when logging libraries are brought up is spdlog, which is however header-only. It's available on Conan-center.
What are some alternatives?
glog - C++ implementation of the Google logging module
Boost.Log - Boost Logging library
easyloggingpp - C++ logging library. It is powerful, supports asynchronous low latency, extendable, light-weight, fast performing, thread and type safe and consists of many built-in features. It provides ability to write logs in your own customized format. It also provide support for logging your classes, third-party libraries, STL and third-party containers etc.
loguru - A lightweight C++ logging library