-
Notifications
You must be signed in to change notification settings - Fork 249
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
error building PCL with cmake_external #49
Comments
Note that the use of -DBUILD_WITH_OPENMP has no effect |
Hi Brian, there was two problems with the build:
A note on binding dependencies - different variables need to be set to help finding the prebuild libraries. |
Thank you very much for your all your help I'm not able to build some of the libraries in #59. For example, running
results in the following error (on Ubuntu):
|
This seems to be unrelated, building pybind11 fails with the same error (had it working recently). I imagine this is could either be from building bazel at a later commit, or from downloading rules_foreign_cc at a later commit. |
So this one is actually a bit weird and seems similar to bazelbuild/bazel#3184. When I bazel build :openblas I get the following error:
|
From the first error that you posted, you seem to be missing CMake on Ubuntu: /bin/bash: line 23: cmake: command not found. Can not say anything about libtool error, I am not calling it directly, there must come from the script. |
ack - I switched over to Ubuntu. added all other necessary dependencies to pcl target (I think) and am now getting the following:
|
Looks like EIGEN_INCLUDE_DIR should be EIGEN_INCLUDE_DIRS (same for FLANN_INCLUDE_DIR) after making that change, build fails later in the process, with the following:
|
|
I had missed one package (OPENNI). The build is not failing but has been running for ~40 minutes. I'll wait for a few hours and see if it completes. |
Build completely successfully in ~1 hour. The final rule looks like this:
|
One last qq - outputs are located under:
When they should be at
e.g. I want to strip |
Great news! though, an hour seems to be really long. Do you want to create a pull request to contribute this to the examples? About the include directory - there is the attribute I added the example into examples/cmake_hello_world_lib/BUILD: In case when we do not pass the custom out_include_dir, we need to include header with #include "version123/hello.h". |
Thank you so very much for your help! I will submit a PR, probably on Monday. I also got an error about not being able to find file Python.h. I resolved this by adding copts=["-I/path_to_system_python"]. Would you happen to know a way of resolving this issue without introducing local dependencies? I now get the following error when building my cc_binary:
Appreciate any insight, my knowledge of building C++ is pretty minimal unfortunately. Thanks again! |
I just took a guess and removed libflann_cpp_s.a from the static_libraries param of flann cmake_external target, and it worked! I don't understand the broader implications of this change so if there's anything I am missing would very much appreciate your guidance. Otherwise, I'll submit a PR on Monday with the full example and close this issue at the time. Thanks again! |
Ok, looking forward for a pull request!
Well, this file should be provided since it is needed by a build.
As far as I could understand from Flann's CMake files, flann_s.a and flann_cpp_s.a are variants for C or C++. So you definitely need only one of them. (It's here) |
ERROR:
System:
BUILD:
WORKSPACE:
The text was updated successfully, but these errors were encountered: