Package Details: python-pyrealsense2-git v2.38.1-1

Git Clone URL: https://aur.archlinux.org/librealsense-git.git (read-only, click to copy)
Package Base: librealsense-git
Description: Intel® RealSense™ SDK 2.0 is a cross-platform library for Intel® RealSense™ depth cameras (D400 series and the SR300)
Upstream URL: https://github.com/IntelRealSense/librealsense
Licenses: Apache
Conflicts: python-pyrealsense2
Provides: python-pyrealsense2
Submitter: otaj
Maintainer: zhou13
Last Packager: zhou13
Votes: 1
Popularity: 0.000000
First Submitted: 2019-04-18 07:52 (UTC)
Last Updated: 2020-09-27 02:12 (UTC)

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

zhou13 commented on 2020-09-27 02:12 (UTC)

It should be fixed now.

nikisalli commented on 2020-09-27 00:27 (UTC)

the current version does not build; appending the -f flag at the rm at line 50 worked for me

lubosz commented on 2020-09-25 09:31 (UTC) (edited on 2020-09-25 09:31 (UTC) by lubosz)

The build currently fails with:

find: cannot delete ‘/home/jessi/.cache/yay/librealsense-git/pkg/librealsense-git/usr/lib/python3.8’: Directory not empty

The problem is how the python package is split out.

This patch solves it for me:

diff --git a/PKGBUILD b/PKGBUILD
index 03c14e3..d6cf6f0 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,7 +5,7 @@
 pkgbase=librealsense-git
 pkgname=(librealsense-git python-pyrealsense2-git)
 _pkgname=librealsense
-pkgver=v2.33.1
+pkgver=v2.38.1
 pkgrel=1
 pkgdesc="Intel® RealSense™ SDK 2.0 is a cross-platform library for Intel® RealSense™ depth cameras (D400 series and the SR300)"
 arch=('x86_64')
@@ -47,7 +47,8 @@ package_librealsense-git() {
   conflicts=('librealsense')
   cd "${srcdir}/${_pkgname}/build"
   DESTDIR="${pkgdir}" make install
-  find ${pkgdir}/usr/lib -name "py*" -delete
+  find ${pkgdir}/usr/lib -name "py*.so" -delete
   cd "${srcdir}/${_pkgname}/config"
   sed -i 's/plugdev/video/g' 99-realsense-libusb.rules
   install -Dm644 99-realsense-libusb.rules "${pkgdir}/etc/udev/rules.d/99-realsense-libusb.rules"

otaj commented on 2020-03-14 11:25 (UTC)

Package disowned

zhou13 commented on 2020-03-14 08:27 (UTC)

I am glad to maintain this package. Feel free to orphan it.

otaj commented on 2020-03-12 08:50 (UTC)

You can change the PKGBUILD for yourself. I generally don't like building examples in provided PKGBUILDs, because it can clutter the package (17M with examples vs 12M without).

However, I switched jobs since I created this package and don't have access to realsense sensor anymore, so if anyone wants to maintain this package, that would be great.

zhou13 commented on 2020-03-12 06:16 (UTC)

Could you add DBUILD_EXAMPLES=true? Those examples are useful for everyday work.

otaj commented on 2020-02-27 09:23 (UTC) (edited on 2020-03-12 08:50 (UTC) by otaj)

Do you have another Python version installed? I just built it in clean chroot without any problems. On the other hand, when I tried to rebuild it after I installed python37 before, it picked up Python3.7 first.

jerry73204 commented on 2020-02-26 17:17 (UTC)

It failed to build on my laptop due to wrong Python version. Please include this patch to fix this issue.

diff --git a/wrappers/python/third_party/pybind11/tools/pybind11Tools.cmake b/wrappers/python/third_party/pybind11/tools/pybind11Tools.cmake
index a7c471a07..e5f627e5b 100644
--- a/wrappers/python/third_party/pybind11/tools/pybind11Tools.cmake
+++ b/wrappers/python/third_party/pybind11/tools/pybind11Tools.cmake
@@ -12,7 +12,7 @@ if(NOT PYBIND11_PYTHON_VERSION)
   set(PYBIND11_PYTHON_VERSION "" CACHE STRING "Python version to use for compiling modules")
 endif()

-set(Python_ADDITIONAL_VERSIONS 3.7 3.6 3.5 3.4)
+set(Python_ADDITIONAL_VERSIONS 3.8 3.7 3.6 3.5 3.4)
 find_package(PythonLibsNew ${PYBIND11_PYTHON_VERSION} REQUIRED)

 include(CheckCXXCompilerFlag)

To include it in PKGBUILD,

prepare() {
  cd "${srcdir}/${_pkgname}"
  patch -Np1 < "${srcdir}/python-version.patch"
}

otaj commented on 2019-05-13 09:53 (UTC)

Well, that means, that the package is most likely fine (and you can install it now), however, I am not too sure whether that is a good message for you, because it means the symptoms you had before point to something messed up with the rest of your system. My main guess would be either python-setuptools or the whole python in general. Try to reinstall those and let me know how it goes afterwards.

Btw, is your system up-to-date?

1 2 Next › Last »