g3log | default logging sinks or you can add

 by   KjellKod C++ Version: 2.3 License: Unlicense

kandi X-RAY | g3log Summary

kandi X-RAY | g3log Summary

g3log is a C++ library typically used in Logging applications. g3log has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Most of the API that you need for using g3log is described in this readme. For more API documentation and examples please continue to read the API readme. Examples of what you will find here are:. G3log aims to keep all background logging to sinks with as little log overhead as possible to the logging sink and with as small "worst case latency" as possible. For this reason g3log is a good logger for many systems that deal with critical tasks. Depending on platform the average logging overhead will differ. On my 2010 laptop the average call, when doing extreme performance testing, will be about ~2 us. The worst case latency is kept stable with no extreme peaks, in spite of any sudden extreme pressure. I have a blog post regarding comparing worst case latency for g3log and other loggers which might be of interest. You can find it here: If you like this logger (or not) it would be nice with some feedback. That way I can improve g3log and g2log and it is also nice to see if someone is using it. If you have ANY questions or problems please do not hesitate in contacting me on my blog or at Hedstrom at KjellKod dot cc. This logger is available for free and all of its source code is public domain. A great way of saying thanks is to send a donation. It would go a long way not only to show your support but also to boost continued development.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              g3log has a medium active ecosystem.
              It has 830 star(s) with 270 fork(s). There are 52 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 2 open issues and 226 have been closed. On average issues are closed in 45 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of g3log is 2.3

            kandi-Quality Quality

              g3log has 0 bugs and 0 code smells.

            kandi-Security Security

              g3log has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              g3log code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              g3log is licensed under the Unlicense License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              g3log releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of g3log
            Get all kandi verified functions for this library.

            g3log Key Features

            No Key Features are available at this moment for g3log.

            g3log Examples and Code Snippets

            No Code Snippets are available at this moment for g3log.

            Community Discussions

            QUESTION

            How can I add the console (stdout) as a sink in g3log?
            Asked 2018-Jul-22 at 02:42

            I am new to g3log. I compiled and ran one of the examples I found in the repo, but was not able to ,modify it to print the log messages to the console rather than a file. The following lines from the example set the logger:

            ...

            ANSWER

            Answered 2018-Jul-22 at 02:42

            You could define a customized sink class with a message receiver function that forward the stripped message to console without formatting. Below is simplest form of the implementation:

            Source https://stackoverflow.com/questions/45941252

            QUESTION

            CMake include 3rd party project
            Asked 2017-Oct-11 at 08:39

            My background is in regular makefiles, I'm trying to convert our project to a CMake setup.

            I get stuck when I try to include g3log as a subproject.

            I added the following lines in my CMakeLists.txt. Note, that ../../external/g3log_src is the top level directory of the third party product.

            ...

            ANSWER

            Answered 2017-Oct-11 at 08:39

            When link with the 3d-party library, you should use library name, not a project name. In case of g3log, the library name is g3logger.

            Also, building 3d-party project should prepend using it:

            Source https://stackoverflow.com/questions/46683223

            QUESTION

            Ignore warnings in external modules when using CMake
            Asked 2017-Aug-27 at 12:05

            I am using CMake GUI (no version) with CMake 3.6.1. I am using an external module with add_subdirectory that shows me some warnings that I do not like (because of the annoying pollution):

            ...

            ANSWER

            Answered 2017-Jan-17 at 20:30

            Turning my comments into an answer

            That sounds like your external module does have a project() command. This resets the policies for this sub-module and below.

            To demonstrate a possible solution, lets say you have a external project as the following:

            g3log/CMakeLists.txt

            Source https://stackoverflow.com/questions/41695993

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install g3log

            You can download it from GitHub.

            Support

            Please look at API.markdown for detailed API documentation. Easy to use, clean syntax and a blazing fast logger. All the slow log I/O disk access is done in a background thread. This ensures that the LOG caller can immediately continue with other tasks and do not have to wait for the LOG call to finish. G3log provides logging, Design-by-Contract [#CHECK], and flush of log to file at shutdown. Buffered logs will be written to the sink before the application shuts down. It is thread safe, so using it from multiple threads is completely fine. It is CRASH SAFE. It will save the made logs to the sink before it shuts down. The logger will catch certain fatal events (Linux/OSX: signals, Windows: fatal OS exceptions and signals) , so if your application crashes due to, say a segmentation fault, SIGSEGV, it will log and save the crash and all previously buffered log entries before exiting. It is cross platform. Tested and used by me or by clients on OSX, Windows, Ubuntu, CentOS. G3log and G2log are used worldwide in commercial products as well as hobby projects. G2log is used since early 2011. The code is given for free as public domain. This gives the option to change, use, and do whatever with it, no strings attached. Two versions of g3log exists. Sinks are receivers of LOG calls. G3log comes with a default sink (the same as G3log uses) that can be used to save log to file. A sink can be of any class type without restrictions as long as it can either receive a LOG message as a std::string or as a g3::LogMessageMover. The std::string comes pre-formatted. The g3::LogMessageMover is a wrapped struct that contains the raw data for custom handling in your own sink. A sink is owned by the G3log and is added to the logger inside a std::unique_ptr. The sink can be called though its public API through a handler which will asynchronously forward the call to the receiving sink. It is crazy simple to create a custom sink. This example show what is needed to make a custom sink that is using custom log formatting but only using that for adding color to the default log formatting. The sink forwards the colored log to cout.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries

            Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link