-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Possibility to disable caching for user code #12317
Copy link
Copy link
Closed
Labels
acceptedThis proposal is planned.This proposal is planned.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.proposalThis issue suggests modifications. If it also has the "accepted" label then it is planned.This issue suggests modifications. If it also has the "accepted" label then it is planned.zig ccZig as a drop-in C compiler featureZig as a drop-in C compiler feature
Milestone
Description
Zig Version
0.10.0-dev.2783+76546b3f8
Steps to Reproduce
Build a very large binary with zig cc as the C toolchain. In our case, the binary is 584M.
Expected Behavior
Currently it is expected that the Zig cache may grow very large. However, when using an external build system to orchestrate the build and cache the results (in our case Bazel), we have no need for the Zig cache outside "internal" builds (libc stubs etc.). It would be great to have a flag to only cache these internal builds, and not user code.
Actual Behavior
With our 584M binary, the Zig cache is 761M after building from a clean cache.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
acceptedThis proposal is planned.This proposal is planned.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.proposalThis issue suggests modifications. If it also has the "accepted" label then it is planned.This issue suggests modifications. If it also has the "accepted" label then it is planned.zig ccZig as a drop-in C compiler featureZig as a drop-in C compiler feature