Skip to content

google-glog 0.7.0-rc1

Pre-release
Pre-release
Compare
Choose a tag to compare
@sergiud sergiud released this 10 Jan 13:17
· 52 commits to master since this release
7e6fca9

In this release, glog underwent a major overhaul to take advantage of C++14 language and library features. Among the many changes, the public API has also been extended to use the more up-to-date standard library types (notably chrono).

Please take the opportunity to test this release candidate and report any issues. The final release of glog 0.7.0 is expected in early February 2024.

Highlights

  • C++14 is now the primary language standard
  • Emscripten support
  • Many fixes and enhancements

Compatibility

glog aims to maintain source compatibility with the previous release. We did our best to ensure such compatibility in this version as well. However, downstream clients must recompile against the new glog version due to ABI incompatible changes.

Deprecations

A number of functions, methods, and types have been deprecated in favor of more uniform interface.

Warning

Deprecated methods will be removed in glog 0.8.0. Please make sure to update your code.

  • google::LogMessage::getMessageTime has been superseded by google::LogMessage::time.
  • google::LogMessageTime::timestamp has been superseded by google::LogMessageTime::when.
  • google::LogMessageTime::gmtoff has been superseded by google::LogMessageTime::gmtoffset.
  • google::EnableLogCleaner(unsigned) has been superseded by google::EnableLogCleaner(std::chrono::minutes).
  • google::LogSink::send accepting std::tm (deprecated since glog 0.6.0) has been superseded by google::LogSink::send to accept google::LogMessageTime instead.
  • google::LogMessageInfo and the custom prefix callback accepting this type have been superseded by google::LogMessage. To customize the log line prefix use the google::InstallPrefixFormatter function instead of the google::InitGoogleLogging overload.

Further changes

  • google::LogSeverity has been converted to an unscoped enum. This can result in compilation issues if implicit conversion between an int and google::LogSeverity was erroneously assumed.
  • By default, CMake no longer generates the undocumented and untested pkg-config files. The support is now opt in which requires the CMake option WITH_PKGCONFIG to be explicitly set to ON.

What's Changed

New Contributors

Full Changelog: v0.6.0...v0.7.0-rc1