Package Details: obs-plugin-looking-glass 2:B7-1

Git Clone URL: https://aur.archlinux.org/looking-glass.git (read-only, click to copy)
Package Base: looking-glass
Description: Plugin for OBS Studio to stream directly from Looking Glass without having to record the Looking Glass client
Upstream URL: https://looking-glass.io/
Licenses: GPL-2.0-or-later
Submitter: Omar007
Maintainer: Omar007
Last Packager: Omar007
Votes: 42
Popularity: 0.85
First Submitted: 2017-12-22 16:49 (UTC)
Last Updated: 2025-03-08 14:17 (UTC)

Latest Comments

1 2 3 4 5 6 .. 10 Next › Last »

Quaternions commented on 2025-03-09 08:10 (UTC)

I'm getting a build error:

In file included from /home/quat/.cache/paru/clone/looking-glass/src/looking-glass-B7/repos/nanosvg/src/nanosvgrast.h:28,
                 from /home/quat/.cache/paru/clone/looking-glass/src/looking-glass-B7/client/src/overlay_utils.c:32:
/home/quat/.cache/paru/clone/looking-glass/src/looking-glass-B7/repos/nanosvg/src/nanosvg.h: In function ‘nsvg__parseTransform’:
/home/quat/.cache/paru/clone/looking-glass/src/looking-glass-B7/repos/nanosvg/src/nanosvg.h:1656:15: error: ‘t[0]’ may be used uninitialized [-Werror=maybe-uninitialized]
 1656 |         float t[6];
      |               ^
compilation terminated due to -Wfatal-errors.
cc1: all warnings being treated as errors
make[2]: *** [CMakeFiles/looking-glass-client.dir/build.make:268: CMakeFiles/looking-glass-client.dir/src/overlay_utils.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:583: CMakeFiles/looking-glass-client.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'looking-glass-2:B7-1 (looking-glass looking-glass-module-dkms)':

I silenced the error by patching the warning out of the cmake files, but that doesn't seem like a good solution.

xAsh commented on 2025-02-03 17:46 (UTC) (edited on 2025-02-03 17:46 (UTC) by xAsh)

OBS Studio as a dependency is insane. Is there no way to make the plugin optional, or alternative builds without it?

nathan1998tw commented on 2025-02-03 15:31 (UTC) (edited on 2025-02-03 16:39 (UTC) by nathan1998tw)

Since kernel version 6.13.0, the import method of namespace needs to be changed:

--- a/module/kvmfr.c
+++ b/module/kvmfr.c
@@ -591,3 +591,5 @@
 MODULE_VERSION("0.0.8");
-#if LINUX_VERSION_CODE >= KERNEL_VERSION(5,16,0)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(6,13,0)
+MODULE_IMPORT_NS("DMA_BUF");
+#elif LINUX_VERSION_CODE >= KERNEL_VERSION(5,16,0)
 MODULE_IMPORT_NS(DMA_BUF);
 #endif

Omar007 commented on 2024-08-14 12:22 (UTC)

@tannisroot: it does not. You need to properly configure your system/chroot. Please see https://wiki.archlinux.org/title/Arch_User_Repository, specifically section 2.1

tannisroot commented on 2024-08-14 08:45 (UTC)

The package should have pkgconfig as a make dependency, it fails to compile otherwise

CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:707 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPkgConfig.cmake:873 (_pkg_check_modules_internal)
  audiodevs/PipeWire/CMakeLists.txt:5 (pkg_check_modules)

Jogging5055 commented on 2024-08-08 03:45 (UTC)

It looks like it had been updated, so I tried it again and was able to build it. Thank you!

Jogging5055 commented on 2024-08-06 16:28 (UTC)

I'm experiencing the same error as Lili1228.

cparish commented on 2024-08-05 16:06 (UTC)

I'm also having the same build issue as Lili1228 from a fully updated and clean build env. I don't immediately see anything wrong with the sources, but I know in the past GCC struggled with maybe-uninitialized false positives after unused paths were optimized out.

Omar007 commented on 2024-07-30 12:07 (UTC) (edited on 2024-07-30 12:19 (UTC) by Omar007)

A fully updated clean chroot? Before being pushed to the AUR this PKGBUILD has gone through 2 builds; one updated clean chroot on a native Arch Linux system as well as an Arch Linux container based build, of which neither failed 🤔

The message in @Lili1228's message seems to suggest the old hacky work-around I had in the PKGBUILD would still be needed but based on the above, it shouldn't be.

@Algebro's problem is something completely different and has nothing to do with the PKGBUILD. Idk what's going on there.

Kalinda commented on 2024-07-30 11:35 (UTC)

Am getting the same error as Lili1228 when I try to build. Doing it in a chroot.

1 2 3 4 5 6 .. 10 Next › Last »