generic-library/g3log
1
0
Fork 0
mirror of https://github.com/KjellKod/g3log.git synced 2025-03-04 19:13:31 +01:00
Code Issues Projects Releases Wiki Activity

explanation of sinks

Browse Source
This commit is contained in:
kjell@kjell-win7.hsd1.co.comcast.net. 2014-01-17 08:24:35 +01:00
parent 3abf46b336
commit f5c89d67b6
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.markdown
View File

@ -31,6 +31,7 @@ CHECK(less > more) << "CHECK(false) triggers a FATAL message");
## What G3Log is: ## What G3Log is:
* ***G3log*** is the acting name for the third version of g2log and it stands for **g2log with dynamic sinks** * ***G3log*** is the acting name for the third version of g2log and it stands for **g2log with dynamic sinks**
* You can choose to use the default log receiver which saves all LOG calls to file, *or*, you can choose to use your own custom made log receivers, *or* you can use both, *or* as many sinks as you need.
* G3log is an asynchronous, "crash-safe" logger. You can read more about it here [[g2log version]]( * G3log is an asynchronous, "crash-safe" logger. You can read more about it here [[g2log version]](
http://www.codeproject.com/Articles/288827/g2log-An-efficient-asynchronous-logger-using-Cplus) http://www.codeproject.com/Articles/288827/g2log-An-efficient-asynchronous-logger-using-Cplus)
@ -173,7 +174,6 @@ Please use the Visual Studio 11 (2012) command prompt "Developer command prompt"
``` ```
cmake -DCMAKE_BUILD_TYPE=Release -G "Visual Studio 11" .. cmake -DCMAKE_BUILD_TYPE=Release -G "Visual Studio 11" ..
msbuild g2log_by_kjellkod.sln /p:Configuration=Release msbuild g2log_by_kjellkod.sln /p:Configuration=Release
Release\g2log-SIGSEGV.exe
``` ```
*** Building on *nix with Clang: *** Building on *nix with Clang:
@ -186,6 +186,7 @@ make
#Enjoy #Enjoy
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 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.