| 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.007660 |
| First Submitted: | 2020-02-14 03:47 (UTC) |
| Last Updated: | 2025-02-16 20:54 (UTC) |
Solution for following error is installation of qt5-tools package. I'd add this pack to dependencies list.
make: /usr/bin/lrelease: No such file or directory
make: *** [Makefile:2605: .qm/OpenRGB_fr.qm] Error 127
==> ERROR: A failure occurred in build().
Aborting...
error: failed to build 'openrgb-git-r2403.3045e860-1':
error: packages failed to build: openrgb-git-r2403.3045e860-1
Sorry to keep you folks waiting. Everything should be fine now.
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`
@Myrddin you can add me as co-maintainer so can I push the fix for the udev-rules
@harre thanks a lot. This solved my issue as well.
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`
I get same error as @cnekmp
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
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
}
@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.
Pinned Comments