One possibility would be cargo build --lto as a level beyond cargo build --release. Presumably this should only work with binaries/static libraries and so be an error if applied to an rlib.
E-easy
huonw
All 2 comments
I think I may actually expect lto = true to be possible in the [profile.release] manifest section as opposed to adding a flag to this.
alexcrichton
on 27 Oct 2014
👍3
One may not want to build with LTO for every release since it takes so long, but maybe this isn't the case.
huonw
on 27 Oct 2014
Was this page helpful?
0 / 5 - 0 ratings
Related issues
ckaran
路
3Comments
skletsun
路
3Comments
tensorchen
路
3Comments
rodoufu
路
3Comments
briansmith
路
3Comments
Most helpful comment
I think I may actually expect
lto = trueto be possible in the[profile.release]manifest section as opposed to adding a flag to this.