<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>book/src/building-from-source.md - fork/helix @ master</title>
<meta name="description" content="book/src/building-from-source.md in fork/helix at master.">
<meta property="og:title" content="book/src/building-from-source.md - fork/helix @ master">
<meta property="og:description" content="book/src/building-from-source.md in fork/helix at master.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="master" data-tip="10f07d7eb089430930e6d3547a98b440b927d025">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/helix</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/helix</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">Georgios Tsoulis</span><span class="commit-message" data-commit="4f5eaa41866eaeec6aeec8f2fb80797e1132e339">docs: fix possible error when building the optimized version from source (#14330)</span><span class="snapshot-sha sha" data-commit="4f5eaa41866eaeec6aeec8f2fb80797e1132e339">4f5eaa41</span><time datetime="2025-08-30T19:25:53+02:00" title="2025-08-30 19:25:53 +0200">2025-08-30</time></p>
<header class="topbar"><details class="switcher"><summary>master</summary><div class="menu"><strong>branches</strong><a class="current" href="/fork/helix/ref/master/">master</a><strong>tags</strong><a href="/fork/helix/ref/23.05/">23.05</a><a href="/fork/helix/ref/23.10/">23.10</a><a href="/fork/helix/ref/24.03/">24.03</a><a href="/fork/helix/ref/24.07/">24.07</a><a href="/fork/helix/ref/25.01/">25.01</a><a href="/fork/helix/ref/25.01.1/">25.01.1</a><a href="/fork/helix/ref/25.07/">25.07</a><a href="/fork/helix/ref/25.07.1/">25.07.1</a><a class="all" href="/fork/helix/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/helix/">helix</a> / <a href="/fork/helix/ref/master/tree/book/">book</a> / <a href="/fork/helix/ref/master/tree/book/src/">src</a> / <span class="cur">building-from-source.md</span></nav>
<span class="view-stats"><span>7.4 KiB</span><span>208 lines</span></span><span class="actions"><a class="raw" href="/fork/helix/raw/3303809861f8fddcd85ec6cdee9addf782e97150/book/src/building-from-source.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><h2>Building from source</h2>
<ul>
<li><a href="#configuring-helixs-runtime-files">Configuring Helix's runtime files</a>
<ul>
<li><a href="#linux-and-macos">Linux and macOS</a></li>
<li><a href="#windows">Windows</a></li>
<li><a href="#multiple-runtime-directories">Multiple runtime directories</a></li>
<li><a href="#note-to-packagers">Note to packagers</a></li>
</ul>
</li>
<li><a href="#validating-the-installation">Validating the installation</a></li>
<li><a href="#configure-the-desktop-shortcut">Configure the desktop shortcut</a></li>
<li><a href="#building-the-debian-package">Building the Debian package</a></li>
</ul>
<p>Requirements:</p>
<p>Clone the Helix GitHub repository into a directory of your choice. The
examples in this documentation assume installation into either <code>~/src/</code> on
Linux and macOS, or <code>%userprofile%\src\</code> on Windows.</p>
<ul>
<li>The <a href="https://www.rust-lang.org/tools/install">Rust toolchain</a></li>
<li>The <a href="https://git-scm.com/">Git version control system</a></li>
<li>A C++14 compatible compiler to build the tree-sitter grammars, for example GCC or Clang</li>
</ul>
<p>If you are using the <code>musl-libc</code> standard library instead of <code>glibc</code> the following environment variable must be set during the build to ensure tree-sitter grammars can be loaded correctly:</p>
<pre class="language-bash"><a-pr>RUSTFLAGS</a-pr>=<a-s>&quot;-C target-feature=-crt-static&quot;</a-s></pre>
<ol>
<li>
<p>Clone the repository:</p>
<pre class="language-bash"><a-f>git</a-f> clone https://github.com/helix-editor/helix
<a-f>cd</a-f> helix</pre>
</li>
<li>
<p>Compile from source:</p>
<pre class="language-bash"><a-c># Reproducible</a-c>
<a-f>cargo</a-f> install <a-co>--path</a-co> helix-term <a-co>--locked</a-co></pre>
<pre class="language-bash"><a-c># Optimized</a-c>
<a-f>cargo</a-f> install \
   <a-co>--profile</a-co> opt \
   <a-co>--config</a-co> <a-s>&#39;build.rustflags=[&quot;-C&quot;, &quot;target-cpu=native&quot;]&#39;</a-s> \
   <a-co>--path</a-co> helix-term \
   <a-co>--locked</a-co></pre>
<p>Either command will create the <code>hx</code> executable and construct the tree-sitter
grammars in the local <code>runtime</code> folder.</p>
</li>
</ol>
<blockquote>
<p>💡 If you do not want to fetch or build grammars, set an environment variable <code>HELIX_DISABLE_AUTO_GRAMMAR_BUILD</code></p>
</blockquote>
<blockquote>
<p>💡 Tree-sitter grammars can be fetched and compiled if not pre-packaged. Fetch
grammars with <code>hx --grammar fetch</code> and compile them with
<code>hx --grammar build</code>. This will install them in
the <code>runtime</code> directory within the user's helix config directory (more
<a href="#multiple-runtime-directories">details below</a>).</p>
</blockquote>
<h3>Configuring Helix's runtime files</h3>
<h4>Linux and macOS</h4>
<p>The <strong>runtime</strong> directory is one below the Helix source, so either export a
<code>HELIX_RUNTIME</code> environment variable to point to that directory and add it to
your <code>~/.bashrc</code> or equivalent:</p>
<pre class="language-bash"><a-k>export</a-k> <a-pr>HELIX_RUNTIME</a-pr>=~/src/helix/runtime</pre>
<p>Or, create a symbolic link:</p>
<pre class="language-bash"><a-f>ln</a-f> <a-co>-Tsf</a-co> <a-o>$</a-o><a-pr>PWD</a-pr>/runtime ~/.config/helix/runtime</pre>
<h4>Windows</h4>
<p>Either set the <code>HELIX_RUNTIME</code> environment variable to point to the runtime files using the Windows setting (search for
<code>Edit environment variables for your account</code>) or use the <code>setx</code> command in
Cmd:</p>
<pre class="language-bash"><a-f>setx</a-f> HELIX_RUNTIME <a-s>&quot;%userprofile%\src\helix\runtime&quot;</a-s></pre>
<blockquote>
<p>💡 <code>%userprofile%</code> resolves to your user directory like
<code>C:\Users\Your-Name\</code> for example.</p>
</blockquote>
<p>Or, create a symlink in <code>%appdata%\helix\</code> that links to the source code directory:</p>
<table><thead><tr><th>Method</th><th>Command</th></tr></thead><tbody>
<tr><td>PowerShell</td><td><code>New-Item -ItemType Junction -Target "runtime" -Path "$Env:AppData\helix\runtime"</code></td></tr>
<tr><td>Cmd</td><td><code>cd %appdata%\helix</code> &lt;br/&gt; <code>mklink /D runtime "%userprofile%\src\helix\runtime"</code></td></tr>
</tbody></table>
<blockquote>
<p>💡 On Windows, creating a symbolic link may require running PowerShell or
Cmd as an administrator.</p>
</blockquote>
<h4>Multiple runtime directories</h4>
<p>When Helix finds multiple runtime directories it will search through them for files in the
following order:</p>
<ol>
<li><code>runtime/</code> sibling directory to <code>$CARGO_MANIFEST_DIR</code> directory (this is intended for
developing and testing helix only).</li>
<li><code>runtime/</code> subdirectory of OS-dependent helix user config directory.</li>
<li><code>$HELIX_RUNTIME</code></li>
<li>Distribution-specific fallback directory (set at compile time—not run time—
with the <code>HELIX_DEFAULT_RUNTIME</code> environment variable)</li>
<li><code>runtime/</code> subdirectory of path to Helix executable.</li>
</ol>
<p>This order also sets the priority for selecting which file will be used if multiple runtime
directories have files with the same name.</p>
<h4>Note to packagers</h4>
<p>If you are making a package of Helix for end users, to provide a good out of
the box experience, you should set the <code>HELIX_DEFAULT_RUNTIME</code> environment
variable at build time (before invoking <code>cargo build</code>) to a directory which
will store the final runtime files after installation. For example, say you want
to package the runtime into <code>/usr/lib/helix/runtime</code>. The rough steps a build
script could follow are:</p>
<ol>
<li><code>export HELIX_DEFAULT_RUNTIME=/usr/lib/helix/runtime</code></li>
<li><code>cargo build --profile opt --locked</code></li>
<li><code>cp -r runtime $BUILD_DIR/usr/lib/helix/</code></li>
<li><code>cp target/opt/hx $BUILD_DIR/usr/bin/hx</code></li>
</ol>
<p>This way the resulting <code>hx</code> binary will always look for its runtime directory in
<code>/usr/lib/helix/runtime</code> if the user has no custom runtime in <code>~/.config/helix</code>
or <code>HELIX_RUNTIME</code>.</p>
<h3>Validating the installation</h3>
<p>To make sure everything is set up as expected you should run the Helix health
check:</p>
<pre class="language-bash"><a-f>hx</a-f> <a-co>--health</a-co></pre>
<p>For more information on the health check results refer to
<a href="https://github.com/helix-editor/helix/wiki/Healthcheck">Health check</a>.</p>
<h3>Configure the desktop shortcut</h3>
<p>If your desktop environment supports the
<a href="https://specifications.freedesktop.org/menu-spec/menu-spec-latest.html">XDG desktop menu</a>
you can configure Helix to show up in the application menu by copying the
provided <code>.desktop</code> and icon files to their correct folders:</p>
<pre class="language-bash"><a-f>cp</a-f> contrib/Helix.desktop ~/.local/share/applications
<a-f>cp</a-f> contrib/helix.png ~/.icons <a-c># or ~/.local/share/icons</a-c></pre>
<p>It is recommended to convert the links in the <code>.desktop</code> file to absolute paths to avoid potential problems:</p>
<pre class="language-bash"><a-f>sed</a-f> <a-co>-i</a-co> <a-co>-e</a-co> <a-s>&quot;s|Exec=hx %F|Exec=</a-s><a-eb>$(</a-eb><a-f>readlink</a-f><a-eb> </a-eb><a-co>-f</a-co><a-eb> ~/.cargo/bin/hx)</a-eb><a-s> %F|g&quot;</a-s> \
  <a-co>-e</a-co> <a-s>&quot;s|Icon=helix|Icon=</a-s><a-eb>$(</a-eb><a-f>readlink</a-f><a-eb> </a-eb><a-co>-f</a-co><a-eb> ~/.icons/helix.png)</a-eb><a-s>|g&quot;</a-s> ~/.local/share/applications/Helix.desktop</pre>
<p>To use another terminal than the system default, you can modify the <code>.desktop</code>
file. For example, to use <code>kitty</code>:</p>
<pre class="language-bash"><a-f>sed</a-f> <a-co>-i</a-co> <a-s>&quot;s|Exec=hx %F|Exec=kitty hx %F|g&quot;</a-s> ~/.local/share/applications/Helix.desktop
<a-f>sed</a-f> <a-co>-i</a-co> <a-s>&quot;s|Terminal=true|Terminal=false|g&quot;</a-s> ~/.local/share/applications/Helix.desktop</pre>
<h3>Building the Debian package</h3>
<p>If the <code>.deb</code> file provided on the release page uses a <code>libc</code> version higher
than that used by your Debian, Ubuntu, or Mint system, you can build the package
from source to match your system's dependencies.</p>
<p>Install <code>cargo-deb</code>, the tool used for building the <code>.deb</code> file:</p>
<pre class="language-bash"><a-f>cargo</a-f> install cargo-deb</pre>
<p>After cloning and entering the Helix repository as previously described,
use the following command to build the release binary and package it into a <code>.deb</code> file in a single step.</p>
<pre class="language-bash"><a-f>cargo</a-f> deb <a-co>--</a-co> <a-co>--locked</a-co></pre>
<blockquote>
<p>💡 This locks you into the <code>--release</code> profile. But you can also build helix in any way you like.
As long as you leave a <code>target/release/hx</code> file, it will get packaged with <code>cargo deb --no-build</code></p>
</blockquote>
<blockquote>
<p>💡 Don't worry about the following:</p>
<pre>warning: Failed to find dependency specification
</pre>
<p>Cargo deb just reports which packaged files it didn't derive dependencies for. But
so far the dependency deriving seams very good, even if some of the grammar files are skipped.</p>
</blockquote>
<p>You can find the resulted <code>.deb</code> in <code>target/debian/</code>. It should contain everything it needs, including the</p>
<ul>
<li>completions for bash, fish, zsh</li>
<li>.desktop file</li>
<li>icon (though desktop environments might use their own since the name of the package is correctly <code>helix</code>)</li>
<li>launcher to the binary with the runtime</li>
</ul>
</section><div class="code-panel"><pre class="code src language-markdown"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text"><a-p>##</a-p> <a-tt>Building from source</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text"><a-p>- </a-p>[Configuring Helix&#39;s runtime files](#configuring-helixs-runtime-files)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text"><a-p>  - </a-p>[Linux and macOS](#linux-and-macos)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text"><a-p>  - </a-p>[Windows](#windows)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text"><a-p>  - </a-p>[Multiple runtime directories](#multiple-runtime-directories)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text"><a-p>  - </a-p>[Note to packagers](#note-to-packagers)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text"><a-p>- </a-p>[Validating the installation](#validating-the-installation)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text"><a-p>- </a-p>[Configure the desktop shortcut](#configure-the-desktop-shortcut)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text"><a-p>- </a-p>[Building the Debian package](#building-the-debian-package)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text"><a-p>Requirements:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L14" href="#L14">14</a><span class="code-text"><a-p>Clone the Helix GitHub repository into a directory of your choice. The</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L15" href="#L15">15</a><span class="code-text"><a-p>examples in this documentation assume installation into either `~/src/` on</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L16" href="#L16">16</a><span class="code-text"><a-p>Linux and macOS, or `%userprofile%\src\` on Windows.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L17" href="#L17">17</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L18" href="#L18">18</a><span class="code-text"><a-p>- The [Rust toolchain](https://www.rust-lang.org/tools/install)</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L19" href="#L19">19</a><span class="code-text"><a-p>- The [Git version control system](https://git-scm.com/)</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L20" href="#L20">20</a><span class="code-text"><a-p>- A C++14 compatible compiler to build the tree-sitter grammars, for example GCC or Clang</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L21" href="#L21">21</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L22" href="#L22">22</a><span class="code-text"><a-p>If you are using the `musl-libc` standard library instead of `glibc` the following environment variable must be set during the build to ensure tree-sitter grammars can be loaded correctly:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L23" href="#L23">23</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L24" href="#L24">24</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L25" href="#L25">25</a><span class="code-text"><a-p>RUSTFLAGS=&quot;-C target-feature=-crt-static&quot;</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L26" href="#L26">26</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L27" href="#L27">27</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L28" href="#L28">28</a><span class="code-text"><a-p>1. Clone the repository:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L29" href="#L29">29</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L30" href="#L30">30</a><span class="code-text"><a-p>   </a-p><a-tl>```sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L31" href="#L31">31</a><span class="code-text"><a-p>   </a-p><a-tl>git clone https://github.com/helix-editor/helix</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L32" href="#L32">32</a><span class="code-text"><a-p>   </a-p><a-tl>cd helix</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L33" href="#L33">33</a><span class="code-text"><a-p>   ```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L34" href="#L34">34</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L35" href="#L35">35</a><span class="code-text"><a-p>2. Compile from source:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L36" href="#L36">36</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L37" href="#L37">37</a><span class="code-text"><a-p>   </a-p><a-tl>```sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L38" href="#L38">38</a><span class="code-text"><a-p>   </a-p><a-tl># Reproducible</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L39" href="#L39">39</a><span class="code-text"><a-p>   </a-p><a-tl>cargo install --path helix-term --locked</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L40" href="#L40">40</a><span class="code-text"><a-p>   ```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L41" href="#L41">41</a><span class="code-text"><a-p>   </a-p><a-tl>```sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L42" href="#L42">42</a><span class="code-text"><a-p>   </a-p><a-tl># Optimized</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L43" href="#L43">43</a><span class="code-text"><a-p>   </a-p><a-tl>cargo install \</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L44" href="#L44">44</a><span class="code-text"><a-p>   </a-p><a-tl>   --profile opt \</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L45" href="#L45">45</a><span class="code-text"><a-p>   </a-p><a-tl>   --config &#39;build.rustflags=[&quot;-C&quot;, &quot;target-cpu=native&quot;]&#39; \</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L46" href="#L46">46</a><span class="code-text"><a-p>   </a-p><a-tl>   --path helix-term \</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L47" href="#L47">47</a><span class="code-text"><a-p>   </a-p><a-tl>   --locked</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L48" href="#L48">48</a><span class="code-text"><a-p>   ```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L49" href="#L49">49</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L50" href="#L50">50</a><span class="code-text"><a-p>   Either command will create the `hx` executable and construct the tree-sitter</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L51" href="#L51">51</a><span class="code-text"><a-p>   grammars in the local `runtime` folder.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L52" href="#L52">52</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L53" href="#L53">53</a><span class="code-text"><a-p>&gt; 💡 If you do not want to fetch or build grammars, set an environment variable `HELIX_DISABLE_AUTO_GRAMMAR_BUILD`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L54" href="#L54">54</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L55" href="#L55">55</a><span class="code-text"><a-p>&gt; 💡 Tree-sitter grammars can be fetched and compiled if not pre-packaged. Fetch</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L56" href="#L56">56</a><span class="code-text"><a-p>&gt; grammars with `hx --grammar fetch` and compile them with</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L57" href="#L57">57</a><span class="code-text"><a-p>&gt; `hx --grammar build`. This will install them in</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L58" href="#L58">58</a><span class="code-text"><a-p>&gt; the `runtime` directory within the user&#39;s helix config directory (more</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L59" href="#L59">59</a><span class="code-text"><a-p>&gt; [details below](#multiple-runtime-directories)).</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L60" href="#L60">60</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L61" href="#L61">61</a><span class="code-text"><a-p>### </a-p><a-tt>Configuring Helix&#39;s runtime files</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L62" href="#L62">62</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L63" href="#L63">63</a><span class="code-text"><a-p>#### </a-p><a-tt>Linux and macOS</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L64" href="#L64">64</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L65" href="#L65">65</a><span class="code-text"><a-p>The **runtime** directory is one below the Helix source, so either export a</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L66" href="#L66">66</a><span class="code-text"><a-p>`HELIX_RUNTIME` environment variable to point to that directory and add it to</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L67" href="#L67">67</a><span class="code-text"><a-p>your `~/.bashrc` or equivalent:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L68" href="#L68">68</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L69" href="#L69">69</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L70" href="#L70">70</a><span class="code-text"><a-p>export HELIX_RUNTIME=~/src/helix/runtime</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L71" href="#L71">71</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L72" href="#L72">72</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L73" href="#L73">73</a><span class="code-text"><a-p>Or, create a symbolic link:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L74" href="#L74">74</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L75" href="#L75">75</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L76" href="#L76">76</a><span class="code-text"><a-p>ln -Tsf $PWD/runtime ~/.config/helix/runtime</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L77" href="#L77">77</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L78" href="#L78">78</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L79" href="#L79">79</a><span class="code-text"><a-p>#### </a-p><a-tt>Windows</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L80" href="#L80">80</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L81" href="#L81">81</a><span class="code-text"><a-p>Either set the `HELIX_RUNTIME` environment variable to point to the runtime files using the Windows setting (search for</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L82" href="#L82">82</a><span class="code-text"><a-p>`Edit environment variables for your account`) or use the `setx` command in</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L83" href="#L83">83</a><span class="code-text"><a-p>Cmd:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L84" href="#L84">84</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L85" href="#L85">85</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L86" href="#L86">86</a><span class="code-text"><a-p>setx HELIX_RUNTIME &quot;%userprofile%\src\helix\runtime&quot;</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L87" href="#L87">87</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L88" href="#L88">88</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L89" href="#L89">89</a><span class="code-text"><a-p>&gt; 💡 `%userprofile%` resolves to your user directory like</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L90" href="#L90">90</a><span class="code-text"><a-p>&gt; `C:\Users\Your-Name\` for example.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L91" href="#L91">91</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L92" href="#L92">92</a><span class="code-text"><a-p>Or, create a symlink in `%appdata%\helix\` that links to the source code directory:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L93" href="#L93">93</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L94" href="#L94">94</a><span class="code-text"><a-p>| Method     | Command                                                                                |</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L95" href="#L95">95</a><span class="code-text"><a-p>| ---------- | -------------------------------------------------------------------------------------- |</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L96" href="#L96">96</a><span class="code-text"><a-p>| PowerShell | `New-Item -ItemType Junction -Target &quot;runtime&quot; -Path &quot;$Env:AppData\helix\runtime&quot;`     |</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L97" href="#L97">97</a><span class="code-text"><a-p>| Cmd        | `cd %appdata%\helix` &lt;br/&gt; `mklink /D runtime &quot;%userprofile%\src\helix\runtime&quot;`       |</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L98" href="#L98">98</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L99" href="#L99">99</a><span class="code-text"><a-p>&gt; 💡 On Windows, creating a symbolic link may require running PowerShell or</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L100" href="#L100">100</a><span class="code-text"><a-p>&gt; Cmd as an administrator.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L101" href="#L101">101</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L102" href="#L102">102</a><span class="code-text"><a-p>#### </a-p><a-tt>Multiple runtime directories</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L103" href="#L103">103</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L104" href="#L104">104</a><span class="code-text"><a-p>When Helix finds multiple runtime directories it will search through them for files in the</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L105" href="#L105">105</a><span class="code-text"><a-p>following order:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L106" href="#L106">106</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L107" href="#L107">107</a><span class="code-text"><a-p>1. `runtime/` sibling directory to `$CARGO_MANIFEST_DIR` directory (this is intended for</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L108" href="#L108">108</a><span class="code-text"><a-p>  developing and testing helix only).</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L109" href="#L109">109</a><span class="code-text"><a-p>2. `runtime/` subdirectory of OS-dependent helix user config directory.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L110" href="#L110">110</a><span class="code-text"><a-p>3. `$HELIX_RUNTIME`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L111" href="#L111">111</a><span class="code-text"><a-p>4. Distribution-specific fallback directory (set at compile time—not run time—</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L112" href="#L112">112</a><span class="code-text"><a-p>   with the `HELIX_DEFAULT_RUNTIME` environment variable)</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L113" href="#L113">113</a><span class="code-text"><a-p>5. `runtime/` subdirectory of path to Helix executable.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L114" href="#L114">114</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L115" href="#L115">115</a><span class="code-text"><a-p>This order also sets the priority for selecting which file will be used if multiple runtime</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L116" href="#L116">116</a><span class="code-text"><a-p>directories have files with the same name.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L117" href="#L117">117</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L118" href="#L118">118</a><span class="code-text"><a-p>#### </a-p><a-tt>Note to packagers</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L119" href="#L119">119</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L120" href="#L120">120</a><span class="code-text"><a-p>If you are making a package of Helix for end users, to provide a good out of</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L121" href="#L121">121</a><span class="code-text"><a-p>the box experience, you should set the `HELIX_DEFAULT_RUNTIME` environment</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L122" href="#L122">122</a><span class="code-text"><a-p>variable at build time (before invoking `cargo build`) to a directory which</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L123" href="#L123">123</a><span class="code-text"><a-p>will store the final runtime files after installation. For example, say you want</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L124" href="#L124">124</a><span class="code-text"><a-p>to package the runtime into `/usr/lib/helix/runtime`. The rough steps a build</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L125" href="#L125">125</a><span class="code-text"><a-p>script could follow are:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L126" href="#L126">126</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L127" href="#L127">127</a><span class="code-text"><a-p>1. `export HELIX_DEFAULT_RUNTIME=/usr/lib/helix/runtime`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L128" href="#L128">128</a><span class="code-text"><a-p>1. `cargo build --profile opt --locked`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L129" href="#L129">129</a><span class="code-text"><a-p>1. `cp -r runtime $BUILD_DIR/usr/lib/helix/`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L130" href="#L130">130</a><span class="code-text"><a-p>1. `cp target/opt/hx $BUILD_DIR/usr/bin/hx`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L131" href="#L131">131</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L132" href="#L132">132</a><span class="code-text"><a-p>This way the resulting `hx` binary will always look for its runtime directory in</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L133" href="#L133">133</a><span class="code-text"><a-p>`/usr/lib/helix/runtime` if the user has no custom runtime in `~/.config/helix`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L134" href="#L134">134</a><span class="code-text"><a-p>or `HELIX_RUNTIME`.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L135" href="#L135">135</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L136" href="#L136">136</a><span class="code-text"><a-p>### </a-p><a-tt>Validating the installation</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L137" href="#L137">137</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L138" href="#L138">138</a><span class="code-text"><a-p>To make sure everything is set up as expected you should run the Helix health</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L139" href="#L139">139</a><span class="code-text"><a-p>check:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L140" href="#L140">140</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L141" href="#L141">141</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L142" href="#L142">142</a><span class="code-text"><a-p>hx --health</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L143" href="#L143">143</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L144" href="#L144">144</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L145" href="#L145">145</a><span class="code-text"><a-p>For more information on the health check results refer to</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L146" href="#L146">146</a><span class="code-text"><a-p>[Health check](https://github.com/helix-editor/helix/wiki/Healthcheck).</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L147" href="#L147">147</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L148" href="#L148">148</a><span class="code-text"><a-p>### </a-p><a-tt>Configure the desktop shortcut</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L149" href="#L149">149</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L150" href="#L150">150</a><span class="code-text"><a-p>If your desktop environment supports the</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L151" href="#L151">151</a><span class="code-text"><a-p>[XDG desktop menu](https://specifications.freedesktop.org/menu-spec/menu-spec-latest.html)</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L152" href="#L152">152</a><span class="code-text"><a-p>you can configure Helix to show up in the application menu by copying the</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L153" href="#L153">153</a><span class="code-text"><a-p>provided `.desktop` and icon files to their correct folders:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L154" href="#L154">154</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L155" href="#L155">155</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L156" href="#L156">156</a><span class="code-text"><a-p>cp contrib/Helix.desktop ~/.local/share/applications</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L157" href="#L157">157</a><span class="code-text"><a-p>cp contrib/helix.png ~/.icons # or ~/.local/share/icons</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L158" href="#L158">158</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L159" href="#L159">159</a><span class="code-text"><a-p>It is recommended to convert the links in the `.desktop` file to absolute paths to avoid potential problems:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L160" href="#L160">160</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L161" href="#L161">161</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L162" href="#L162">162</a><span class="code-text"><a-p>sed -i -e &quot;s|Exec=hx %F|Exec=$(readlink -f ~/.cargo/bin/hx) %F|g&quot; \</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L163" href="#L163">163</a><span class="code-text"><a-p>  -e &quot;s|Icon=helix|Icon=$(readlink -f ~/.icons/helix.png)|g&quot; ~/.local/share/applications/Helix.desktop</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L164" href="#L164">164</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L165" href="#L165">165</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L166" href="#L166">166</a><span class="code-text"><a-p>To use another terminal than the system default, you can modify the `.desktop`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L167" href="#L167">167</a><span class="code-text"><a-p>file. For example, to use `kitty`:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L168" href="#L168">168</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L169" href="#L169">169</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L170" href="#L170">170</a><span class="code-text"><a-p>sed -i &quot;s|Exec=hx %F|Exec=kitty hx %F|g&quot; ~/.local/share/applications/Helix.desktop</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L171" href="#L171">171</a><span class="code-text"><a-p>sed -i &quot;s|Terminal=true|Terminal=false|g&quot; ~/.local/share/applications/Helix.desktop</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L172" href="#L172">172</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L173" href="#L173">173</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L174" href="#L174">174</a><span class="code-text"><a-p>### </a-p><a-tt>Building the Debian package</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L175" href="#L175">175</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L176" href="#L176">176</a><span class="code-text"><a-p>If the `.deb` file provided on the release page uses a `libc` version higher</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L177" href="#L177">177</a><span class="code-text"><a-p>than that used by your Debian, Ubuntu, or Mint system, you can build the package</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L178" href="#L178">178</a><span class="code-text"><a-p>from source to match your system&#39;s dependencies.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L179" href="#L179">179</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L180" href="#L180">180</a><span class="code-text"><a-p>Install `cargo-deb`, the tool used for building the `.deb` file:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L181" href="#L181">181</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L182" href="#L182">182</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L183" href="#L183">183</a><span class="code-text"><a-p>cargo install cargo-deb</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L184" href="#L184">184</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L185" href="#L185">185</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L186" href="#L186">186</a><span class="code-text"><a-p>After cloning and entering the Helix repository as previously described,</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L187" href="#L187">187</a><span class="code-text"><a-p>use the following command to build the release binary and package it into a `.deb` file in a single step.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L188" href="#L188">188</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L189" href="#L189">189</a><span class="code-text"><a-p>```</a-p><a-tl>sh</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L190" href="#L190">190</a><span class="code-text"><a-p>cargo deb -- --locked</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L191" href="#L191">191</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L192" href="#L192">192</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L193" href="#L193">193</a><span class="code-text"><a-p>&gt; 💡 This locks you into the `--release` profile. But you can also build helix in any way you like.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L194" href="#L194">194</a><span class="code-text"><a-p>&gt; As long as you leave a `target/release/hx` file, it will get packaged with `cargo deb --no-build`</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L195" href="#L195">195</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L196" href="#L196">196</a><span class="code-text"><a-p>&gt; 💡 Don&#39;t worry about the following:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L197" href="#L197">197</a><span class="code-text"><a-p>&gt; </a-p><a-tl>```</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L198" href="#L198">198</a><span class="code-text"><a-p>&gt; </a-p><a-tl>warning: Failed to find dependency specification</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L199" href="#L199">199</a><span class="code-text"><a-p>&gt; ```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L200" href="#L200">200</a><span class="code-text"><a-p>&gt; Cargo deb just reports which packaged files it didn&#39;t derive dependencies for. But</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L201" href="#L201">201</a><span class="code-text"><a-p>&gt; so far the dependency deriving seams very good, even if some of the grammar files are skipped.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L202" href="#L202">202</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L203" href="#L203">203</a><span class="code-text"><a-p>You can find the resulted `.deb` in `target/debian/`. It should contain everything it needs, including the</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L204" href="#L204">204</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L205" href="#L205">205</a><span class="code-text"><a-p>- completions for bash, fish, zsh</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L206" href="#L206">206</a><span class="code-text"><a-p>- .desktop file</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L207" href="#L207">207</a><span class="code-text"><a-p>- icon (though desktop environments might use their own since the name of the package is correctly `helix`)</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L208" href="#L208">208</a><span class="code-text"><a-p>- </a-p>launcher to the binary with the runtime</span></span></pre></div></div>
</main>
</body>
</html>
