# One repo, one crate per shared object.
#
# Every crate here builds a `.so` that a jolt library binds through
# `jolt.ffi/defcfn`, plus `jolt-abi`, which is the rules they all keep at the
# edge rather than a library anyone loads.
#
# Deliberately NOT one cdylib with cargo features selecting the parts. Features
# are additive within a library, so `graphics` + `moq` would mean one object
# carrying egui *and* QUIC, Opus, H.264 and the camera stacks — a chat client
# that is not in a call would link the whole media plane to open a window. The
# feature unification that comes with it has bitten this code before: enabling
# eframe's wayland/x11 features for the desktop build pulled them into the
# Android one and made the activity exit on launch.
#
# A workspace gives the parts of a monorepo worth having — one CI, one release,
# shared conventions in `jolt-abi` — while each consumer still links only what
# it asked for. jolt's `:jolt/native` is a vector; naming two objects there is
# no harder than naming one.
[workspace]
resolver = "2"
members = [
    "crates/jolt-abi",
    "crates/jolt-moq",
    "crates/jolt-tui",
    "crates/jolt-vidya",
    "crates/vidya-core",
]

[workspace.package]
version = "0.1.0"
edition = "2021"
license = "MIT"
repository = "https://gitlab.com/nandithebull/jolt-native"

# vidya-ffi set opt-level 2 when it was its own workspace: the tree walk and
# the texture uploads are hot every frame, and a debug build of them is not
# worth looking at. A member cannot set this, so it is set here.
[profile.release]
opt-level = 2
# 1.5M off the desktop object; opt-level 3 was measured alongside and is larger,
# so it stays at 2.
lto = "fat"
codegen-units = 1

[workspace.dependencies]
jolt-abi = { path = "crates/jolt-abi" }
log = "0.4"