z3
z3 copied to clipboard
Z3Prover
No debian build in the releases, since 4.8.5
Is there any reason to drop it? Our servers run Debian, and it was actually very useful to have a pre-packaged Z3 for debian.
We are using Azure Pipelines for the builds and releases. Prior to that we used self-hosted machines and the process was very manual and time consuming.
The default hosted builds are for ubuntu:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops
it is possible to use containers to build for custom platforms https://docs.microsoft.com/en-us/azure/devops/pipelines/ecosystems/containers/build-image?view=azure-devops
This is exploited in the generation of python pip releases.
https://github.com/Z3Prover/z3/blob/1f9aff04dfc19a8970847758edd93d31315f3a10/scripts/release.yml#L41
If you have a pointer to a suitable container for Debian, then you are invited to add a pull request that includes a build step (in release.yml and nightly.yaml) that produces the Debian binary as well.
Possibly a simpler approach is to leverage Manylinux (Centos) builds. From what I am informed, they would work (as a least common denominator). So then the update to the nightly and release scripts is simply to include Manylinux as a target in what gets published.
Thanks, Will definitely make a pull request with the Debian pipeline as soon as I have some time. Il 30 dic 2019, 06:43 +0100, Nikolaj Bjorner [email protected], ha scritto:
@algobardo do you have a reaction to what would work for you? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
I don't know about Azure pipelines, but this is what we (radare2) project use to generate Debian (and other) packages automatically with GitHub Actions:
- https://github.com/radareorg/radare2/blob/master/.github/workflows/release.yml
- https://github.com/radareorg/radare2/blob/master/sys/debian.sh
- https://github.com/radareorg/radare2/tree/master/sys/debian
I hope it might be useful somehow.
