Skip to content

Conversation

@TheVeryDarkness
Copy link
Contributor

The release name 0.12.2 is in env.Z3_VERSION and may be changed to z3-0.12.2 if expected.

Uploaded files in my fork is in 0.12.2.

I didn't attach a SHA256 or other validation information, and this may be added in the future.

And I may also add some codes to let z3-sys download and test uploaded archive. But archive for Windows is just too big, can we cache downloaded archive globally? Or add an env var that points to the archive?

Use vcpkg-rs to manage z3 instead. A non-default feature vcpkg is added.

However, vcpkg-rs does not support wasm32 target currently. I created a pull request there at mcgoo/vcpkg-rs#53
Make emscripten visible to wasm32-unknown-unknown if emscripten is installed.
Z3_HEADER_VAR will disappear when the feature vcpkg is enabled.
Use is_err instead of pattern matching.
Added missing cargo:rerun-if-changed for header.
So that rust can continue to build.
By this, we can check whether the toolchain matches the vcpkg triplet.
@TheVeryDarkness TheVeryDarkness changed the title Upload z3 built by vcpkg as release assets in CI. Maybe test it in CI later. Upload z3 built by vcpkg as release assets in CI. Maybe test whether it works in CI later. Oct 29, 2023
@TheVeryDarkness
Copy link
Contributor Author

TheVeryDarkness commented Oct 29, 2023

The test failed because there is no such release 0.12.2 here and it doesn't have write access.

@toolCHAINZ toolCHAINZ added the test/lint/ci Updates to automated checks label Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test/lint/ci Updates to automated checks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants