<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>a sleepy crow&#39;s nest</title>
    <link>https://publish.ministryofinternet.eu/sleepycrow/</link>
    <description>angry bird caws at the internet</description>
    <pubDate>Sat, 19 Sep 2026 16:28:23 +0200</pubDate>
    <item>
      <title>(Actually) Building Aseprite from Source on Fedora</title>
      <link>https://publish.ministryofinternet.eu/sleepycrow/actually-building-aseprite-from-source</link>
      <description>&lt;![CDATA[Aseprite is by far the best pixel art tool I&#39;ve ever had the pleasure of using. I&#39;ve been happily using it for quite a few years without any issue. That&#39;s until I decided to move to fedora.&#xA;&#xA;You see, while Aseprite&#39;s creator - David Capello - does theoretically provide linux builds of Aseprite (at some added cost), he - annoyingly enough - only builds .deb packages.&#xA;&#xA;Luckily, thanks to Aseprite&#39;s unique business model - that being open source, but with paid builds - it&#39;s somewhat easy to compile Aseprite from source code by yourself.&#xA;&#xA;Step 1: Install dependencies&#xA;&#xA;This one-liner is the same as in the official install instructions, with one small change - I&#39;ve added python2, which is required by some of the scripts you&#39;ll be running in the next step.&#xA;&#xA;sudo dnf install -y gcc-c++ cmake ninja-build libX11-devel libXcursor-devel libXi-devel mesa-libGL-devel fontconfig-devel python2&#xA;&#xA;Step 2: Build Skia&#xA;&#xA;Skia is a 2D graphic library developed by Google Inc., and pretty much the only dependency of Aseprite that you&#39;ll have to compile yourself. Sadly, the build process is somewhat tricky, as it depends on the deprecated python2, and does require some super-secret tricks you might now know about!&#xA;&#xA;First off, you&#39;ll need to make a deps/ directory in your home folder, then clone google&#39;s build tools repo and the aseprite-m81 branch of the aseprite fork of skia into it, like so:&#xA;&#xA;mkdir $HOME/deps&#xA;cd $HOME/deps&#xA;git clone https://chromium.googlesource.com/chromium/tools/depottools.git&#xA;git clone -b aseprite-m81 https://github.com/aseprite/skia.git&#xA;&#xA;...then add the depottools repo to your PATH environment variable, and cd into the skia repo:&#xA;&#xA;export PATH=&#34;${PWD}/depottools:${PATH}&#34;&#xA;cd skia&#xA;&#xA;Now&#39;s the tricky part that you won&#39;t find in dacap&#39;s documentation! In the skia/ folder you&#39;d just cd&#39;d into, you&#39;ll find a file called .gn. Open it up in a text editor, then add the following line at the end:&#xA;&#xA;scriptexecutable = &#34;python2&#34;&#xA;&#xA;Having done that, you may now run the following commands to download dependencies, prepare build files for ninja, then (finally) build the library with ninja.&#xA;&#xA;python tools/git-sync-deps&#xA;gn gen out/Release-x64 --args=&#34;isdebug=false isofficialbuild=true skiausesystemexpat=false skiausesystemicu=false skiausesystemlibjpegturbo=false skiausesystemlibpng=false skiausesystemlibwebp=false skiausesystemzlib=false&#34;&#xA;ninja -C out/Release-x64 skia modules&#xA;&#xA;Step 3: Build Aseprite&#xA;&#xA;Finally, having built Skia, you can now build Aseprite itself. Download the Aseprite-v1.x-Source.zip file from the latest Aseprite release and extract it somewhere, then, cd into that folder, and run the following bundle of commands:&#xA;&#xA;mkdir build&#xA;cd build&#xA;cmake \&#xA;  -DCMAKEBUILDTYPE=RelWithDebInfo \&#xA;  -DLAFBACKEND=skia \&#xA;  -DSKIADIR=$HOME/deps/skia \&#xA;  -DSKIALIBRARYDIR=$HOME/deps/skia/out/Release-x64 \&#xA;  -DSKIA_LIBRARY=$HOME/deps/skia/out/Release-x64/libskia.a \&#xA;  -G Ninja \&#xA;  ..&#xA;ninja aseprite&#xA;&#xA;This bundle is exactly the same as in the official INSTALL.md build instructions, and - just as in the original - $HOME/deps/skia is the directory where you&#39;d built Skia earlier.&#xA;&#xA;...and you&#39;re done!&#xA;&#xA;Yep, that&#39;s it. Provided none of the commands errored out - you should now have a built, working version of aseprite in the build/bin/ folder. :)&#xA;&#xA;If you enjoy Aseprite, make sure to support it&#39;s creator by buying it!]]&gt;</description>
      <content:encoded><![CDATA[<p><a href="https://aseprite.org" rel="nofollow">Aseprite</a> is by far the best pixel art tool I&#39;ve ever had the pleasure of using. I&#39;ve been happily using it for quite a few years without any issue. That&#39;s until I decided to move to fedora.</p>

<p>You see, while Aseprite&#39;s creator – <a href="https://github.com/dacap" rel="nofollow">David Capello</a> – <em>does</em> theoretically provide linux builds of Aseprite (<a href="https://aseprite.org/#buy" rel="nofollow">at some added cost</a>), he – annoyingly enough – only builds .deb packages.</p>

<p>Luckily, thanks to Aseprite&#39;s unique business model – that being open source, but with paid builds – it&#39;s somewhat easy to compile Aseprite from source code by yourself.</p>

<h2 id="step-1-install-dependencies">Step 1: Install dependencies</h2>

<p>This one-liner is the same as in the <a href="https://github.com/aseprite/aseprite/blob/main/INSTALL.md" rel="nofollow">official install instructions</a>, with one small change – I&#39;ve added python2, which is required by some of the scripts you&#39;ll be running in the next step.</p>

<pre><code>sudo dnf install -y gcc-c++ cmake ninja-build libX11-devel libXcursor-devel libXi-devel mesa-libGL-devel fontconfig-devel python2
</code></pre>

<h2 id="step-2-build-skia">Step 2: Build Skia</h2>

<p>Skia is a 2D graphic library developed by Google Inc., and pretty much the only dependency of Aseprite that you&#39;ll have to compile yourself. Sadly, the build process is somewhat tricky, as it depends on the deprecated python2, and does require some super-secret tricks you might now know about!</p>

<p>First off, you&#39;ll need to make a <code>deps/</code> directory in your home folder, then clone google&#39;s build tools repo and the aseprite-m81 branch of the aseprite fork of skia into it, like so:</p>

<pre><code>mkdir $HOME/deps
cd $HOME/deps
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
git clone -b aseprite-m81 https://github.com/aseprite/skia.git
</code></pre>

<p>...then add the <code>depot_tools</code> repo to your <code>PATH</code> environment variable, and <code>cd</code> into the skia repo:</p>

<pre><code>export PATH=&#34;${PWD}/depot_tools:${PATH}&#34;
cd skia
</code></pre>

<p>Now&#39;s the tricky part that you won&#39;t find in <a href="https://github.com/dacap" rel="nofollow">dacap</a>&#39;s documentation! In the <code>skia/</code> folder you&#39;d just cd&#39;d into, you&#39;ll find a file called <code>.gn</code>. Open it up in a text editor, then add the following line at the end:</p>

<pre><code>script_executable = &#34;python2&#34;
</code></pre>

<p>Having done that, you may now run the following commands to download dependencies, prepare build files for ninja, then (finally) build the library with ninja.</p>

<pre><code>python tools/git-sync-deps
gn gen out/Release-x64 --args=&#34;is_debug=false is_official_build=true skia_use_system_expat=false skia_use_system_icu=false skia_use_system_libjpeg_turbo=false skia_use_system_libpng=false skia_use_system_libwebp=false skia_use_system_zlib=false&#34;
ninja -C out/Release-x64 skia modules
</code></pre>

<h2 id="step-3-build-aseprite">Step 3: Build Aseprite</h2>

<p>Finally, having built Skia, you can now build Aseprite itself. Download the <code>Aseprite-v1.x-Source.zip</code> file from the <a href="https://github.com/aseprite/aseprite/releases/latest" rel="nofollow">latest Aseprite release</a> and extract it somewhere, then, <code>cd</code> into that folder, and run the following bundle of commands:</p>

<pre><code>mkdir build
cd build
cmake \
  -DCMAKE_BUILD_TYPE=RelWithDebInfo \
  -DLAF_BACKEND=skia \
  -DSKIA_DIR=$HOME/deps/skia \
  -DSKIA_LIBRARY_DIR=$HOME/deps/skia/out/Release-x64 \
  -DSKIA_LIBRARY=$HOME/deps/skia/out/Release-x64/libskia.a \
  -G Ninja \
  ..
ninja aseprite
</code></pre>

<p>This bundle is exactly the same as in the <a href="https://github.com/aseprite/aseprite/blob/main/INSTALL.md#linux-details" rel="nofollow">official INSTALL.md build instructions</a>, and – just as in the original – $HOME/deps/skia is the directory where you&#39;d built Skia earlier.</p>

<h2 id="and-you-re-done">...and you&#39;re done!</h2>

<p>Yep, that&#39;s it. Provided none of the commands errored out – you should now have a built, working version of aseprite in the <code>build/bin/</code> folder. :)</p>

<p>If you enjoy Aseprite, make sure to support it&#39;s creator by <a href="https://aseprite.org/#buy" rel="nofollow">buying it</a>!</p>
]]></content:encoded>
      <guid>https://publish.ministryofinternet.eu/sleepycrow/actually-building-aseprite-from-source</guid>
      <pubDate>Thu, 24 Jun 2021 18:12:30 +0200</pubDate>
    </item>
  </channel>
</rss>