saymrwulf/xous-core
1
0
Fork 0
mirror of https://github.com/saymrwulf/xous-core.git synced 2026-11-14 08:03:34 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
xous-core/services/ime-plugin-api/Cargo.toml

19 lines
665 B
TOML
Raw Normal View History

refactor API into a separate crate with traits
2021-03-03 20:33:20 +00:00
[package]
authors = ["bunnie <bunnie@kosagi.com>"]
description = "IME Plugin Common APIs"
ipc: convert project to use `xous-ipc` This rewrites the entire project so that most runnable projects now use `xous-ipc` instead of `xous::String` where possible. This also removes `rkyv` from the list of dependencies in `xous-rs`. Signed-off-by: Sean Cross <sean@xobs.io>
2021-03-26 12:22:33 +00:00
edition = "2018"
name = "ime-plugin-api"
version = "0.1.0"
refactor API into a separate crate with traits
2021-03-03 20:33:20 +00:00
fix #174
2022-06-10 13:36:53 +00:00
# Dependency versions enforced by Cargo.lock.
refactor API into a separate crate with traits
2021-03-03 20:33:20 +00:00
[dependencies]
ipc: convert project to use `xous-ipc` This rewrites the entire project so that most runnable projects now use `xous-ipc` instead of `xous::String` where possible. This also removes `rkyv` from the list of dependencies in `xous-rs`. Signed-off-by: Sean Cross <sean@xobs.io>
2021-03-26 12:22:33 +00:00
graphics-server = {path = "../graphics-server"}# this is used by the IMEF portion of the API
pin down versions and harmonize versions across servers Versions are pinned down to the minor number. Yes, this means that we don't automatically pull in features and bug updates from crates.io, but it also means we don't pull in new attack surfaces and code that hasn't been tested or reviewed. I'd like this process to be very deliberate and not automatic for Xous. The `rand` crate is almost pinned down to a single version, except for an odd dependency that's pulled in by hosted mode that depends on rand 0.8.4 via a subordinate dependency via the `tempfile` crate. Pondering if it's worth it to try and eliminate that, because the 0.8.4 version doesn't get compiled into any version that touches real hardware. It just makes it harder to analyze the Cargo.lock file, mostly. I think I'll leave it as-is.
2022-01-10 07:39:55 +00:00
log = "0.4.14"
bump xous version
2023-01-17 16:02:46 +00:00
xous = "0.9.31"
xous-ipc = "0.9.31"
xous-names = {package = "xous-api-names", version = "0.9.28"}# used by the IMEF for registering listeners
refactor API into a separate crate with traits
2021-03-03 20:33:20 +00:00
pin down versions and harmonize versions across servers Versions are pinned down to the minor number. Yes, this means that we don't automatically pull in features and bug updates from crates.io, but it also means we don't pull in new attack surfaces and code that hasn't been tested or reviewed. I'd like this process to be very deliberate and not automatic for Xous. The `rand` crate is almost pinned down to a single version, except for an odd dependency that's pulled in by hosted mode that depends on rand 0.8.4 via a subordinate dependency via the `tempfile` crate. Pondering if it's worth it to try and eliminate that, because the 0.8.4 version doesn't get compiled into any version that touches real hardware. It just makes it harder to analyze the Cargo.lock file, mostly. I think I'll leave it as-is.
2022-01-10 07:39:55 +00:00
num-derive = {version = "0.3.3", default-features = false}
num-traits = {version = "0.2.14", default-features = false}
refactor of the imef interface part 1
2021-04-04 16:30:46 +00:00
rkyv = {version = "0.4.3", default-features = false, features = ["const_generics"]}
Reference in a new issue Copy permalink