<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gaming on diary</title>
		<link>/tags/gaming/</link>
		<description>Recent content in Gaming on diary</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>shawn boyette</copyright>
		
		
			<lastBuildDate>Thu, 16 Jul 2026 00:11:19 -0600</lastBuildDate>
		
			<atom:link href="/tags/gaming/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Project updates and SteamOS exploration</title>
				<link>/posts/2026/0716-project-updates-and-steamos-exploration/</link>
				<pubDate>Thu, 16 Jul 2026 00:11:19 -0600</pubDate>
				<guid>/posts/2026/0716-project-updates-and-steamos-exploration/</guid>
				<description>&lt;p&gt;Firstly, everything mentioned in the previous post is done. I&amp;rsquo;m&#xA;especially happy with the solution I came up with for build-level&#xA;config in &lt;code&gt;fpc-ctl&lt;/code&gt;:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Config within the per-project shell script is removed, excepting a&#xA;pointer to the project&amp;rsquo;s JSON config file&lt;/li&gt;&#xA;&lt;li&gt;Everything that was in the script is moved to a &lt;code&gt;builds&lt;/code&gt; object in&#xA;the config&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;configmap&lt;/code&gt;, which maps project configuration attributes to&#xA;build variables, has been extended&#xA;&lt;ul&gt;&#xA;&lt;li&gt;When a &lt;code&gt;configmap&lt;/code&gt; value contains &lt;code&gt;::&lt;/code&gt;, the right-hand side of the&#xA;value is treated as an override to the value given at the project&#xA;level&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This has made it possible to cleanly have multiple builds (or even&#xA;subprojects) defined with a single config file, all managed by&#xA;&lt;code&gt;fpc-ctl&lt;/code&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
