-
Notifications
You must be signed in to change notification settings - Fork 2.2k
pcl/fix with_openmp and with_opencv options not being applied #28991
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
base: master
Are you sure you want to change the base?
Conversation
thanks @trns1997 - could you provide logs both before and after the proposed changes so that we can verify this? thanks! |
Sorry it took me a while. Here are the logs you requested. This class prints a warning when OpenMP is not available, and prints nothing when OpenMP is enabled. Case 1:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove before merge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove before merge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove before merge
Summary
Changes to recipe: recipes/pcl/1.14.x
Closes #28985
Motivation
The
with_openmpandwith_opencvoptions for thepclpackage are not being applied when set viaconanfile.txt. Even when explicitly enabling these options, the resulting PCL build behaves as if they are disabled.Details
Options such as:
are ignored during configuration. CMake output confirms that OpenMP and OpenCV support are not enabled, and PCL prints warnings during configuration indicating that OpenMP is disabled.
This change aims to ensure that the option values passed from profiles or conanfile.txt are properly forwarded to the build system and not overwritten in recipe logic (e.g. config_options, configure, or CMake toolchain integration).
Additionally, I discovered that although with_opencv defaults to True in the recipe, OpenCV is never actually enabled nor installed because the current CMake option propagation and dependency checks prevent the condition from ever being met. So even when explicitly enabling with_opencv, the build proceeds without OpenCV support, making the default value misleading and ineffective. Maybe we should consider simplifying this mechanism to prevent confusion?
Add a 👍 reaction to pull requests you find important to help the team prioritize, thanks!