fspindle
commented
11 years ago I have changed visp-config file, the one that is installed by "make install", by removing the usage of pkg-config. I don't know if the changes will introduce an issue with the Debian multi-arch support. I don't think so, but we have to keep that in mind.
Fabien
Hi Thomas,
When I build vision_visp\visp package with ViSP 2.7.1 release candidate, other packages are unable to find visp headers and libraries.
$ rosmake visp ok $ rosmake visp_tracker Building CXX object CMakeFiles/visp_tracker.dir/src/libvisp_tracker/tracker.o /home/fspindle/fuerte_workspace/vision_visp/visp_tracker/src/libvisp_tracker/conversion.cpp:14:26: fatal error: visp/vpImage.h: No such file or directory compilation terminated.
The issue is in relation with the changes done in visp-config that uses now pkg-config visp --cflags. In our case visp.pc is not in PKG_CONFIG_PATH environment variable: $ pkg-config visp --cflags No package 'visp' found
To reproduce the error, edit vision_visp/visp/Makefile and put
VERSION = 2.7.1-rc1 TARBALL = build/ViSP-$(VERSION).tar.gz TARBALL_URL = \ https://gforge.inria.fr/frs/download.php/32728/ViSP-2.7.1-rc1.zip UNPACK_CMD = unzip SOURCE_DIR = build/ViSP-$(VERSION)
MD5SUM_FILE = ViSP-$(VERSION).tar.gz.md5sum
roscd visp make wipe rosdep install visp rosmake visp
A workaround is to set PKG_CONFIG_PATH (in my case) export PKG_CONFIG_PATH=$HOME/fuerte_workspace/vision_visp/visp/install/lib/pkgconfig
then remove visp_tracker/build folder and run a rosmake vision_visp
I don't know how to fix properly this issue. I can revert the changes done in visp-config, but I don't think that it is the best solution.
Any ideas ?
Fabien