Add the ability for Kani to use a locally installed toolchain at runtime #3058
Assignees
Labels
[C] Feature / Enhancement
A new feature request or enhancement to an existing feature.
Comments
jaisnan
added
the
[C] Feature / Enhancement
jaisnan
added a commit
that referenced
this issue
Mar 7, 2024
Adds `--use-local-toolchain` to Kani's setup flow, which accepts a local toolchain and then uses that to finish the Kani setup. Some notes: 1. Why? This is mainly for installing GPG verified toolchains. 2. This is missing some cleanup and refactoring work, like ensuring that the user defined toolchain matches the one that Kani was built against etc. Marked as Todo, for later. Resolves [#3058](#3058) By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to use GPG verified toolchain components, Kani needs to be able to use locally installed toolchains.
These toolchains are typically fetched from the rust-lang server and then, verified with the associated
.ascfile.Kani's setup currently depends on rustup to install the toolchain, which doesn't allow us to use verified components. This also means having rustup itself as a dependency.
Being able to do this, will also enable us to remove rustup as a runtime dependency.
The text was updated successfully, but these errors were encountered: