You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The serde_with crate uses chrono, which pulls in a number of android specific dependencies (which you can see in your top level Cargo.lock). Chrono does not need to pull these in if you arent using the Clock feature. It did not look like you were using offset::local so I think you can turn it off and ship without those dependencies. Doing so would lead to a smaller and faster to build library, which I would really appreciate. It was entertaining to find android centric dependencies in a CLI application I am developing.
I would love to have a way to not use the clock feature and instead just "detect" that it is enabled somewhere else in the dependency tree. Something like #[cfg(accessible(...))], but that isn't anywhere near stabilization rust-lang/rust#64797.
The timezone dependency is gated by [target.'cfg(target_os = "android")'.dependencies] so it will only be built if you target Android. Otherwise, it is just an entry in the lock file. Further, there is a cargo bug where it includes dependencies in the lockfile, even though they are disabled rust-lang/cargo#10801. However, they are never compiled.
The serde_with crate uses chrono, which pulls in a number of android specific dependencies (which you can see in your top level Cargo.lock). Chrono does not need to pull these in if you arent using the Clock feature. It did not look like you were using
offset::local
so I think you can turn it off and ship without those dependencies. Doing so would lead to a smaller and faster to build library, which I would really appreciate. It was entertaining to find android centric dependencies in a CLI application I am developing.For more information: chronotope/chrono#1220
The text was updated successfully, but these errors were encountered: