Skip to content

fix(packaging): reuse provided dependency targets - #127

Merged
LimiNode merged 2 commits into
mainfrom
packaging/dependency-reuse
Sep 10, 2026
Merged

fix(packaging): reuse provided dependency targets#127
LimiNode merged 2 commits into
mainfrom
packaging/dependency-reuse

Conversation

@LimiNode

@LimiNode LimiNode commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • reuse an existing time_shield::time_shield target before package discovery or bundled fallback
  • guard installed dependency discovery for TimeShield, fmt, kurlyk, zlib, zstd, and mdbx-containers
  • retain the TimeShield 1.0.6 minimum when discovery is needed
  • add focused build-tree and installed-package regression scenarios with dependency discovery disabled

Validation

  • CMake configure/build and packaging checks pass on the supported CI matrices
  • build-tree test predefines time_shield::time_shield and disables TimeShield discovery
  • installed-package test predefines time_shield::time_shield and fmt::fmt, disables both discoveries, and builds a fmt-enabled consumer

This is separate from the documentation/API PRs #125 and #126.

Skip dependency discovery when parent or consumer projects already provide the exported targets, while retaining the TimeShield 1.0.6 requirement for discovery.
Exercise build-tree TimeShield reuse and installed-package reuse of parent-provided TimeShield and fmt targets with package discovery disabled. Run the focused integration scenarios in the Linux C++17 CI job so regressions cannot pass through the normal package consumer flow unnoticed.
@LimiNode
LimiNode force-pushed the packaging/dependency-reuse branch from a16160f to 7ceb567 Compare September 10, 2026 23:06
@LimiNode
LimiNode merged commit 7b029a6 into main Sep 10, 2026
14 checks passed
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.

1 participant