Skip to content

chore: use lizardbyte-common in c++#221

Merged
ReenigneArcher merged 10 commits into
masterfrom
chore/use-lizardbyte-common-in-c++
Jun 30, 2026
Merged

chore: use lizardbyte-common in c++#221
ReenigneArcher merged 10 commits into
masterfrom
chore/use-lizardbyte-common-in-c++

Conversation

@ReenigneArcher

@ReenigneArcher ReenigneArcher commented Jun 29, 2026

Copy link
Copy Markdown
Member

Description

Use lizardbyte-common helpers. Also updates readme per LizardByte/roadmap#168.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

Integrate lizardbyte-common library into the test build. Configure the submodule to be built as part of tests and link it to the test target. Update the lizardbyte-common submodule to the latest version.
Switch the test build from the local googletest submodule to `lizardbyte::test_support`. This removes `third-party/googletest` from submodules, enables `LIZARDBYTE_COMMON_BUILD_TEST_SUPPORT`, updates test linking/dependencies, and replaces direct `<gtest/gtest.h>` includes with `<lizardbyte/common/testing.h>`. Several fixture classes were also updated to inherit from `BaseTest` to align with the shared test support layer.
Bump `third-party/lizardbyte-common` from `4c05418359b38b09f3d5802243858a1d462a3b06` to `0fcde420419c77fdde04ffb04ceda0b560bd1cfc` to bring in the latest upstream changes.
@codecov

codecov Bot commented Jun 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.16%. Comparing base (ee7ab0b) to head (c416017).
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #221   +/-   ##
=======================================
  Coverage   63.16%   63.16%           
=======================================
  Files          35       35           
  Lines        5261     5261           
  Branches     2385     2385           
=======================================
  Hits         3323     3323           
  Misses       1114     1114           
  Partials      824      824           
Flag Coverage Δ
Linux 63.36% <ø> (ø)
macOS 49.95% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee7ab0b...c416017. Read the comment docs.

Bumps `third-party/lizardbyte-common` from `0fcde42` to `d219f38` to pull in the latest upstream common library changes.
Update several unit test fixtures to explicitly call `BaseTest::SetUp()` and `BaseTest::TearDown()`. This ensures shared test harness initialization and cleanup always run, preventing cross-test state leakage and making filesystem-related tests more reliable.
Bumps `third-party/lizardbyte-common` from `d219f38` to `60bf936` to pull in the latest upstream changes from the shared common library.
Advance the `third-party/lizardbyte-common` submodule to commit `3f29834` to pull in the latest upstream shared changes.
@ReenigneArcher ReenigneArcher marked this pull request as ready for review June 29, 2026 18:46
Enhanced the README with a centered header layout featuring the Moonlight logo. Reorganized badges for better visual hierarchy, added emoji to section headings, and added the moonlight-logo.svg SVG asset. Also updated documentation links and removed the downloads badge.
Drops the Read the Docs badge from the README badge list and updates the `third-party/lizardbyte-common` submodule to commit `49aa8c6` to pull in the latest shared common changes.
@sonarqubecloud

Copy link
Copy Markdown

@ReenigneArcher ReenigneArcher merged commit 8c12a9a into master Jun 30, 2026
17 checks passed
@ReenigneArcher ReenigneArcher deleted the chore/use-lizardbyte-common-in-c++ branch June 30, 2026 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

c/c++: add env function wrappers for each platform

1 participant