-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Book] Cairo execution artifacts #48
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey! Let's try to modify that a little bit, something like that:
- Page title and general context: add page title (see other doc files for reference) and some words on what we are trying to achieve, e.g. "executing cairo program to obtain execution trace, memory, and AIR inputs"
- Installation: list everything you need to do before you can run the program
2.0. Need rust
2.1. Corelib: I suggest to split the flow in two steps 1) get the cairo repo, it can be already in the system if you have Scarb or you need to clone manually 2) make a symbolic link to the corelib folder (moving is also ok but less preferrable)
2.2. Cairo1-run: it's better to use cargo install rather than clone the entire repo
@dmirgaleev For the first point. I'm not sure if what I understood is the thing that you meant. I was thinking about a title for the readme, not this: I put this "executing cairo program to obtain execution trace, memory, and AIR inputs". As the title of the readme. |
You shared me this some days ago: https://docs.swmansion.com/scarb/docs/reference/global-directories.html#cache-directory |
Waiting for all your feedback here mate @dmirgaleev |
I think we're done. Let me know sir! |
fa22115
to
c5fe44e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This the first version of the artifacts docs for the
execution.md
file. Issue #27