You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if we are in test-e2e or mopro-example-app
and run first time with cargo build --bin ios/ cargo build --bin android/ mopro build
(for example, multiplier2 circuit)
It will generate a target and a build folder with binaries
and it caches for rust-witness circuits
so if we update the circuits and transpile for new circuits (e.g. keccak256_256_test circuit)
and run cargo build --bin ios/ cargo build --bin android/ mopro build again
it shows the error with cached circuits
e.g.
Problem
Currently if we are in
test-e2e
ormopro-example-app
and run first time with
cargo build --bin ios
/cargo build --bin android
/mopro build
(for example,
multiplier2
circuit)It will generate a
target
and abuild
folder with binariesand it caches for rust-witness circuits
so if we update the circuits and transpile for new circuits (e.g.
keccak256_256_test
circuit)and run
cargo build --bin ios
/cargo build --bin android
/mopro build
againit shows the error with cached circuits
e.g.
The current solution is to remove
target
andbuild
folder and run againDetails
There are several possible solutions
rust-witness
building time a lot, we don't need the cache.e.g.
mopro clean
to executerm -rf target && rm -rf build
Acceptance criteria
Users don't need to clean up
target
andbuild
, and won't get the error above when updating circuitsThe text was updated successfully, but these errors were encountered: