Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs(bb): How to use docker_interactive.sh #4220

Merged
merged 4 commits into from
Jan 25, 2024
Merged

docs(bb): How to use docker_interactive.sh #4220

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c9fc3b5
doc: How to use docker_interactive.sh
ludamad Jan 25, 2024
bb9fbe8
Update README.md
ludamad Jan 25, 2024
a853f67
Update README.md
ludamad Jan 25, 2024
d193be2
Merge branch 'master' into ad/doc/bb/docker_interactive.sh
ludamad Jan 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions barretenberg/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -249,3 +249,15 @@ CI will automatically run integration tests against Aztec. The tests in `circuit
CI will automatically run integration tests against Aztec's circuits which live [here](https://github.com/AztecProtocol/aztec-packages/tree/master/circuits). To change which Aztec branch or commit for CI to test against, modify [`.aztec-packages-commit`](./cpp/.aztec-packages-commit).

When working on a PR, you may want to point this file to a different Aztec branch or commit, but then it should probably be pointed back to master before merging.

### Testing locally in docker

A common issue that arises is that our CI system has a different compiler version e.g. namely for GCC. If you need to mimick the CI operating system locally you can use bootstrap_docker.sh or run dockerfiles directly. However, there is a more efficient workflow for iterative development:

```
cd barretenberg/cpp
./scripts/docker_interactive.sh
mv build build-native # your native build folders are mounted, but will not work! have to clear them
cmake --preset gcc ; cmake --build build
```
This will allow you to rebuild as efficiently as if you were running native code, and not have to see a full compile cycle.
Loading