File: platform-build.md

package info (click to toggle)
chiaki 2.1.0-1.1
  • links: PTS
  • area: main
  • in suites: bookworm, bullseye, sid
  • size: 4,976 kB
  • sloc: ansic: 17,461; cpp: 7,282; xml: 2,689; sh: 372; python: 96; makefile: 6
file content (30 lines) | stat: -rw-r--r-- 1,158 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

# Platform-specific build instructions

## Fedora

On Fedora, build dependencies can be installed via:

```
sudo dnf install cmake make qt5-qtmultimedia-devel qt5-qtsvg-devel qt5-qtbase-gui ffmpeg-devel opus-devel openssl-devel python3-protobuf protobuf-c protobuf-devel qt5-rpm-macros SDL2-devel libevdev-devel systemd-devel
```

Then, Chiaki builds just like any other CMake project:
```
git submodule update --init
mkdir build && cd build
cmake ..
make
```

In order to utilize hardware decoding, necessary VA-API component needs to be installed separately depending on your GPU. For example on Fedora:

* **Intel**: `libva-intel-driver`(majority laptop and desktop) OR `libva-intel-hybrid-driver`(most netbook with Atom processor)
* **AMD**: Already part of default installation
* **Nvidia**: `libva-vdpau-driver`

## Windows

Windows support is reduced to the absolute minimum for maintainability.
Official Windows builds are done on AppVeyor within MSYS2 using this script, which can also work as a template for building locally: [scripts/appveyor.sh](../scripts/appveyor.sh).
Other methods of building may work, but will not be officially supported.