-
Notifications
You must be signed in to change notification settings - Fork 141
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add support for dfx pull This PR adds support for DFX pull. Supporting dfx pull creates a dependency between the dev build and the prod build, because the wasm metadata needs to include the dev build hash. Furthermore, it is not only the prod_build but also the dev build that needs to include additional metadata. To make the feature work this PR: - changes the build order of the wasm modules so that the prod buid is built after the dev build to include the dev build hash - all II wasm files include additional metadata, _if_ the commit corresponds to a release (since no valid metadata can be generated for non-released wasms) - a script has been added to generate the above metadata - a script for wasm hash verification has been added since verification of wasm hashes is no more difficult (as it entails building II twice and including the hash of one module in the other) Future work: - Refactor build scripts to separate building the wasm from adding metadata. This would allow to build all wasms in parallel again, shortening CI times. - Try to move to `dfx` for wasm post-processing. This would remove a substantial amount of scripts / logic from our build process. * Adjust metadata init type and guide * Fix shell expansion issues and improve init guide * Improve comment * Update release build check with metadata * Implement review feedback Changes: - Change `dfx pull` to `dfx deps` - Fix a misleading comment (including the location I copied it from) - Introduced helper functions to print in color - Fix typos
- Loading branch information
Frederik Rothenberger
authored
Aug 24, 2023
1 parent
73e6ad3
commit 5ed4fc3
Showing
9 changed files
with
369 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.