Sorry to keep you folks waiting. Everything should be fine now.
Search Criteria
Package Details: openrgb-git 0.9.1233.g1809c75-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/openrgb-git.git (read-only, click to copy) |
---|---|
Package Base: | openrgb-git |
Description: | Configuration utility for RGB lights supporting motherboards, RAM, & peripherals |
Upstream URL: | https://gitlab.com/CalcProgrammer1/OpenRGB |
Keywords: | led |
Licenses: | GPL-2.0-only |
Conflicts: | openrgb |
Provides: | openrgb |
Submitter: | Myrddin |
Maintainer: | CalcProgrammer1 |
Last Packager: | CalcProgrammer1 |
Votes: | 34 |
Popularity: | 0.081253 |
First Submitted: | 2020-02-14 03:47 (UTC) |
Last Updated: | 2025-02-16 20:54 (UTC) |
Dependencies (6)
- hidapi (hidapi-gitAUR)
- libusb (libusb-gitAUR)
- mbedtls (mbedtls-gitAUR, mbedtls-dtlsAUR)
- qt5-tools
- git (git-gitAUR, git-glAUR) (make)
- i2c-nct6793-dkms (i2c-nct6793-dkms-gitAUR) (optional) – Nuvoton SMBus driver, needed for onboard RGB on certain ASUS Z270 and Z370 boards
Required by (15)
- keyboard-center (requires openrgb) (optional)
- keyboard-center2 (requires openrgb) (optional)
- keyboard-visualizer-git (requires openrgb)
- openrgb-plugin-e131-receiver-git (requires openrgb)
- openrgb-plugin-effects-git (requires openrgb)
- openrgb-plugin-fan-sync-git (requires openrgb)
- openrgb-plugin-hardware-sync-git (requires openrgb)
- openrgb-plugin-http-hook-git (requires openrgb)
- openrgb-plugin-razer-extras-git (requires openrgb)
- openrgb-plugin-sample-git (requires openrgb)
- openrgb-plugin-scheduler-git (requires openrgb)
- openrgb-plugin-skin-git (requires openrgb)
- openrgb-plugin-visual-map-git (requires openrgb)
- python-openrgb (requires openrgb)
- python-openrgb-git (requires openrgb)
Sources (3)
Myrddin commented on 2022-05-03 23:52 (UTC)
cnekmp commented on 2022-05-02 21:49 (UTC)
Please modify PKGBUILD with adding line to build(). It's annoying to add this line with every update of this package
./scripts/build-udev-rules.sh `pwd`
harre commented on 2022-04-24 00:51 (UTC)
@Myrddin you can add me as co-maintainer so can I push the fix for the udev-rules
cnekmp commented on 2022-04-19 21:11 (UTC)
@harre thanks a lot. This solved my issue as well.
harre commented on 2022-04-19 01:42 (UTC) (edited on 2022-04-19 01:42 (UTC) by harre)
It seems they have added that the udev-rules will be generated automagically.
Just add this step last in the build():
./scripts/build-udev-rules.sh `pwd`
harre commented on 2022-04-19 00:56 (UTC)
I get same error as @cnekmp
cnekmp commented on 2022-04-18 18:51 (UTC)
Version r1772.84de7ebc-1 fails to build:
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Info: creating stash file /home/user/.cache/paru/clone/openrgb-
git/src/openrgb/.qmake.stash
Project MESSAGE: 60-openrgb.rules - UDEV rules file missing. Adding script to build
.....
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat '60-openrgb.rules': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
error: failed to build 'openrgb-git-r1772.84de7ebc-1':
error: packages failed to build: openrgb-git-r1772.84de7ebc-1
[user@unknown ~]$ ls -la /usr/lib/udev/rules.d/60-openrgb.rules
-rw-r--r-- 1 root root 68789 Apr 12 21:07 /usr/lib/udev/rules.d/60-openrgb.rules
Neko-san commented on 2021-12-11 22:29 (UTC)
I managed to get it to build like this:
options=(!lto)
pkgver() {
cd openrgb
printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}
build() {
cd "$srcdir/openrgb"
qmake QMAKE_CFLAGS="${CFLAGS}" QMAKE_CXXFLAGS="${CXXFLAGS}" QMAKE_LFLAGS="${LDFLAGS}" OpenRGB.pro
make -j2
}
package() {
cd "$srcdir/openrgb"
install -Dm755 openrgb "$pkgdir"/usr/bin/openrgb
install -Dm644 qt/OpenRGB.png "$pkgdir"/usr/share/pixmaps/openrgb.png
install -Dm644 -t "$pkgdir"/usr/share/applications ../openrgb.desktop
install -Dm644 -t "$pkgdir"/usr/lib/udev/rules.d 60-openrgb.rules
install -Dm644 -t "$pkgdir"/usr/lib/modules-load.d ../openrgb.conf
}
gardotd426 commented on 2021-11-29 07:59 (UTC)
@NoraViper PKGBUILDs are never supposed to require user interaction during the build process (like any prompts asking the user whether they want to enable or disable something). And just default enabling the MSI Mystic Light code would be a horrible idea considering the fact that it's been known to brick motherboards in the past. So default enabling it could very well lead to a bunch of people bricking their hardware and it would be the PKGBUILD maintainer's fault.
NovaViper commented on 2021-11-28 23:49 (UTC)
Can you add an option that automatically enables MSI Mystic Light support? Thanks
Pinned Comments