<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Writing on Ignacio LD — AI &amp; Mobile Engineering</title>
		<link>https://ignacio.tech/blog/</link>
		<description>Recent content in Writing on Ignacio LD — AI &amp; Mobile Engineering</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://ignacio.tech/blog/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Building Android apps on Asahi Linux</title>
				<link>https://ignacio.tech/blog/building-android-apps-on-asahi-linux/</link>
				<pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://ignacio.tech/blog/building-android-apps-on-asahi-linux/</guid>
				<description>&lt;p&gt;Asahi Linux runs beautifully on Apple Silicon until you try to build an Android app. The Java, the Gradle daemon, the Kotlin compiler, all of that works. Then the build fails on a single binary called &lt;code&gt;aapt2&lt;/code&gt; with an error that looks like the file is corrupt, when really it&amp;rsquo;s just the wrong architecture.&lt;/p&gt;&#xA;&lt;p&gt;This is the setup I use to develop Android apps on an M-series Mac running Asahi Linux. It wraps Google&amp;rsquo;s x86-64 &lt;code&gt;aapt2&lt;/code&gt; with QEMU user-mode emulation, and swaps the SDK&amp;rsquo;s &lt;code&gt;adb&lt;/code&gt; for a native ARM64 build. By the end you can run &lt;code&gt;./gradlew assembleDebug&lt;/code&gt; and &lt;code&gt;adb install&lt;/code&gt; like on any other machine.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
