# Devlog ⚡ Build System Reworked

**URL:** <https://ziggit.dev/t/devlog-build-system-reworked/15742>\
**Category:** Media\
**Tags:** build-system, devlog\
**Created:** [May 27, 2026, 6:06am UTC](https://ziggit.dev/t/devlog-build-system-reworked/15742 "2026-05-27T06:06:44Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![andrewrk](https://ziggit.dev/user_avatar/ziggit.dev/andrewrk/32/7011_2.png) [@andrewrk](https://ziggit.dev/u/andrewrk)\
**Post date:** [May 27, 2026, 6:54pm UTC](https://ziggit.dev/t/devlog-build-system-reworked/15742/9 "2026-05-27T18:54:20Z")

</div>

If you’re writing tooling you definitely want the binary format. You don’t have to parse it, you just load it into memory and it’s ready to go. `std.Build.Configuration` API has everything you need.

That’s a great point about getting the path to that file though. That should definitely be a `zig build` flag. Tracking issue:

[https://codeberg.org/ziglang/zig/issues/35498](https://codeberg.org/ziglang/zig/issues/35498)

---

_[View the full topic](https://ziggit.dev/t/devlog-build-system-reworked/15742)._