conda-forge / pcl-feedstock

A conda-smithy repository for pcl.

About pcl-feedstock

Feedstock license: BSD-3-Clause

Home: http://www.pointclouds.org

Package license: BSD-3-Clause

Summary: Point Cloud Library (PCL)

Development: https://github.com/pointcloudlibrary/pcl

Documentation: http://www.pointclouds.org

The Point Cloud Library (PCL) is a standalone, large scale, open project for 2D/3D image and point cloud processing.

Current build status

Azure

Variant Status linux_64 linux_aarch64 linux_ppc64le osx_64 osx_arm64 win_64

Current release info

Name	Downloads	Version	Platforms

Installing pcl

Installing pcl from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, pcl can be installed with conda:

conda install pcl

or with mamba:

mamba install pcl

It is possible to list all of the versions of pcl available on your platform with conda:

conda search pcl --channel conda-forge

or with mamba:

mamba search pcl --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search pcl --channel conda-forge

# List packages depending on `pcl`:
mamba repoquery whoneeds pcl --channel conda-forge

# List dependencies of `pcl`:
mamba repoquery depends pcl --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating pcl-feedstock

If you would like to improve the pcl recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/pcl-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @Tobias-Fischer
• @chambbj
• @hobu

pcl-feedstock's Issues

Could you give some tutorials about how to use this

Comment:

Hello, it is my first time to use conda-forge, and I notice I could't import pcl in my python script after I install it.
And I check out the env folder where it was installed, I found files about pcl just in those folders bin, include, and share not in site-packages.
So, I think this is the reason why I could not import it.
Could you give some tutorials about how to use this, Thanks!

Why is ppc64le disabled?

Is there a specific technical reason for not enabling ppc64le for this feedstock?

Thanks!

OSX build on CircleCI failing

Upon merge of #1, the OSX build on CircleCI now ends in

Traceback (most recent call last):
  File "/Users/distiller/miniconda3/bin/upload_or_check_non_existence", line 131, in <module>
    main()
  File "/Users/distiller/miniconda3/bin/upload_or_check_non_existence", line 121, in main
    upload(cli, fname, owner, channel)
  File "/Users/distiller/miniconda3/bin/upload_or_check_non_existence", line 68, in upload
    env=os.environ)
  File "/Users/distiller/miniconda3/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['anaconda', '--quiet', '-t', '/var/folders/ms/xg67k5sn16xc7sdr_w3q45840000gn/T/tmp610nchy8/binstar.token', 'upload', '/Users/distiller/miniconda3/conda-bld/osx-64/pcl-1.8.1-h386bb81_1.tar.bz2', '--user=conda-forge', '--channel=main']' returned non-zero exit status 1.
Exited with code 1

Not sure I follow. I do see a similar issue raised at conda-forge/conda-forge-ci-setup-feedstock#12, but the build number was bumped and recipe rerendered in the PR, so it seems that couldn't be the issue.

Could use some help from @conda-forge/core. Thanks!

[warning] failed package validation and/or copy for commit a4ee540f99916869cf065206b112048abe008a4e

Hi @conda-forge/pcl! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.

error messages:

• invalid feedstock token

PCL 0.14.0 missing for windows

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

There was a post merge build: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=852572&view=logs&jobId=a70f640f-cc53-5cd3-6cdc-236a1aa90802&j=a70f640f-cc53-5cd3-6cdc-236a1aa90802&t=6119ccbe-9301-594f-7c27-f792b80a7fcc

Installed packages

.

Environment info

.

Allow variant for headless use without GUI support

Currently PCL is depending on VTK and a bunch of other GUI libraries. For a lot of robotic applications this isn't used since PCL is used without visualization and simply used as an embedded library. Depending on GUI libraries is causing a huge number of other packages to be installed that aren't necessary.

Regression: qhull not found

For some reason, in recent builds that pull in qhull 2020.2, we get

-- Could NOT find Qhull (missing: QHULL_LIBRARIES QHULL_INCLUDE_DIRS) 

whereas previously with qhull 2019.1, we got

-- Found Qhull: optimized;$PREFIX/lib/libqhull_p.so;debug;$PREFIX/lib/libqhull_p.so  
-- QHULL found (include: $PREFIX/include, lib: optimized;$PREFIX/lib/libqhull_p.so;debug;$PREFIX/lib/libqhull_p.so)

So probably there's an issue with the new version of qhull. Should we pin to the old version until we figure out what's wrong there? The issue is that certain header files (e.g. convex_hull.h) are not being created at the moment.

/cc @wolfv @conda-forge/qhull

@conda-forge-admin, please rerender

Additional comment:

No response

rerendering

@conda-forge-admin please rerender