> For the complete documentation index, see [llms.txt](https://wiki.libreelec.tv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.libreelec.tv/development/build-commands/build-commands-le90.md).

# Build Commands LE 9.0.x

| Image             | Command                                          |
| ----------------- | ------------------------------------------------ |
| Generic (x86\_64) | PROJECT=Generic ARCH=x86\_64 make image          |
| Raspberry Pi 0/1  | PROJECT=RPi ARCH=arm DEVICE=RPi make image       |
| Raspberry Pi 2/3  | PROJECT=RPi ARCH=arm DEVICE=RPi2 make image      |
| Raspberry Pi 4    | PROJECT=RPi ARCH=arm DEVICE=RPi4 make image      |
| Allwinner A20     | PROJECT=Allwinner ARCH=arm DEVICE=A20 make image |
| Allwinner A64     | PROJECT=Allwinner ARCH=arm DEVICE=A64 make image |
| Allwinner H3      | PROJECT=Allwinner ARCH=arm DEVICE=H3 make image  |
| Allwinner H5      | PROJECT=Allwinner ARCH=arm DEVICE=H5 make image  |
| Allwinner H6      | PROJECT=Allwinner ARCH=arm DEVICE=H6 make image  |

## Notes

The Virtual project was combined into the Generic image. Running `make image` will output an OVA file in addition to the normal .img.gz and .tar files.

Amlogic, Raspberry Pi, and Rockchip build projects require a `DEVICE=<name>` to be specified. For example, to build an Amlogic image for a LibreComputer LePotato board:

```
PROJECT=Amlogic ARCH=arm DEVICE=LePotato make image
```

## Environment

Official releases were built using Ubuntu 16.04 and 18.04 LTS.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.libreelec.tv/development/build-commands/build-commands-le90.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.