mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
a5c9ac2e95
The Cargo.lock of rust_riotmodules_standalone should explicitly list all versions of software that would ever be pulled in by enabling RIOT modules backed by a Rust crate. That way, the Cargo.lock file will not spontaneously change because the software is being built with a different set of modules enabled. This did not happen before, because while the optional dependencies could all be selected on the command line, they were not visible as possible features to `cargo update`, and were thus not encoded in the Cargo.lock file.
30 lines
794 B
TOML
30 lines
794 B
TOML
[package]
|
|
name = "rust_riotmodules_standalone"
|
|
version = "0.1.0"
|
|
authors = ["Christian Amsüss <chrysn@fsfe.org>"]
|
|
edition = "2021"
|
|
publish = false
|
|
|
|
[lib]
|
|
crate-type = [ "staticlib" ]
|
|
|
|
[profile.release]
|
|
lto = true
|
|
opt-level = "s"
|
|
debug = true
|
|
panic = "abort"
|
|
codegen-units = 1
|
|
|
|
[dependencies]
|
|
riot-wrappers = { version = "0.8", features = [ "set_panic_handler" ] }
|
|
|
|
rust_riotmodules = { path = "../rust_riotmodules" }
|
|
|
|
[features]
|
|
# By having this explicit feature (comapred to what is enabled by the build
|
|
# system as `--features rust_riotmodules/foo`), all possible dependencies are
|
|
# visible to `cargo update` and in `Cargo.lock. This should not be enabled for
|
|
# compilation, as the modules behind it likely have their own RIOT modules they
|
|
# need enabled.
|
|
_all = [ "rust_riotmodules/_all" ]
|