-
-
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
io features related to pcap will be disabled #2651
Comments
How to resolve it? Here is an example for openni. You don't have to modify pcl cmake files. They just check and won't install it for you. More mature software will install it for you. Hence the problem could be either that you haven't install them or you don't specify the dynamic libraries in the linking stage. To install pcl with openni, do function install_pcl() {
# http://www.pointclouds.org/documentation/tutorials/installing_homebrew.php
brew install pcl
# https://github.com/totakke/homebrew-openni, homebrew/science has been discarded.
brew tap brewsci/science
brew tap toakke/openni
brew install openni
brew install sensor
brew install sensor-kinect
brew install nite
brew tap toakke/openni2
brew install openni2
brew install openni2-freenectdriver
}
To link it in the linking stage, add following definitions to a CXX compiler (clang based): ROOT="$( cd "$( dirname "${BASH_SOURCE[0]}" )/.." && pwd )"
echo ${ROOT}
args=(
"-DOPENNI_INCLUDE_DIRS=/usr/local/include/ni"
"-DOPENNI_INCLUDE_DIR=/usr/local/include/ni2"
)
cd "${ROOT}/build"
cmake .. ${args} |
@SQ-Duan Did you compile pcl yourself or are you using the version from from aptitude? If the ubuntu package wasn't compiled with pcap support you can't use that in your downstream project. The list of dependencies PCLConfig tries to find, is generated with what is used during the compilation of the library. |
@yiakwy I just add 2 funtions to find the libraries in file
And I using cmake to add PCL libraries to my project as blow:
|
@SergioRAgostinho I use cmake to add PCL libs to my project like this:
then |
Ok. Next step is to stop using 1.7 and giving a try at 1.9.1 to see if you still observe the same problem, when you compile the latest version, with pcap support. |
@SQ-Duan It might be operating system problems. Try to find library headers by hand. Try to find where apt install them. It might not be inside "/usr/local/include". Have a good luck! |
Closing due to inactivity. Please reopen if needed. |
I gave a try at 1.9.1 just now, and the same problem appeared:
Problem 1The warnings of pcap and png are caused by the lack of macro to find pcap and png. My solution is add some lines to find pcap and png in Problem 2And I found another problem: warning of libusb-1.0. This is caused by the line 318 |
Ubuntu 16.04, source install of libpcl1.9.1 A note on your "Problem 1": I used (note the second line is different from here, might be a typo):
and had to move file /usr/local/share/pcl-1.9/Modules/FindPcap.cmake to /usr/local/share/pcl-1.9/Modules/FindPCAP.cmake for it to work. I don't know how to solve "Problem 2" as I also have that warning. EDIT: while looking for a solution to the libusb issue I went in verbose mode, where:
They might be harmless, but still. For the first I used this workaround , but I can't do the same for the second as /usr/lib/python2.7/dist-packages/vtk doesn't exist. EDIT2: found this which reiterates the first workaround and solves the second issue as well. EDIT3: it works but isn't pretty
|
@aPonza for the Problem 1, I just copied the macro in FindPCAP.cmake to PCLConfig.cmake instead of moving the file FindPCAP.cmake. |
@aPonza For the problem 2, I deleted |
It's 2021 and I'm still getting these warnings when using PCL. Is there really no way of getting rid of these without manually fiddling with PCL's CMake config? Why doesn't it work by default? |
Which version of PCL? |
The version that comes with Ubuntu 20.04 these days. Output of
When building a program that uses PCL, I get these warnings:
Output of
|
Oh and it also gives these warnings lately:
This is probably related to this part of
Since Eigen does indeed ship with |
Do you use the latest version of perception_pcl? This commit should remove that warning (see also the commit message). |
After running |
If you have the latest released version of perception_pcl installed (1.7.2), the |
Output of
so it seems that I do indeed have the 1.7.1 version of |
Oh, you have multiple ROS distributions installed? So far you only mentioned Noetic. I guess then it depends on which distribution you source in your workspace. I am not sure whether the warning appears in the ROS2 versions of perception_pcl. |
I'm sorry, I probably didn't make this entirely clear. Only the packages which have |
I can also confirm that the warning still occurs on Ubuntu 20.04/ROS noetic even with
However, the warning message doesn't show on Ubuntu 18.04/ROS melodic with |
I had the same problem, with Ubuntu 20.04, ROS Noetic, pcl 1.10.1, and
I found a dirty solution. If you make sure these warnings cannot affect the functionality of your program, we can change this line in your find_package(PCL REQUIRED) to find_package(PCL REQUIRED QUIET) Because in here the code throw these warnings out: if(${LIB}_FOUND)
...
else()
if("${_is_optional}" STREQUAL "OPTIONAL")
list(APPEND PCL_${COMPONENT}_DEFINITIONS "-DDISABLE_${LIB}")
# HERE
pcl_message("** WARNING ** ${_component} features related to ${_lib} will be disabled")
... and the cmake macro ...
macro(pcl_message)
if(NOT PCL_FIND_QUIETLY)
message(${ARGN})
endif()
endmacro()
...
So just make However, this solution can not solve this problem actually. In ancient Chinese, we call it "hiding one's ears and stealing the bell (掩耳盗铃)". We still need a better solution. |
U may have a typo |
This is now fixed by commit bbbe9f8 (will be included in PCL 1.13.1) |
Environment
Context
When using
CMake
to create a project with PCL, the output is always showing that io features related to png will be disabled and io features related to pcap will be disabled.Reason
In file
PCLConfig.cmake.in
between line 432 and line 453, there is no function to findPCAP
, which causes the WARNING as above. It's same for the WARNING ofPNG
.The text was updated successfully, but these errors were encountered: