<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Open Source on Fran Kuo | R&amp;D Leadership</title>
    <link>https://chenfu.ai/en/tags/open-source/</link>
    <description>Recent content in Open Source on Fran Kuo | R&amp;D Leadership</description>
    <generator>Hugo -- 0.157.0</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Sep 2007 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://chenfu.ai/en/tags/open-source/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reflections on Patch Files and Embedded Systems Development</title>
      <link>https://chenfu.ai/en/posts/patch-vs-embedded-system-development/</link>
      <pubDate>Wed, 19 Sep 2007 00:00:00 +0000</pubDate>
      <guid>https://chenfu.ai/en/posts/patch-vs-embedded-system-development/</guid>
      <description>&lt;p&gt;Recently, I was assigned to work on a streaming server project. On our development platform, we utilize a combination of patch files and shell scripts to manage source code. We start with the upstream source, apply modifications via &lt;code&gt;patch&lt;/code&gt; commands, and then compile the results into the necessary shared libraries or executables. Initially, I didn&amp;rsquo;t give much thought to why we adopted this specific workflow, but lately, I&amp;rsquo;ve begun to appreciate the profound advantages of this approach.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
