ecto_openni fails to build against ecto on ARM
trainman419 opened this issue · 7 comments
Full build log: http://packages.namniart.com:8080/view/IbinT/job/ros-indigo-ecto-openni_binarydeb_trusty_armhf/1/console
It looks like ecto isn't exporting include directories properly:
CMake Error at /opt/ros/indigo/share/ecto/cmake/ectoConfig.cmake:106 (message):
Project 'ecto' specifies
'/tmp/buildd/ros-indigo-ecto-0.6.4-0trusty-20140805-1659/include' as an
include dir, which is not found. It does neither exist as an absolute
directory nor in
'/tmp/buildd/ros-indigo-ecto-0.6.4-0trusty-20140805-1659//tmp/buildd/ros-indigo-ecto-0.6.4-0trusty-20140805-1659/include'.
Ask the maintainer 'Vincent Rabaud <vincent.rabaud@gmail.com>' to fix it.
Call Stack (most recent call first):
/opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:75 (find_package)
CMakeLists.txt:5 (find_package)
This also caused ecto_ros and ecto_opencv to fail to build on armhf.
damn, I still do not get that bug: it's been happening since Groovy (but I have not seen it on Indigo).
Just re-trigger the ecto job and it should work again. Somehow, once in a while, it thinks it is in devel space and not install space ......
The full build log from the offending build of ecto is here if it helps: http://packages.namniart.com:8080/view/IbinT/job/ros-indigo-ecto_binarydeb_trusty_armhf/1/consoleFull
In the meantime I'll retrigger the ecto build and see if that fixes the downstream packages.
A second build of ecto doesn't seem to have fixed the problem.
At least it's consistent?
Thanks! I've pushed the most recently released versions of ecto and ecto_ros to my build farm, and I'll let you know how it goes.
Success! ecto_openni built against the new version of ecto.
Bouya ! Took two years to fix that stupid bug ...... It was so trivial ...