Background
The Motoko recipe in icp-cli-recipes is being rewritten to delegate compilation to mops build instead of invoking moc directly (see dfinity/icp-cli-recipes#26). This aligns Motoko with how the Rust recipe delegates to cargo build.
The new recipe uses {{_.canister.name}} (injected automatically by icp-cli via dfinity/icp-cli#567) to match against the [canisters] key in mops.toml — no extra recipe configuration: params needed.
Required changes
Tracked and implemented in #28. Three templates need updating once both blocking PRs are merged.
What moves to mops.toml
Before (icp.yaml / canister.yaml) |
After (mops.toml) |
main: src/main.mo |
[canisters.backend] main = "src/main.mo" |
candid: backend.did |
[canisters.backend] candid = "backend.did" |
args: --incremental-gc |
[canisters.backend] args = ["--incremental-gc"] |
Blocked on
Background
The Motoko recipe in icp-cli-recipes is being rewritten to delegate compilation to
mops buildinstead of invokingmocdirectly (see dfinity/icp-cli-recipes#26). This aligns Motoko with how the Rust recipe delegates tocargo build.The new recipe uses
{{_.canister.name}}(injected automatically by icp-cli via dfinity/icp-cli#567) to match against the[canisters]key inmops.toml— no extra recipeconfiguration:params needed.Required changes
Tracked and implemented in #28. Three templates need updating once both blocking PRs are merged.
What moves to
mops.tomlicp.yaml/canister.yaml)mops.toml)main: src/main.mo[canisters.backend] main = "src/main.mo"candid: backend.did[canisters.backend] candid = "backend.did"args: --incremental-gc[canisters.backend] args = ["--incremental-gc"]Blocked on
mops build_.canister.nameinto recipe template context icp-cli#567 —{{_.canister.name}}built-in variable