#cargo-build #artifact #garbage #outdated #collect #gc

build cargo-gc-bin

Garbage collect outdated cargo build artifacts

5 releases

0.1.4 May 7, 2024
0.1.3 Nov 15, 2023
0.1.2 Oct 9, 2023
0.1.1 Aug 24, 2023
0.1.0 Aug 24, 2023

#93 in Build Utils

Download history 2793/week @ 2024-08-06 3042/week @ 2024-08-13 2996/week @ 2024-08-20 3193/week @ 2024-08-27 3459/week @ 2024-09-03 2038/week @ 2024-09-10 2722/week @ 2024-09-17 2530/week @ 2024-09-24 707/week @ 2024-10-01 2669/week @ 2024-10-08 2198/week @ 2024-10-15 2576/week @ 2024-10-22 4507/week @ 2024-10-29 2758/week @ 2024-11-05 3514/week @ 2024-11-12 2606/week @ 2024-11-19

13,623 downloads per month

Apache-2.0

13KB
214 lines

cargo gc

Crates.io License

Cargo extension to recycle outdated build artifacts. And try the best to avoid recompilation.

Usage

Install it with cargo:

cargo install cargo-gc-bin

The executable is cargo-gc. You can invoke it with cargo gc command:

cargo gc

It will check and remove all outdated build artifacts in the current project. See cargo gc --help for more information.

Limitations / Known issues

  • It needs to invoke cargo build that takes lots of time.
  • Need to re-link after GC
  • cargo check will re-check from scratch

Explaination

cargo gc uses the output information from cargo build to help recognize build artifacts in use, and removes all others. In the current implementation, top-level arficats are not recognized and leads to re-link after GC.

Compare to other utils like cargo sweep, this one is based on the informations provided by cargo itself rather than filesystem timestamp. So it can be more accurate and still avoiding recompilation as much as possible.

Next steps

Technically, it's possible to implement a "perfect" GC that can remove all outdated artifacts without any recompilation. And done this in a totally static way (i.e., without invoking cargo build). As the tuple ("crate name", "fingreprint") can be computed outside of cargo.

Dependencies

~5–13MB
~149K SLoC