mirror of
https://github.com/dolphin-emu/dolphin.git
synced 2024-11-14 13:27:45 -07:00
outsource the heavy lifting for Arch info
parent
f2942bc966
commit
88579573f9
@ -19,6 +19,9 @@ sudo apt install libudev-dev libsystemd-dev || sudo apt install libeudev-dev #di
|
||||
sudo dnf install vulkan-loader vulkan-loader-devel cmake git gcc-c++ libXext-devel libgudev qt6-qtbase-devel qt6-qtbase-private-devel systemd-devel openal-soft-devel libevdev-devel libao-devel SOIL-devel libXrandr-devel pulseaudio-libs-devel bluez-libs-devel libusb-devel libXi-devel
|
||||
```
|
||||
|
||||
### Arch:
|
||||
see https://aur.archlinux.org/packages/dolphin-emu-git?all_deps=1#pkgdeps
|
||||
|
||||
### (!WIP) Chrome/Chromium OS (via [Chromebrew](https://github.com/chromebrew/chromebrew)):
|
||||
```sh
|
||||
crew install binutils wayland cmake gcc buildessential git libx11 pkg-config libxi libxext qtbase qtwayland mesa libxfixes libxxf86vm libusb libdrm libxrandr gettext linuxheaders enet libxshmfence libunwind lm_sensors elfutils patchelf vulkan_icd_loader
|
||||
@ -113,4 +116,4 @@ On some distributions of Linux, package maintainers provide unofficial, unmodifi
|
||||
- The compiler will normally tell you what's going on if you run into an error. Read the error messages closely and look them up verbatim to see if it's something missing on your system and/or a typo in recent Dolphin commits.
|
||||
- QT5 support has been [officially been deprecated](https://dolphin-emu.org/blog/2022/06/09/leaving-a-legend/) by the Dolphin development team. While it's still technically possible to build using QT5, as of [5.0-17764](https://dolphin-emu.org/download/dev/950e1f94dc73b56309c090d7b04033506b057ae0/) the minimum requirement was raised to 5.15. It's recommended to install the proper QT6 dependencies instead - by the time you're reading this, it's possible that not even 5.15 works anymore.
|
||||
- That being said, there _is_ a [known bug](https://bugs.dolphin-emu.org/issues/12913) as of QT **6.3** where mouse clicks don't work on Linux. No one's really sure why yet.
|
||||
- Need more speed? As an alternative to `cmake ..` during the build process, type `cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS=-mcpu=native -DCMAKE_C_FLAGS=-mcpu=native` instead. The resulting build will be optimized specifically for YOUR processor! The difference is more noticeable the weaker your computer is. Note that this may result in longer compile times, and the binaries you build will almost certainly be unusable on any computer besides your own.
|
||||
- Need more speed? As an alternative to `cmake ..` during the build process, type `cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS=-mcpu=native -DCMAKE_C_FLAGS=-mcpu=native` instead. The resulting build will be optimized specifically for YOUR processor! The difference is more noticeable the weaker your computer is. Note that this may result in longer compile times, and the binaries you build will almost certainly be unusable on any computer besides your own. AUR users of `*-git` packages can get a similar effect by following https://wiki.archlinux.org/title/makepkg#Building_optimized_binaries
|
Loading…
Reference in New Issue
Block a user