[GH-ISSUE #361] cargo install and root workspace Cargo.toml inconsistency #195

Open
opened 2026-03-02 23:45:21 +03:00 by kerem · 0 comments
Owner

Originally created by @LucasFA on GitHub (Feb 6, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/361

Is your feature request related to a problem? Please describe.
The debug = 1 setting is not set when installing the crate with cargo install, but it does affect cargo build --release and the published binaries in the github release (built in CD).

Describe the solution you'd like
Eventually it would be nice to remove the debug information from the binary, but I gather it's been useful. Right now, it's good enough for me to have learned the why behind the discrepancy in binary sizes. I didn't think this was evident but if you knew this already, nevermind.

More context
See https://github.com/rust-lang/cargo/issues/8264 for why this happens. Also, this reddit post, with simple ways to fix this in either direction.

Originally created by @LucasFA on GitHub (Feb 6, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/361 **Is your feature request related to a problem? Please describe.** The `debug = 1` setting is not set when installing the crate with `cargo install`, but it does affect `cargo build --release` and the published binaries in the github release (built in CD). **Describe the solution you'd like** Eventually it would be nice to remove the debug information from the binary, but I gather it's been useful. Right now, it's good enough for me to have learned the why behind the discrepancy in binary sizes. I didn't think this was evident but if you knew this already, nevermind. **More context** See https://github.com/rust-lang/cargo/issues/8264 for why this happens. Also, this [reddit post](https://www.reddit.com/r/rust/comments/115ffks/cargo_install_does_not_respect_profilerelease/), with simple ways to fix this in either direction.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-player#195
No description provided.