gitwtfhub

wtf is glog?

google/glog — explained in plain English

Analysis updated 2026-06-24

★ 7,365C++Audience · developerComplexity · 2/5Setup · moderate

TL;DR

glog was Google's C++ logging library, but it is no longer maintained and will be archived on 2025-06-30, the project recommends migrating to ng-log (a compatible community fork) or Abseil Logging (Google's actively maintained alternative).

Mindmap

mindmap
  root((glog))
    Status
      No longer maintained
      Archived 2025-06-30
    What it was
      C++ logging library
      Severity filtering
      File log output
    Alternatives
      ng-log community fork
      Abseil Logging
    Migration
      Compatible API
      Migration guide

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Migrate an existing C++ codebase from glog to ng-log using its compatible API and official migration instructions.

REASON 2

Replace glog in a project with Abseil Logging to stay on a Google-backed, actively maintained logging library.

What's in the stack?

C++

How it stacks up

google/glogfastled/fastledlibcpr/cpr
Stars7,3657,3877,329
LanguageC++C++C++
Setup difficultymoderateeasymoderate
Complexity2/52/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

This project is archived and no longer maintained, migrate to ng-log or Abseil Logging before the 2025-06-30 archive date.

Wtf does this do

Google Logging Library (glog) was a C++ library for recording log messages inside applications. It provided a stream-based API and helper macros that let developers write log statements that could be filtered by severity, written to files, and handled in various other ways at runtime. The project is no longer maintained. Google announced it will be archived on 2025-06-30. The README points to two alternatives: ng-log, a community-maintained fork with a compatible API and migration instructions, and Abseil Logging, a logging library from Google that is actively supported. Developers using glog in existing projects are encouraged to migrate to one of these.

Yoink these prompts

Prompt 1
How do I migrate a C++ project from glog to ng-log while keeping the same LOG() and DCHECK() macros?
Prompt 2
Show me how to add Abseil Logging to a C++ CMake project as a drop-in replacement for glog.
Prompt 3
What are the key API or behaviour differences between glog and ng-log that I need to update during migration?

Frequently asked questions

wtf is glog?

glog was Google's C++ logging library, but it is no longer maintained and will be archived on 2025-06-30, the project recommends migrating to ng-log (a compatible community fork) or Abseil Logging (Google's actively maintained alternative).

What language is glog written in?

Mainly C++. The stack also includes C++.

How hard is glog to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is glog for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.

Other repos in this lane