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
It appears calling cargo build with a custom target directory is generating a lot of garbage. Either collect the garbage or use the default directory and parse the location from cargo.
The text was updated successfully, but these errors were encountered:
If the goal of #578 was to make it easier to determine the location of the artifacts, and make sure they are up-to-date, I think it could be achieved without having to rebuild everything and using a separate temp folder. For instance, it may rebuild things in-place (if necessary), and then have some logic to figure out the current target directory. Would this help?
It appears calling
cargo build
with a custom target directory is generating a lot of garbage. Either collect the garbage or use the default directory and parse the location from cargo.The text was updated successfully, but these errors were encountered: