jalr/OpenRGB
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Adding qt5-linguist to Fedora build dependencies

Browse source
This commit is contained in:
Chris 2022-07-20 14:34:13 +10:00
parent d33c410ea6
commit c479a06312
1 changed files with 28 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

56
README.md
View file

@ -42,7 +42,7 @@ There have been two instances of hardware damage in OpenRGB's development and we
* You will need the **Microsoft Visual 2019 C++ runtime** installed. You can get it [here](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads)
* Pre-built Release binaries are available for Windows 10 / 11 64bit under the [Releases section](https://gitlab.com/CalcProgrammer1/OpenRGB/-/releases/permalink/latest#Windows-64-bit) on GitLab.
* If you want to test the latest (potentially unstable) code you can also get the Windows package from [the pipeline builds](https://gitlab.com/CalcProgrammer1/OpenRGB/-/jobs/artifacts/master/download?job=Windows+64).
<details>
<summary><h5>Compiling</h5></summary>
@ -51,7 +51,7 @@ There have been two instances of hardware damage in OpenRGB's development and we
2. Open the OpenRGB.pro project in Qt Creator.
3. Use the MSVC compiler kit, either 32- or 64-bit, to build the application.
4. Run the project from Qt Creator. If you want to use your custom build standalone, download the latest matching Release package and replace the OpenRGB.exe in it with your new build.
</details>
----
@ -68,14 +68,14 @@ There have been two instances of hardware damage in OpenRGB's development and we
* Pre-built binaries in AppImage format are available under the [Releases](https://gitlab.com/CalcProgrammer1/OpenRGB/-/releases/permalink/latest#Linux-64-bit) section on GitLab.
* There is also a unofficial universal Flatpak build [available on Flathub](https://flathub.org/apps/details/org.openrgb.OpenRGB). Note: To ensure you have device permissions please [install the latest UDEV rules](#installing-udev-rules-manually).
<details>
<summary><h5>Arch</h5></summary>
##### Binaries
* OpenRGB is available in the AUR for both the [release](https://aur.archlinux.org/packages/openrgb/) and [pipeline](https://aur.archlinux.org/packages/openrgb-git/) builds
</details>
<details>
<summary><h5>Debian / Ubuntu</h5></summary>
@ -92,7 +92,7 @@ There have been two instances of hardware damage in OpenRGB's development and we
2. git clone https://gitlab.com/CalcProgrammer1/OpenRGB
3. cd OpenRGB
4. qmake OpenRGB.pro
5. make -j$(nproc)
5. make -j$(nproc)
6. You can then run the application from the compile directory with `./openrgb` or install with `make install`
7. You will also need to [install the latest UDEV rules](#installing-udev-rules-manually).
@ -112,16 +112,16 @@ There have been two instances of hardware damage in OpenRGB's development and we
##### Compiling
1. Install build dependencies
- `sudo dnf install automake gcc-c++ qt5-qtbase-devel hidapi-devel libusbx-devel mbedtls-devel`
- `sudo dnf install automake gcc-c++ qt5-qtbase-devel qt5-linguist hidapi-devel libusbx-devel mbedtls-devel`
2. git clone https://gitlab.com/CalcProgrammer1/OpenRGB
3. cd OpenRGB
4. qmake-qt5 OpenRGB.pro
5. make -j$(nproc)
5. make -j$(nproc)
6. You can then run the application from the compile directory with `./openrgb` or install with `make install`
7. You will also need to [install the latest UDEV rules](#installing-udev-rules-manually).
</details>
----
### SMBus Access
@ -134,21 +134,21 @@ There have been two instances of hardware damage in OpenRGB's development and we
2. Load the i2c driver for your chipset:
<details>
<summary><h6>Intel</h6></summary>
* `sudo modprobe i2c-i801`
* `sudo modprobe i2c-nct6775` - Secondary controller for motherboard LEDs (requires [kernel patch](https://gitlab.com/CalcProgrammer1/OpenRGB/-/wikis/OpenRGB-Kernel-Patch))
* `sudo modprobe i2c-nct6775` - Secondary controller for motherboard LEDs (requires [kernel patch](https://gitlab.com/CalcProgrammer1/OpenRGB/-/wikis/OpenRGB-Kernel-Patch))
</details>
<details>
<summary><h6>AMD</h6></summary>
* `sudo modprobe i2c-piix4`
* `sudo modprobe i2c-piix4`
* Unmodified kernel will have one interface, patched kernel will have two. The first at 0x0B00 and the second at 0x0B20. The 0x0B20 interface is for motherboard LEDs.
</details>
----
* You'll have to enable user access to your SMBus if you don't run as root.
- List all SMBus controllers: `sudo i2cdetect -l`
- Note the number for PIIX4, I801, and NCT6775 controllers.
@ -160,8 +160,8 @@ There have been two instances of hardware damage in OpenRGB's development and we
* USB devices require [udev rules](#installing-udev-rules-manually) to access as a normal user.
* Alternatively you can run OpenRGB as root to detect all USB devices. (Not recommended)
* USB based Gigabyte AORUS motherboards may also have an ACPI conflict. Please [add a kernel parameter](#kernel-parameters) to resolve this conflict.
* USB based Gigabyte AORUS motherboards may also have an ACPI conflict. Please [add a kernel parameter](#kernel-parameters) to resolve this conflict.
### Installing UDEV rules manually
* If you have installed OpenRGB from a package then latest UDEV rules are installed locally at `/usr/lib/udev/rules.d/60-openrgb.rules`
@ -179,23 +179,23 @@ There have been two instances of hardware damage in OpenRGB's development and we
<details>
<summary><h5>Arch</h5></summary>
* Please see [the Arch wiki](https://wiki.archlinux.org/title/kernel_parameters) for details on how to update your bootloader.
</details>
<details>
<summary><h5>Debian / Ubuntu</h5></summary>
* Please see [the Ubuntu Documentation](https://wiki.ubuntu.com/Kernel/KernelBootParameters) for Kernel Parameters for more information on updating your boot parameters.
</details>
<details>
<summary><h5>Fedora</h5></summary>
* On Fedora, install `grubby` and then following command:
`grubby --update-kernel=ALL --args="acpi_enforce_resources=lax"`
`grubby --update-kernel=ALL --args="acpi_enforce_resources=lax"`
* For more information please refer to the Fedora docs for [grubby](https://docs.fedoraproject.org/en-US/fedora/latest/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/#sec-Making_Persistent_Changes_to_a_GRUB_2_Menu_Using_the_grubby_Tool).
</details>
----
@ -294,7 +294,7 @@ There have been two instances of hardware damage in OpenRGB's development and we
* Http Hook Plugin (by morg): https://gitlab.com/OpenRGBDevelopers/OpenRGBHttpHookPlugin
* Razer extras Plugin (by morg): https://gitlab.com/OpenRGBDevelopers/OpenRGBRazerExtrasPlugin
* Fan Hardware Sync Plugin (by Shady): https://gitlab.com/ShadyNawara/openrgbfansyncplugin
## Projects Used
* WinRing0: https://openlibsys.org/
@ -311,7 +311,7 @@ There have been two instances of hardware damage in OpenRGB's development and we
* httplib: https://github.com/yhirose/cpp-httplib
* mdns: https://github.com/mjansson/mdns
* macUSPCIO: https://github.com/ShadyNawara/macUSPCIO
## Projects Researched
While no code from these projects directly made its way into OpenRGB, these projects have been invaluable resources for protocol information.