#214 detect and warn (or fix automatically) if upstream sets incompatible compiler flags
Opened 3 months ago by decathorpe. Modified 3 months ago

I found that some crates set their own compiler settings in Cargo.toml, like this:

[profile.release]
lto = true
codegen-units = 1
debug = 0
strip = true

(from zoxide 0.8.2)

Especially the debug = 0 and strip = true settings are problematic for our builds. Packages will build successfully, but fail during debuginfo package generation with very cryptic error messages.

It would be great if we could detect this setting if crates set it, and either print a warning, or strip those incompatible settings automatically.


Login to comment on this ticket.

Metadata