<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build on Siddharth Mishra</title><link>http://brightprogrammer.in/tags/build/</link><description>Recent content in Build on Siddharth Mishra</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 14 Jun 2026 21:53:10 -0700</lastBuildDate><atom:link href="http://brightprogrammer.in/tags/build/index.xml" rel="self" type="application/rss+xml"/><item><title>A Build System For C in C</title><link>http://brightprogrammer.in/posts/a-build-system-in-c-for-c/</link><pubDate>Wed, 29 Jan 2025 00:00:00 +0000</pubDate><guid>http://brightprogrammer.in/posts/a-build-system-in-c-for-c/</guid><description>&lt;p>I recently started a new project where I had to decide (again) how to build this project. This decision is faced
by any developer who use a language that does not have a standard way of building things. In my case, my project
is to be written in C, my go-to language, and as we all know, it does not have any standard other than the standard
spec. I usually go with CMake, as my go-to build system, because I&amp;rsquo;ve seen many projects use it. It&amp;rsquo;s almost like
the &amp;ldquo;industry&amp;rdquo; standard. It&amp;rsquo;s very old, and regularly updated, to keep itself up to date with available libraries,
frameworks, compiler features etc&amp;hellip; and it might be good for very big projects, but I decided that I&amp;rsquo;ll try something
simpler this time.&lt;/p></description></item></channel></rss>