<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rust on rmqa.com</title>
    <link>https://rmqa.com/tags/rust/</link>
    <description>Recent content in Rust on rmqa.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rmqa.com/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Checking Rust Style Release Targets and a Missing Intel Mac Build With rmqa</title>
      <link>https://rmqa.com/checking-rust-style-release-targets-and-a-missing-intel-mac-build-with-rmqa/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/checking-rust-style-release-targets-and-a-missing-intel-mac-build-with-rmqa/</guid>
      <description>&lt;p&gt;Rust projects usually name their release files after target triples: &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt;, &lt;code&gt;aarch64-apple-darwin&lt;/code&gt;, &lt;code&gt;x86_64-pc-windows-msvc&lt;/code&gt;. Each archive also wraps its contents in a folder with the same name, so unpacking &lt;code&gt;tidy-2.3.0-aarch64-apple-darwin.tar.gz&lt;/code&gt; gives a folder &lt;code&gt;tidy-2.3.0-aarch64-apple-darwin/&lt;/code&gt; with the program inside. Many projects ship two license files, MIT and Apache.&lt;/p&gt;&#xA;&lt;p&gt;None of that fits a simple &lt;code&gt;{os}_{arch}&lt;/code&gt; pattern, and rmqa doesn&amp;rsquo;t need it to. Any string you add to a &lt;code&gt;[[platform]]&lt;/code&gt; becomes a template variable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
