Skip to content
This repository was archived by the owner on Jun 16, 2025. It is now read-only.

Conversation

capossele
Copy link
Contributor

With this addition, running cargo build from the root folder results in also building the forge ffi cli of the risc0-ethereum crate.

Solves #83

@capossele capossele self-assigned this Mar 5, 2024
@capossele capossele requested review from nategraf and Cardosaum March 5, 2024 15:22
@nategraf
Copy link
Member

nategraf commented Mar 6, 2024

Would it be possible to instead declare the ffi CLI a a dev dependency of risc0-ethereum-contracts, or possibly of the template workspace? I think this would be a cleaner way to achieve the same results, unless it doesn't work for some reason.

@capossele
Copy link
Contributor Author

Would it be possible to instead declare the ffi CLI a a dev dependency of risc0-ethereum-contracts, or possibly of the template workspace? I think this would be a cleaner way to achieve the same results, unless it doesn't work for some reason.

Yeah I've tried a couple of different approaches similar to what you have suggested but they were all unsuccessful mainly because cargo does not really like working with two different virtual workspaces

@nategraf
Copy link
Member

nategraf commented Mar 8, 2024

Hmmmm... maybe we can address this issue, and the issue with the location of Elf.sol and ImageID.sol by adding a Forge remapping as part of build.rs to point into the correct folder in the target directory, where the source code for both risc0-ethereum-contracts and risc0-forge-ffi will be cloned. If this works, it could also potentially allow us to drop risc0-ethereum-contracts as a submodule. It's a bit speculative, but I think worth trying.

@capossele
Copy link
Contributor Author

Closing for now, I'll reopen once risc0/risc0-ethereum#120 gets merged

@capossele capossele closed this May 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants