Package Details: pcl 1.15.0-1

Git Clone URL: https://aur.archlinux.org/pcl.git (read-only, click to copy)
Package Base: pcl
Description: A standalone, large scale, open project for 2D/3D image and point cloud processing
Upstream URL: https://www.pointclouds.org
Licenses: BSD-3-Clause
Submitter: None
Maintainer: kino_t
Last Packager: kino_t
Votes: 49
Popularity: 0.000093
First Submitted: 2011-04-05 03:39 (UTC)
Last Updated: 2025-02-22 18:38 (UTC)

Pinned Comments

kino_t commented on 2023-02-18 14:49 (UTC) (edited on 2023-02-19 01:24 (UTC) by kino_t)

Binary of pcl is now available: https://github.com/arch4edu/arch4edu

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 24 Next › Last »

dobedobedo commented on 2022-01-22 13:27 (UTC)

I can confirm that adding

liblas adios2 utf8cpp freeglut ospray python-mpi4py openvr cgns unixodbc

as dependencies by editing PKGBUILD makes the compilation work.

chiossif commented on 2022-01-20 08:15 (UTC)

I had to install these: liblas adios2 utf8cpp freeglut ospray python-mpi4py openvr cgns unixodbc in order to start makepkg. Please consider adding them as dependencies.

Although at 71%: "No rule to make target '/usr/lib/jvm/default/lib/libjawt.so', needed by " a few bins.

Hope all these help. TY :-)

ngoonee commented on 2022-01-20 01:49 (UTC)

@leuko thanks, but I already have both installed

@blurgy my errors start with warnings about not providing Findospray.cmake, but the actual errors start after configure, starts off with this. Linking /include doesn't help.

CMake Error at cmake/pcl_targets.cmake:306 (add_executable): Target "pcl_mesh2pcd" links to target "ospray::ospray" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Call Stack (most recent call first): tools/CMakeLists.txt:246 (PCL_ADD_EXECUTABLE)

leuko commented on 2022-01-19 16:42 (UTC)

I installed the version 1.12.1, but had to add the following optional dependencies of vtk:

  • fmt
  • pugixml

These are also listed as deps in pcl-git, so it would be great if they are listed as dependencies.

Regarding previous comments: I did not have any problem regarding OSPRay.

blurgy commented on 2022-01-18 07:49 (UTC)

@ngoonee The error in my previous comment says that it could not find OSPRay headers from /include, which OSPRay determines this by assuming / to be its installation prefix (from line 68 of /usr/lib/cmake/ospray-2.8.0/osprayConfig.cmake), so symlinking /usr/include to /include should have solved the error mentioned in my previous comment. Since ospray is not listed as a dependency for pcl in this PKGBUILD, are you sure you have OSPRay installed? And what is your build error specifically?

ngoonee commented on 2022-01-15 09:32 (UTC)

@blurgy doesn't seem to work for me, no change in build errors

blurgy commented on 2022-01-06 08:47 (UTC) (edited on 2022-01-06 08:48 (UTC) by blurgy)

For those having troubles with cmake saying fail to find OSPRay headers, like:

CMake Error at /lib64/cmake/ospray-2.8.0/osprayConfig.cmake:26 (message):
  Failed to find OSPRay - OSPRay install root: /, determined from relative
  path from osprayConfg.cmake install location: /lib64/cmake/ospray-2.8.0,
  does not contain OSPRay headers.  Either the install directory was deleted,
  or the install tree was only partially relocated outside of CMake after
  OSPRay was built.
Call Stack (most recent call first):
  /lib64/cmake/ospray-2.8.0/osprayConfig.cmake:69 (ospray_report_not_found)
  /lib64/cmake/vtk/VTK-vtk-module-find-packages.cmake:209 (find_package)
  /lib64/cmake/vtk/vtk-config.cmake:150 (include)
  cmake/pcl_find_vtk.cmake:25 (find_package)
  CMakeLists.txt:379 (include)

A temporary workaround is to create a symlink at /include to point to /usr/include:

# cd / && ln -s usr/include

It is a problem due to OSPRay determining a wrong installation directory on Arch Linux systems, see this issue: ospray/ospray#511.

CromFr commented on 2022-01-04 08:45 (UTC) (edited on 2022-01-04 08:46 (UTC) by CromFr)

I had some issues re-building PCL after upgrading my system (including boost 1.78). Installing the following dependencies fixed the issue:

  • community/liblas
  • community/adios2
  • community/utf8cpp
  • extra/jdk-openjdk

I'm not sure why those packages are now required, I already built PCL a month ago without any issue... (maybe PCL is falling back to those libraries if some parts of boost are unavailable?)

roachsinai commented on 2022-01-04 01:09 (UTC)

@mrwsl thanks a lot! I'll have a try!

mrwsl commented on 2022-01-03 09:17 (UTC)

@roachsinai: check your dmesg. I had the same error triggered by oom-kill. I reduced the cores to avoid high memory usage.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 24 Next › Last »