Skip to content

cvcpkg(cvcgl): bump cvc_revision 2→3 — rebuild against guarded libcvc 3.4.0+cvc.3 #439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
transfix merged 1 commit into from
Sep 28, 2026
Merged

cvcpkg(cvcgl): bump cvc_revision 2→3 — rebuild against guarded libcvc 3.4.0+cvc.3 #439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion cvcpkg/recipes/cvcgl/recipe.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,13 @@ recipe:
# being an inert stub. imgui is now a runtime dep (the export links the relocatable
# $<INSTALL_INTERFACE:imgui>). Prior bundles shipped imgui-less, forcing consumers
# (cvcdbg demos) to rebuild cvcGL from source.
cvc_revision: 2
# Bumped 2 -> 3: republish cvcGL against libcvc 3.4.0+cvc.3. The published +cvc.2 was built
# against libcvc +cvc.2 and leaks an EXACT pin to it (cvcpkg records the built-against dep
# version); that dragged the pre-guard libcvc +cvc.2 into wasm-mt consumer installs, so
# `cvcpkg install cvc/libcvc cvc/cvcgl --platform wasm-mt` failed to resolve abseil (the gRPC
# deps that +cvc.3 guards off wasm). Rebuilding cvcGL against +cvc.3 re-points that pin to the
# guarded libcvc. cvcGL source itself is unchanged.
cvc_revision: 3
maintainer: "cvcpkg group"
maintainer_email: "info@cvcpkg.org"
maintainer_url: "https://cvcpkg.org"
Expand Down
Loading