Though not a dependency per se, don’t forget that you also need the CMake build system, at least version 2.8.3. Additional help on how to use the CMake build system is available on our tutorials page.
Please note that the following installation instructions are only valid for POSIX systems (e.g., Linux, MacOS) with an already installed make/gnu toolchain. For instructions on how to download and compile PCL in Windows (which uses a slightly different process), please visit our tutorials page.
For systems for which we do not offer precompiled binaries, you need to compile Point Cloud Library (PCL) from source. Here are the steps that you need to take:
tar xvfj PCL-1.6.0-Source.tar.bz2
cd PCL-1.6.0-Source && mkdir build && cd build
cmake ..Or change them:
ccmake ..Please note that cmake might default to a debug build. If you want to compile a release build of PCL with enhanced compiler optimizations, you can change the build target to "Release" with "-DCMAKE_BUILD_TYPE=Release".
cmake -DCMAKE_BUILD_TYPE=Release ..
makeAnd install the result:
make installor alternatively, if you did not change the CMAKE_INSTALL_PREFIX variable which declares where PCL should be installed, do:
sudo make install
cd PCL-1.6.0 && mkdir build && cd build cmake -DCMAKE_BUILD_TYPE=Release .. make sudo make installAgain, for a detailed tutorial on how to compile and install PCL and its dependencies in Microsoft Windows, please visit our tutorials page. Additional information for developers is available at the Github PCL Wiki.
If you are eager to try out a certain feature of PCL that is currently under development (or you plan on developing and contributing to PCL), we recommend you try checking out our source repository, as shown below. If you're just interested in browsing our source code, you can do so by visiting https://github.com/PointCloudLibrary/pcl.
git clone https://github.com/PointCloudLibrary/pcl pcl-trunkPlease note that above steps (3-5) are almost identical for compiling the experimental PCL trunk code:
cd pcl-trunk && mkdir build && cd build cmake -DCMAKE_BUILD_TYPE=Release .. make sudo make install
Because PCL is split into a list of code libraries, the list of dependencies differs based on what you need to compile. The difference between mandatory and optional dependencies, is that a mandatory dependency is required in order for that particular PCL library to compile and function, while an optional dependency disables certain functionality within a PCL library but compiles the rest of the library that does not require the dependency.
pcl_* denotes all PCL libraries, meaning that the particular dependency is a strict requirement for the usage of anything in PCL.
The following code libraries are required for the compilation and usage of the PCL libraries shown below:
The following code libraries enable certain additional features for the PCL libraries shown below, and are thus optional: