# Static

{% hint style="success" %} <mark style="color:orange;">**Build Profile**</mark>

* [x] Prefer [**`mimalloc`**](https://github.com/microsoft/mimalloc) over other musl allocators ([<mark style="color:red;">**Not Always**</mark>](#user-content-fn-1)[^1])
* [x] Prefer [LTO](https://gcc.gnu.org/wiki/LinkTimeOptimization)
* [x] Prefer [PIE](https://en.wikipedia.org/wiki/Position-independent_code)
  {% endhint %}

{% hint style="success" %} <mark style="color:purple;">**Sources**</mark>

* Most (around 90%) of our **`static`** packages are built from source using standard build tools.
* The rest are fetched from upstream like GitHub Releases etc.
  {% endhint %}

{% hint style="warning" %} <mark style="color:orange;">**`Nomenclature`**</mark>

* **`*source*`** : Implies it was built from source

* **`*official*`** : Implies it was built/fetched from official source

* **`*stable*`** : Implies it was likely fetched from upstream source & not built from source
  {% endhint %}

* [x] If the binary is a desktop app i.e. needs desktop integration, it needs to go under [**./packages**](https://github.com/pkgforge/soarpkgs/tree/main/packages)

[^1]: We have had reports of users running into segfault errors on old hardware


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pkgforge.dev/formats/binaries/static.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.