bvandeusenandClaude Opus 5
0a7480cf9b
Android becomes a native Kotlin client over this same code (Scribe note 2730), so
the local store and sync engine stop being modules of the desktop app and become
`thoughtsync-core`, a crate with no UI framework in it at all.
This is a move, not a rewrite, and the measurement is why: every file in local/
and sync/ already carried ZERO Tauri references — 4,980 of 6,372 lines. The
coupling was 473 lines of command shim, which stays behind in the desktop crate
as src/commands/. Kept as git renames so history follows the files.
The desktop imports them under their old names (`use thoughtsync_core::{local,
sync}`) so every call site reads exactly as before. What moved is where they
live, not what they are.
Two things a workspace changes that are easy to miss, both caught before pushing:
[profile.release] now lives at the workspace ROOT. Cargo silently ignores
profiles declared by a non-root member — leaving it in the desktop crate would
have dropped lto/strip/opt-level from every release build with only a warning.
And a workspace shares ONE target dir, so the bundles moved from
desktop/src-tauri/target to target/. Thirteen references across publish-release,
debundle-graphics, verify.sh, package-prebuilt and the workflow now point there.
Pinning target-dir back would have been the smaller diff, but the Android lane
also produces Rust artifacts and they do not belong under desktop/.
Also retires the Tauri Android lane in the same push rather than leaving a path
that is being replaced: gen/android, android.yml and docs/android-dev.md are
gone, the mobile_entry_point attribute with them, and the lib drops to rlib —
staticlib/cdylib existed for Tauri mobile, and the .so Android loads will be
built from the core crate instead. Rule 22, no parallel path.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
46 lines
2.4 KiB
TOML
46 lines
2.4 KiB
TOML
[package]
|
|
name = "thoughtsync-core"
|
|
version = "0.1.0"
|
|
description = "ThoughtSync client core — local-first SQLite store and opt-in sync engine"
|
|
authors = ["bvandeusen"]
|
|
edition = "2021"
|
|
|
|
[dependencies]
|
|
serde = { workspace = true }
|
|
serde_json = { workspace = true }
|
|
log = { workspace = true }
|
|
# Local-first store (M10.4): bundled = compile SQLite in, so there's no system
|
|
# libsqlite dependency to vary across the AppImage / native / Windows / Android builds.
|
|
rusqlite = { version = "0.32", features = ["bundled"] }
|
|
uuid = { version = "1", features = ["v4"] }
|
|
# RFC3339 timestamps for created_at/updated_at/remind_at (Date.parse-able on the JS side).
|
|
chrono = { version = "0.4", default-features = false, features = ["clock"] }
|
|
# HTTP for the opt-in server handshake (M10.6) and the sync engine (M10.7).
|
|
#
|
|
# native-tls, NOT rustls, deliberately: on x86_64-pc-windows-msvc native-tls resolves
|
|
# to `schannel` — pure-Rust bindings to the OS TLS stack — so nothing C or assembly
|
|
# has to cross-compile on the Windows lane, which is the fragile one. rustls would
|
|
# instead pull in ring/aws-lc-rs and their assembler. On Linux native-tls uses
|
|
# OpenSSL, whose headers (libssl-dev) ci-tauri already ships.
|
|
# default-features off drops http2/charset we don't need for a JSON API.
|
|
reqwest = { version = "0.12", default-features = false, features = ["json", "native-tls"] }
|
|
# Verifying downloaded attachment bytes against the sha256 the server advertised.
|
|
sha2 = "0.10"
|
|
|
|
# Android has no system OpenSSL to link against, and `native-tls` resolves to
|
|
# OpenSSL there — unlike Windows, where it lands on schannel and costs nothing.
|
|
# Without this the build dies at `openssl-sys`: "Could not find directory of
|
|
# OpenSSL installation".
|
|
#
|
|
# `vendored` compiles OpenSSL from source with the NDK toolchain. The alternative
|
|
# was rustls on Android only, which builds faster — but rustls ships its own root
|
|
# store, so the phone would trust a DIFFERENT set of certificates than the desktop
|
|
# does. A self-hosted server behind a private or enterprise CA would then work on
|
|
# one surface and fail on another, and "the surfaces behave the same" is worth more
|
|
# than build minutes.
|
|
#
|
|
# Declared as a direct dependency purely to turn the feature on: cargo's feature
|
|
# unification applies it to the copy `native-tls` pulls in transitively.
|
|
[target.'cfg(target_os = "android")'.dependencies]
|
|
openssl-sys = { version = "0.9", features = ["vendored"] }
|