Repository navigation
Toolchain 0.4.1
Toolchain 0.4.1 preserves dependency linkage across SDK packaging and import, and retains TTX's scoped C-provider allocation policy.
Main update:
SDKs carry the static archives and shared runtimes required by their declared dependencies. Static and shared outputs can each select either dependency linkage through ordinary Bazel dependency targets. Separate repository names can import both variants of one published library in the same workspace.
TTX's retention provider remains C-authored so its tests exercise negotiation, substitution and release without relying on C++ provider helpers or native type identity.
Features:
- Bundle transitive static archives with their linker options and whole-archive initialization requirements.
- Preserve shared runtime dependencies and Windows import libraries alongside the consuming SDK.
- Separate an SDK repository's name from its published library identity with the optional
libraryfield. - Reuse matching declared dependency binaries and reject conflicting contents or static link requirements.
- Reject unavailable requested linkage variants instead of substituting another variant.
- Permit
mallocandfreeonly for modulettxatvalidation/providers/retention/provider.c. - Keep that allocation exception confined to those two operations and that complete source path in Toolchain's reviewed source policy.