refactor: use Cargo workspace

This commit is contained in:
Tien Do Nam
2026-08-03 14:06:24 +02:00
parent fdc0676e6b
commit 39e593100b
13 changed files with 536 additions and 9035 deletions
+1 -1
View File
@@ -22,7 +22,7 @@ This is a multi-language monorepo: a Flutter app on top of a Rust protocol imple
| `cli/` | Rust CLI crate (`localsend-cli`): interactive terminal client on top of `packages/core` (v2 HTTP + multicast). |
| `support/scripts/` | Release/packaging scripts (per-platform builds, MSIX, Inno Setup, FOSS stripping). |
There is no Cargo workspace; `packages/core`, `packages/localsend_isolates/rust`, `server`, and `cli` are independent crates.
The four Rust crates (`packages/core`, `packages/localsend_isolates/rust`, `server`, `cli`) form a single Cargo workspace rooted at the repository root: one shared `Cargo.lock` and `target/`, and `[profile.*]` settings live only in the root `Cargo.toml` (member profiles would be ignored). Cargokit still builds the plugin crate into its own target dir during Flutter builds.
Dependency direction: `app``localsend_isolates` → (`typed_isolates`, `rust_lib_localsend_app``localsend` core).
The app depends on **only** `localsend_isolates` — not on `flutter_rust_bridge`, `typed_isolates`, or the plugin crate directly.