piwalker/dolphin
1
0
Fork 0
mirror of https://github.com/dolphin-emu/dolphin.git synced 2024-11-14 13:27:45 -07:00
Code Issues Actions Packages Projects Releases Wiki Activity

replaced -mcpu=native with -march=native

Riedler 2023-06-15 11:07:04 +02:00
parent b72d78337e
commit 7a81d6b9e1
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Building-for-Linux.md

@ -121,4 +121,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. This can be worked around by setting `QT_XCB_NO_XI2=1`. As an example, you can just run Dolphin using the `QT_XCB_NO_XI2=1 dolphin-emu` command in a terminal. Another easy way to accomplish this would be to install `menulibre` from your package manager, open it and use it to modify Dolphin's desktop file, and change the Command to read something like `env QT_XCB_NO_XI2=1 QT_QPA_PLATFORM=xcb dolphin-emu`. Although it would be more proper to set this as an [environment variable](https://wiki.archlinux.org/title/environment_variables).
- 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
- Need more speed? As an alternative to `cmake ..` during the build process, type `cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS=-march=native -DCMAKE_C_FLAGS=-march=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