-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Loading dependencies from an env var.
- Loading branch information
Showing
2 changed files
with
34 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
This crate uses the external submodules | ||
[pil-stark]([email protected]:powdr-labs/pil-stark.git) and | ||
[zkevm-prover](https://github.com/powdr-labs/zkevm-prover) to generate EStark ZK | ||
proofs from a rust friendly interface. | ||
|
||
At runtime, it needs to find the contents of the cargo's `OUT_DIR` (which is | ||
populated by `build.rs` at build time) otherwise execution will panic. This | ||
means that, if used as a cargo dependency from the same machine it is built, | ||
e.g. with `cargo run` or `cargo test`, it will work out of the box. But if the | ||
binaries are executed from another machine, e.g. from a `nextest` archive, it | ||
will fail unless the original `OUT_DIR` contents are manually provided. | ||
|
||
Cargo's `OUT_DIR` will typically be | ||
`target/<profile>/build/pil-stark-prover-<hash>/out`. If the original directory | ||
is not found at runtime, the library will search for its contents in the path | ||
pointed by environment variable `PIL_STARK_PROVER_DEPS`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters