-
Notifications
You must be signed in to change notification settings - Fork 61
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
ARM build not published #60
Comments
This is probably obvious, but I would also list for completeness:
|
Related to 2.: Rust issues related to fully reproducible builds. |
My impression is that it will be a really long shot to achieve reproducible wasm builds across different processor architectures. In fact, we're currently using docker as an "isolation chamber" to achieve reproducible builds in a single architecture. By fixing things like the OS, compiler, installed libs and their versions, etc. We are breaking some (if not all) of those when switching to a different arch. What about Probably a recipe for trouble... perhaps your option 3., adding a suffix to ARM built artifacts, it's the best we can do for the moment. |
Created #63. |
Perhaps we can close this with #64. And create another, to document progress in the "reproducibility" area. Doing a Will check the same with un-optimized artifacts, and publish in a "reproducibility" branch. |
Based on #64, the following four images are published now:
|
In 0.12.2 / #56 an ARM build of this project was created. This makes the CosmWasm development experience of ARM users much smother as the contract compilation does not need to go through an emulator. However, during our testing it was discovered that this ARM build produces different compilation results than the Intel build. As a consequence the build is not proproducible.
I see a few things to move forward:
Input welcome. For now, the ARM build is not published to DockerHub.
The text was updated successfully, but these errors were encountered: