-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Pcl 1.11.1 #59146
Pcl 1.11.1 #59146
Conversation
Please also update the test to catch the boost issues. |
63ee8cc
to
73b22b4
Compare
Errors building test program on 10.14 and 10.15:
|
PCL's CI has been bitten by this issue a couple of times. In the current CI setup we were forced to settle for command-line tools. I'm unsure of homebrew's CI infrastructure but keep it in mind. A juicy list of user reports of the same problem can be found at PointCloudLibrary/pcl#2601 |
Including |
@dtrodrigues CMake is not picking up on the command line tools. It's using XCode's Toolchain. My suspicion is that the command line tools are not present in the path you're specifying to CMake. |
This is possibly related to Homebrew/brew#7426 . Looking at a smaller example like the Compared to #52532, this is a case where we want to use the CLT vs the sdk. @Bo98 do you have any ideas? |
The problematic flag is likely This is likely a problem in a pkg-config file or CMake module of PCL or one of its dependencies. |
I'm not really sure where to go from here. One part that puzzles me is that the library and some executables appear to build successfully during the The currently available Homebrew Based on the comment from @Bo98, this may be an upstream issue with PCL or one of its dependencies, so we're kind of stuck until that is resolved. |
It's possibly because of the superenv's heroic work to make a fundamentally broken build somehow work.
I think it's a VTK bug. I can have a look but it might be a day or two before I manage to. |
Change target to PCL 1.11.1? |
c98f224
to
5f4e91c
Compare
Formula/pcl.rb
Outdated
-DBUILD_simulation:BOOL=AUTO_OFF | ||
-DBUILD_simulation:BOOL=OFF | ||
-DWITH_CUDA:BOOL=OFF | ||
-DWITH_DOCS:BOOL=OFF | ||
-DWITH_OPENGL:BOOL=OFF |
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.
You might be able to enable these again now. We merged some last minute fixes after realizing that OpenGL is still being shipped in Catalina.
@@ -13,39 +12,34 @@ class Pcl < Formula | |||
sha256 "d14889b636e81d1427a7d0300c028b571ac038e54b3760eba8900a7175d210c1" => :high_sierra | |||
end | |||
|
|||
depends_on "cmake" => :build | |||
depends_on "cmake" => [:build, :test] | |||
depends_on "pkg-config" => :build | |||
depends_on "boost" | |||
depends_on "cminpack" |
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.
This is no longer needed
depends_on "pkg-config" => :build | ||
depends_on "boost" | ||
depends_on "cminpack" | ||
depends_on "eigen" | ||
depends_on "flann" | ||
depends_on "glew" |
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.
This is needed again.
This is our current CI build pipeline in macos using homebrew. I can submit a PR later against your branch with the changes. |
@SergioRAgostinho do you want to submit a new PR directly against |
Sure. |
5f4e91c
to
8996041
Compare
@Bo98 you were right --
After merging #60380 and rebasing on top of that, this PR should pass CI. |
8996041
to
7e08ace
Compare
With the fix for vtk now in place, this should be good to go. |
🤖 A scheduled task has triggered a merge. |
brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingbrew install <formula>
)?cc @SergioRAgostinho, previous attempt at #54706
Shim issue should be resolved by #56273
Should resolve Boost 1.73 issue in #59064