-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boost cmake configuration issue on macOS Monterey (PCL Installation) #6225
Comments
Hi, just to be sure: Does the file BoostConfig.cmake exist on your computer? |
Thank you for your response! If you run sudo port install boost, it defaults to installing Boost 1.76, not Boost 1.87 as you mentioned. Here's an example of what you might see:
But even if i install specifically boost187 the error still persist:
The BoostConfig.cmake is present for boost187 but not for the default 176. |
Okay, that is good. BoostConfig.cmake is definitely required. |
I just commented on this macports ticket and proposed a solution: https://trac.macports.org/ticket/71871 |
Description
I encountered an issue while installing and configuring PCL on macOS Monterey (M1) using the procedure described in the official documentation "Compiling PCL and its dependencies from MacPorts and source on Mac OS X". The problem arose due to a failure to locate Boost despite it being installed via MacPorts. The issue seems related to the BoostConfig.cmake file and the paths not being correctly set.
Environment
OS: macOS Monterey (12.6.5)
Boost Version: 1.71.0 (installed via MacPorts)
PCL Version: [6b93e78 master]
CMake Version: [3.31.3]
Steps to Reproduce
Just follow the installation steps provided in the PCL documentation.
Error message
Actual Behavior
CMake fails to locate the BoostConfig.cmake file because the default search paths do not include the MacPorts Boost directory (/opt/local/libexec/boost/1.71/lib/cmake/Boost-1.71.0).
Resolution
I resolved the issue by explicitly setting Boost_DIR and other Boost-related paths in the CMakeLists.txt. Here's what I added:
The text was updated successfully, but these errors were encountered: