recipes: build with the features bento declares
Both recipes ran a bare `cargo tauri build`, so the Supernote feature --
now off by default -- would have been absent from every release binary.
They now append `feature_flags()`, which bento renders from the app's
`features` list in bento.toml. Keeping the list in the topology rather
than in each recipe means macOS and iOS pick it up for free when those
recipes land.
2 files changed,
+5 insertions,
-2 deletions
| 6 |
6 |
|
// then collect the AppImage + .deb. BB bundles its Rhai plugins + themes as
|
| 7 |
7 |
|
// resources at build time. OTA upload stays manual via the MNW dashboard.
|
| 8 |
8 |
|
//
|
|
9 |
+ |
// Cargo features come from the app's `features` list in bento.toml, not from
|
|
10 |
+ |
// this file, so every target ships the same set.
|
|
11 |
+ |
//
|
| 9 |
12 |
|
// Note: BB is NOT in the launch wave; ships in a later wave.
|
| 10 |
13 |
|
|
| 11 |
14 |
|
let h = build_host();
|
| 19 |
22 |
|
sh_ok(h, "cd " + r + " && . ~/.tauri/passwords.env && " +
|
| 20 |
23 |
|
"TAURI_SIGNING_PRIVATE_KEY=$HOME/.tauri/balanced-breakfast.key " +
|
| 21 |
24 |
|
"TAURI_SIGNING_PRIVATE_KEY_PASSWORD=$BB_TAURI_PASSWORD " +
|
| 22 |
|
- |
"cargo tauri build");
|
|
25 |
+ |
"cargo tauri build " + feature_flags());
|
| 23 |
26 |
|
|
| 24 |
27 |
|
step("collect");
|
| 25 |
28 |
|
let appimage = sh(h, "ls -t " + r + "/target/release/bundle/appimage/*.AppImage | head -1").stdout_tail.trim();
|
| 20 |
20 |
|
"$env:RUSTC_WRAPPER=''; " +
|
| 21 |
21 |
|
"$env:TAURI_SIGNING_PRIVATE_KEY='C:\\Users\\me\\.tauri\\balanced-breakfast.key'; " +
|
| 22 |
22 |
|
"$env:TAURI_SIGNING_PRIVATE_KEY_PASSWORD=$env:BB_TAURI_PASSWORD; " +
|
| 23 |
|
- |
"cd " + win_repo + "; cargo tauri build\"");
|
|
23 |
+ |
"cd " + win_repo + "; cargo tauri build " + feature_flags() + "\"");
|
| 24 |
24 |
|
|
| 25 |
25 |
|
step("collect");
|
| 26 |
26 |
|
collect(h, win_repo + "/target/release/bundle/msi/*.msi", "balanced_breakfast", v);
|