I got tired of typing nasm/ld/gcc by hand, so I built a tool that does it for me
Alex Voste created a command-line tool called fz (ForgeZero) to simplify the process of compiling assembly and C code. The tool eliminates the need for remembering various compiler flags and allows users to build projects with a single command. It also features incremental builds, strict mode for C, and JSON output for CI/CD pipelines.
- ▪fz is a CLI tool that automates the compilation of assembly and C code without the need for complex configurations.
- ▪It supports incremental builds and can watch for file changes to rebuild automatically.
- ▪The tool enforces quality by compiling C files with strict warnings and includes options for sanitizers.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/alexvoste/i-got-tired-of-typing-nasmldgcc-by-hand-so-i-built-a-tool-that-does-it-for-me-5bkf |
| Publication time | Sun, 17 May 2026 16:11:51 +0000 |
| Retrieval time | 2026-05-17T16:33:20.825Z |
| Last seen | 2026-05-17T16:33:20.825Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | DU_sXj8tm2qn |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3933967) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Alex Voste Posted on May 17 I got tired of typing nasm/ld/gcc by hand, so I built a tool that does it for me #assembly #c #devtools #go If you've ever written assembly or C without CMake, Makefiles, or any build system — you know the ritual. Open terminal. Remember the flags. Compile one file. Then another. Then link them. Then mess up the argument order. Then do it again. And again. Every. Single. Time. I did this long enough to finally say: enough.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
