linux-enable-ir-emitter-git/PKGBUILD: line 33: pushd: .github/workflows/deps: No such file or directory

Avoid building the dependencies and statically linking them.

diff --git a/PKGBUILD b/PKGBUILD
index f280235..bf57dca 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@
 # Contributor: Nathaniel van Diepen <eeems@eeems.email>

 pkgname=linux-enable-ir-emitter-git
-pkgver=6.0.3.r0.gb8ee83d
+pkgver=6.1.1.r1.g7e0a520
 pkgrel=1
 pkgdesc="Enables infrared cameras that are not directly enabled out-of-the box"
 url="https://github.com/EmixamPP/linux-enable-ir-emitter"
@@ -15,7 +15,7 @@ provides=(linux-enable-ir-emitter)
 conflicts=(linux-enable-ir-emitter chicony-ir-toggle)

 makedepends=(git meson cmake argparse qt6-base zlib gtk3)
-depends=(bash cairo glib2 gdk-pixbuf2 gtk3 glibc gcc-libs)
+depends=(bash cairo glib2 gdk-pixbuf2 gtk3 glibc gcc-libs opencv yaml-cpp)

 install=linux-enable-ir-emitter.install
 options=(emptydirs !buildflags)
@@ -30,12 +30,7 @@ pkgver() {

 build() {
     cd "${srcdir}/${pkgname}"
-    pushd .github/workflows/deps
-    cmake . -B build -GNinja
-    ninja -C build
-    popd
-    meson setup --reconfigure build --libdir=lib --prefer-static --pkg-config-path=$(find .github -name "pkgconfig")
-    meson configure build --optimization=s --prefix=/usr --strip
+    meson setup --prefix=/usr --buildtype=plain build
     meson compile -C build
 }

btw this package fails to build even with gcc13 for the latest upstream commit, is someone willing to help with patches?

@MikeWalrus Upstream uses gcc 13 in their CI, so it will involve less patches if this package will use it too. What are significant downsides of using gcc 13 instead of the latest gcc?

@MikeWalrus I do not completely understand what patch do you propose. Forcefully enable LTO even if disabled in makepkg.conf?

@nojo I agree and that’s why I suggest patching the flags in meson.build.

You're right - package successfully compiles with lto enabled in /etc/makepkg.conf. Nevertheless, I think it's would be incorrect to both

• assume that package would always be built with lto

• forcefully enable lto even if it disabled in makepkg.conf

not to avoid problems for users with custom config

@FabioLolix Can you elaborate on this? Disabling lto will only break the package and that's probably why nojo has that error. :D

Enabling lto makes the error disappear, so maybe you've disabled it.

lto is enabled by default now, it should be disabled when it cause problems by default not to avoid problems for users with custom config