-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Upgrade CVC5 version when fix for cvc5/cvc5#8900 is released #31
Labels
Windows
Issues relating to Windows support
Comments
Another reason to upgrade the CVC5 version is to bring in the changes from cvc5/cvc5#7512, which will make it possible to build CVC5 natively on Windows. |
RyanGlScott
added a commit
that referenced
this issue
Mar 13, 2023
This patch: * Upgrades CVC5 to version 1.0.5, which contains several key bugfixes and a new `--win64-native` flag, which allows CVC5 to be build natively on Windows. * Backports the `--win64-native` flag to CVC4, thereby allowing it to be built natively as well. * Tweaks the CI configuration to clean up how Python dependencies are installed, which are important to building CVC4 and CVC5. Fixes #4. By upgrading the CVC5 version, this also fixes #31.
RyanGlScott
added a commit
that referenced
this issue
Mar 14, 2023
This patch: * Upgrades CVC5 to version 1.0.5, which contains several key bugfixes and a new `--win64-native` flag, which allows CVC5 to be build natively on Windows. * Backports the `--win64-native` flag to CVC4, thereby allowing it to be built natively as well. * Tweaks the CI configuration to clean up how Python dependencies are installed, which are important to building CVC4 and CVC5. Fixes #4. By upgrading the CVC5 version, this also fixes #31.
RyanGlScott
added a commit
that referenced
this issue
Mar 14, 2023
This patch: * Upgrades CVC5 to version 1.0.5, which contains several key bugfixes and a new `--win64-native` flag, which allows CVC5 to be build natively on Windows. * Backports the `--win64-native` flag to CVC4, thereby allowing it to be built natively as well. * Tweaks the CI configuration to clean up how Python dependencies are installed, which are important to building CVC4 and CVC5. Fixes #4. By upgrading the CVC5 version, this also fixes #31.
RyanGlScott
added a commit
that referenced
this issue
Mar 15, 2023
This patch: * Upgrades CVC5 to version 1.0.5, which contains several key bugfixes and a new `--win64-native` flag, which allows CVC5 to be build natively on Windows. * Backports the `--win64-native` flag to CVC4, thereby allowing it to be built natively as well. * Tweaks the CI configuration to clean up how Python dependencies are installed, which are important to building CVC4 and CVC5. Fixes #4. By upgrading the CVC5 version, this also fixes #31.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently, CVC5 implements a fix for cvc5/cvc5#8900 that (1) is critical to making CVC5 work correctly with SBV on Windows (see LeventErkok/sbv#644), and (2) avoids an annoying issue where using CVC5 with SBV on macOS/Linux creates files named
"stdout"
. Ideally, we could just backport the fix for cvc5/cvc5#8900 to the most recent CVC5 release (1.0.4 at the time of writing), but that would not help on Windows, where we currently have to rely on using a cross-compiled binary that we download from CVC5's website. See #4. As a result, we would either have to work around #4 and build our own cross-compiled CVC5 first (which sounds painful), or we would have to wait for a new CVC5 release. I'm inclined to do the latter.The text was updated successfully, but these errors were encountered: