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
By default, hakari will produce [build-dependencies] (I haven't learned why yet), but I found this will probably make a dependency compiled twice (under --release). This is because build-dependencies have different build profile configs
To compile quickly, all profiles, by default, do not optimize build dependencies
@sunshowers Are you aware of this issue? I'm wondering what's the best practice. Is it better to remove build-dependencies in workspace-hack, or set profile.release.build-override 🤔
The text was updated successfully, but these errors were encountered:
Thanks for reporting this! That's definitely an annoying issue and I wasn't aware of it.
Hakari produces build dependencies because what it cares about is dependencies built on the host platform.
I don't plan to work on this unless my employer runs into it. However if you or someone else would like to think through and put together a plan, it would be really appreciated.
By default, hakari will produce
[build-dependencies]
(I haven't learned why yet), but I found this will probably make a dependency compiled twice (under--release
). This is because build-dependencies have different build profile configshttps://doc.rust-lang.org/cargo/reference/profiles.html#build-dependencies
@sunshowers Are you aware of this issue? I'm wondering what's the best practice. Is it better to remove
build-dependencies
inworkspace-hack
, or setprofile.release.build-override
🤔The text was updated successfully, but these errors were encountered: