This repository was archived by the owner on Oct 31, 2023. It is now read-only.
fix: Add lib
crate-type to build
#215
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In the Noir PR that integrates acvm-0.13.0 updates there was a blocker where
acvm-backend-barretenberg
was not being found.I followed the hack mentioned in this issue (rust-lang/cargo#4881). That includes an extra
crate-type
. However, I think this most likely blows up the size of the binary that is created. And I noticed that cargo added a flag a few months ago to specify the crate type (rust-lang/cargo#10083). Should we update our manifest and flake on the Noir repo to handle this @phated ?I pushed this PR to test the Noir CI with the new dep: acvm-0.13.0-dbg. I will push this branch as a PR on the Noir repo once the final CI passes and a couple other updates are reconciled.
Problem*
Resolves
Summary*
This PR sets out to
Example
Before:
After:
Additional Context
PR Checklist*
cargo fmt
on default settings.