[profile.release] debug = true forced full DWARF into release builds. On ELF targets (the manylinux/musllinux wheels) the debug sections are embedded in the .so (~160 MB, over PyPI's 100 MB file limit); MSVC emits a sidecar .pdb instead and the apple/zig link path drops it, so only the Linux wheels were bloated. Move debug=true to [profile.test] so cargo still gets readable backtraces without fattening the release wheels.
39 lines
1.3 KiB
TOML
39 lines
1.3 KiB
TOML
[workspace]
|
|
resolver = "3"
|
|
members = ["ndbioimage", "image-tiff", "image-registration"]
|
|
|
|
[workspace.package]
|
|
version = "0.3.1"
|
|
edition = "2024"
|
|
rust-version = "1.94.1"
|
|
authors = ["Wim Pomp <w.pomp@nki.nl>"]
|
|
license = "MIT OR Apache-2.0"
|
|
description = "Read bio image formats using the bio-formats java package."
|
|
repository = "https://git.pomppervova.nl/wim/ndbioimage"
|
|
documentation = "https://docs.rs/ndbioimage"
|
|
readme = "README.md"
|
|
keywords = ["bioformats", "imread", "ndarray", "metadata"]
|
|
categories = ["multimedia::images", "science"]
|
|
|
|
[profile.test]
|
|
inherits = "release"
|
|
# Full debug info goes in the TEST profile only (readable cargo-test
|
|
# backtraces). It must NOT be in the release profile: on ELF targets
|
|
# (Linux/musl wheels) the DWARF gets embedded in the .so (~160 MB, over
|
|
# PyPI's 100 MB limit) - MSVC puts it in a sidecar .pdb and the
|
|
# apple/zig link path drops it, which is why only the Linux wheels were
|
|
# bloated.
|
|
debug = true
|
|
|
|
[profile.release]
|
|
|
|
[profile.dev.package.backtrace]
|
|
opt-level = 3
|
|
|
|
# Build against the libczirw-sys checkout in the submodule of that name:
|
|
# its fixes (self-contained cmake build via vendored Eigen, msvc C runtime
|
|
# alignment for xwin, bindgen flags for zig's libc++) are not yet published
|
|
# to crates.io; drop this patch once a release containing them is available
|
|
[patch.crates-io]
|
|
libczirw-sys = { path = "libczirw-sys" }
|