Package Details: droidcam 6.0-8

Git Clone URL: https://aur.archlinux.org/droidcam.git (read-only)
Package Base: droidcam
Description: A tool for using your android device as a wireless/usb webcam
Upstream URL: https://www.dev47apps.com/droidcam/linuxx
Licenses: custom
Submitter: marquicus
Maintainer: AwesomeHaircut (jamesan)
Last Packager: AwesomeHaircut
Votes: 46
Popularity: 0.616970
First Submitted: 2011-06-29 20:31
Last Updated: 2016-07-27 21:48

Latest Comments

AwesomeHaircut commented on 2016-09-09 16:13

You need to make sure you have the headers for the kernel you're currently running. Make sure 'pacman -Q linux' --add -lts or-ck if appropriate --and
'uname -r' show the same version. If you just upgraded reboot.

JohnnyDeacon commented on 2016-09-09 03:37

==> Starting build()...
make -C /lib/modules/`uname -r`/build M=`pwd`
make[1]: Entering directory '/usr/lib/modules/4.7.2-1-MANJARO/build'
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory '/usr/lib/modules/4.7.2-1-MANJARO/build'
make: *** [Makefile:4: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
:: failed to build droidcam package(s)

AwesomeHaircut commented on 2016-07-21 05:12

Thanks a lot for that Jame San! I made you a co maintainer and you can update changes. I'll merge them first thing in the morning; unless you're a bit faster than me haha

jamesan commented on 2016-07-12 22:25

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).

AwesomeHaircut commented on 2016-07-06 21:29

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.

jamesan commented on 2016-07-05 08:02

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.

nipsky commented on 2016-07-01 20:14

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.

capoeira commented on 2016-04-30 22:26

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.

djmattyg007 commented on 2016-04-09 00:14

@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.

AwesomeHaircut commented on 2016-03-09 18:57

@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.

All comments