Arch Linux User Repository

The current source tarball is rather old, I gather, and the latest package builds without encountering that same warnings treated as errors. Running a diff between the current (v4.1) and latest (v6.0) tarballs reveals a significant number of code changes in implementing the v4l2loopback_dc kernel module, which appears to be a custom and simplified modification of the official mainline v4l2loopback kernel module. Please find changes returning this package to working order here: https://github.com/jamesan-unofficial-aur-pkgs/droidcam/commit/5f2a2c27a871c86d23158369febf22e6ee2a7110. I also cleaned up the package in general and managed to: - eliminate patching of upstream code as target lines are no longer present; - remove conflict or dependency on v4l2loopback kernel module (i.e. it's unaffected by the presence of v4l2loopback-dkms); - added support for i686 architecture as its supported by a parallel package upstream; - eliminated all dependencies as the binary executables are statically linked (I suspect the gtk2 dependency is uneeded); - rearranged lines and separated the logic into the prepare(), build(), and package() functions. The entire set of changes can be found in a series of commits here: https://github.com/jamesan-unofficial-aur-pkgs/droidcam/commits/master with the repo located here: https://github.com/jamesan-unofficial-aur-pkgs/droidcam. There's no mechanism for pull/merge requests in the AUR, but I can push my commits into the repo if you add me as co-maintainer (or you can fork that repo of mine and DIY).

Sorry about not replying, I don't use this often but I do want to make sure it's at working haha. Let me know how it goes @jamesan. If anyone wants to test the prebuilt package I'll make it available on my website. I'll see if I can put a repo too.

I'm struggling with the identical error (exact log output as posted) posted by nipsky, which presents when compiling the v4l2loopback_dc kernel module as the last step in the package() function. I'm also using the CK patchset variant of the same kernel version as nipsky: 4.6.3-1-ck There's reference to droidcam's upstream build process fails at this kernel module for versions of the Linux kernel above 3.18/3.19. Let me see if this error vanishes if I boot up with a 3.xx kernel.

I get an error trying to build the package: make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/lib/modules/4.6.3-1-ARCH/build' CC [M] /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.o /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2331:30: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .vidioc_s_std = &vidioc_s_std, ^ /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2331:30: note: (near initialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_std’) /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2351:30: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .vidioc_s_audio = &vidioc_s_audio, ^ /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2351:30: note: (near initialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_audio’) /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2353:30: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .vidioc_s_audout = &vidioc_s_audout, ^ /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2353:30: note: (near initialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_audout’) cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:298: /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.o] Error 1 make[1]: *** [Makefile:1429: _module_/tmp/makepkg/droidcam/src/v4l2loopback] Error 2 make[1]: Leaving directory '/usr/lib/modules/4.6.3-1-ARCH/build' make: *** [Makefile:4: all] Error 2 ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build droidcam.

I get a "file or folder not found" window. clicking on ok will freeze the software. using 5.1 but writing here because discussion is here.

@AwesomeHaircut no package should ever modify anything in /home. Example configuration files belong in /usr/share. You should then add a message in a post_install() script about where to find an example config file.

@erikvanvelzen thanks it should be updated now. I didn't add the settings because aur packages shouldn't modify the ~ folder. I might be wrong though.

Below is a diff for droidcam 6.0 (version in AUR is currently 4.1) It also creates the file ~/.droidcam/settings I hope someone can update --- PKGBUILD_old 2015-10-28 12:00:33.036382004 +0100 +++ PKGBUILD 2015-11-15 02:24:08.440670180 +0100 @@ -1,11 +1,11 @@ # Maintainer: Daniel Nagy <danielnagy at gmx de> pkgname=droidcam -pkgver=4.1 -pkgrel=2 +pkgver=6.0 +pkgrel=3 _kver="`uname -r | cut -d"." -f1,2`-ARCH" pkgdesc='A tool for using your android device as a wireless/usb webcam' -arch=('i686' 'x86_64') +arch=('x86_64') url='http://www.dev47apps.com/' license=('custom') depends=( 'bluez-libs' 'gtk2') @@ -19,15 +19,12 @@ sha1sums=( 'f85b3f34f98908bd1327df0ea0e650dcbdcb07e9') -## as of 2013-10-29 these hash sums worked. But as of 2014-02-03 somethings changed and -## the new hash sums are listed below. -## [[ "${CARCH}" = "i686" ]] && _arch="x86" && sha1sums+=('64fad1b28169f1f5a3cdd03175fac5973fe5d0ef') -## [[ "${CARCH}" = "x86_64" ]] && _arch="x64" && sha1sums+=('982ecb2fb2c30adc2fb7f3a2c250ce65b5d40777') +## as of 2015-11-11 only x64 is available for droidcam version 6.0 +# [[ "${CARCH}" = "i686" ]] && _arch="x86" && sha1sums+=('5b00632275a2c09551d1c72703732150b1f685fe') +[[ "${CARCH}" = "x86_64" ]] && _arch="x64" && sha1sums+=('0c1d6c7b0298e5ec935aa1a93a80529d8a02c9a9') -[[ "${CARCH}" = "i686" ]] && _arch="x86" && sha1sums+=('5b00632275a2c09551d1c72703732150b1f685fe') -[[ "${CARCH}" = "x86_64" ]] && _arch="x64" && sha1sums+=('79166f6439a1bebfd83c8a1190cf67065c60951e') +source+=("http://files.dev47apps.net/600/droidcam-v4l2-${_arch}.tar.gz") -source+=("http://www.dev47apps.com/files/41/droidcam-v4l2-${_arch}.tar.gz") package() { # Install droidcam binary file @@ -60,4 +57,8 @@ _extramodules="extramodules-$(uname -r | cut -f-2 -d'.')-$(uname -r|sed -e 's/.*-//g')" MODPATH="${pkgdir}/usr/lib/modules/${_extramodules}/" install -Dm644 v4l2loopback-dc.ko "$MODPATH/v4l2loopback_dc.ko" + + # settings file + mkdir ~/.droidcam + touch ~/.droidcam/settings }

@laegnur (and others): you need the correct version of linux-*-headers (matching your kernel) installed to build the v4l2loopback module - for me it was linux-ck-k10-headers.

> this is problematic because some people might have v4l2loopback-dkms installed Can it be made that either v4l2loopback-dkms or v4l2loopback package is installed is fine? The preference could be whatever you choose.