spdlog
Our great sponsors
spdlog | Simple-Log | |
---|---|---|
44 | 2 | |
22,172 | 14 | |
- | - | |
8.9 | 0.0 | |
9 days ago | over 2 years ago | |
C++ | C++ | |
MIT | Boost Software License 1.0 |
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.
spdlog
-
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?
-
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 a good debugger can do
* Aha! In digging up the docs for NDC, I found this[1], which does mention a book for your reading list: "Patterns for Logging Diagnostic Messages" part of the book "Pattern Languages of Program Design 3" edited by Martin et al.
- Does spdlog::get()->critical throw?
-
CMake question
FetchContent_Declare( spdlog GIT_REPOSITORY https://github.com/gabime/spdlog GIT_TAG origin/v1.x ) FetchContent_MakeAvailable(spdlog)
-
I want to slightly change the behavior of the std::cout
Typically, you'd use a logging library to handle stuff like this. I personally like spdlog. You use different logger functions (info, warn, error) and depending on what level you have set for the logger (or globally) some of the functions become no-ops. E.g. When not running in verbose mode all spdlog::info() do nothing.
Simple-Log
-
[C++20] Simple-Log - multithreaded logging library
- The examples are at https://github.com/DNKpp/Simple-Log/tree/master/src/examples . I already thought of putting them into the root directory, probably will do that in the near future.
What are some alternatives?
glog - C++ implementation of the Google logging module
fmtlog - fmtlog is a performant fmtlib-style logging library with latency in nanoseconds.
Boost.Log - Boost Logging library
Ichor - C++20 Microservice Bootstrapping Framework
easyloggingpp - C++ logging library. It is extremely powerful, 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.
binary_log - Fast binary logger for C++
G3log - G3log is an asynchronous, "crash safe", logger that is easy to use with default logging sinks or you can add your own. G3log is made with plain C++14 (C++11 support up to release 1.3.2) with no external libraries (except gtest used for unit tests). G3log is made to be cross-platform, currently running on OSX, Windows and several Linux distros. See Readme below for details of usage.
Simple-Iterator - Simple to use iterator_interface for several iterator categories
plog - Portable, simple and extensible C++ logging library
lwlog - Very fast synchronous and asynchronous C++17 logging library
log4cplus - log4cplus is a simple to use C++ logging API providing thread-safe, flexible, and arbitrarily granular control over log management and configuration. It is modelled after the Java log4j API.
xtr - A Fast and Convenient C++ Logging Library for Low-latency or Real-time Environments