mirror of
https://github.com/Xahau/xahaud.git
synced 2026-04-29 15:37:46 +00:00
1e698ed194
- Add BEAST_ENHANCED_LOGGING CMake option for build-time control - Implement file:line logging with customizable position (prefix/suffix/none) via LOG_LOCATION_POSITION env var (defaults to suffix for readability) - Add flexible timestamp formatting via LOG_DATE_FORMAT (date::format syntax) - Add local timezone support via LOG_DATE_LOCAL env var - Support customizable highlight colors via LOG_HIGHLIGHT_ESCAPE env var (red, green, yellow, blue, magenta, cyan, white, gray, orange, none) - Apply consistent highlighting to both file:line and partition:severity - Centralize all enhanced logging features in beast_EnhancedLogging module - Smart TTY detection with NO_COLOR/FORCE_COLOR support - Constexpr path stripping using SOURCE_ROOT_PATH - Move implementations to .cpp files to minimize recompilation - Update zlib to 1.3.1 to fix macOS 15.5 build issues - Enable date-tz library for timezone support Example output with defaults: 2025-Jul-26 15:20:07.124745 NetworkOPs:NFO STATE->connected [ripple/app/misc/NetworkOPs.cpp:2264] Environment variables: LOG_LOCATION_POSITION=suffix # or prefix, none LOG_HIGHLIGHT_ESCAPE=cyan # or red, green, yellow, etc LOG_DATE_FORMAT=%Y-%b-%d %r.%f %Z # custom timestamp format LOG_DATE_LOCAL=1 # use local timezone Zero runtime cost when disabled - all features are build-time conditional. Backward compatible - no changes when BEAST_ENHANCED_LOGGING is not defined.
These are modules and sources that support our CMake build.
== FindBoost.cmake ==
In order to facilitate updating to latest releases of boost, we've made a local copy of the FindBoost cmake module in our repo. The latest official version can generally be obtained here.
The latest version provided by Kitware can be tailored for use with the version of CMake that it ships with (typically the next upcoming CMake release). As such, the latest version from the repository might not work perfectly with older versions of CMake - for instance, the latest version might use features or properties only available in the version of CMake that it ships with. Given this, it's best to test any updates to this module with a few different versions of cmake.