Fixes rosidl:
ImportError: No module named 'json'
ImportError: No module named 'em'
Fixes ros2:
ImportError: No module named 'xmlrpc'
ImportError: No module named 'pydoc'
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes rmw-fastrtps-cpp failure:
http://errors.yoctoproject.org/Errors/Details/174717/
DEBUG: Executing shell function do_compile
NOTE: VERBOSE=1 cmake --build TOPDIR/tmp-glibc/work/aarch64-oe-linux/rmw-fastrtps-cpp/git-r0/build --target all -- -j 9
ninja: error: 'TOPDIR/tmp-glibc/work/aarch64-oe-linux/fastrtps/git-r0/recipe-sysroot/usr/lib/libtinyxml2.so', needed by 'librmw_fastrtps_cpp.so', missing and no known rule to make it
WARNING: TOPDIR/tmp-glibc/work/aarch64-oe-linux/rmw-fastrtps-cpp/git-r0/temp/run.do_compile.13110:1 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build 'TOPDIR/tmp-glibc/work/aarch64-oe-linux/rmw-fastrtps-cpp/git-r0/build' "$@" -- -j 9'
ERROR: Function failed: do_compile (log file is located at TOPDIR/tmp-glibc/work/aarch64-oe-linux/rmw-fastrtps-cpp/git-r0/temp/log.do_compile.13110)
* it was caused by fastrtps's /usr/lib/fastrtps/cmake/fastrtpsTargets.cmake
containing the full path to libtinyxml2.so inside fastrtps's WORKDIR
which might be already removed by rm_work by the time when
rmw-fastrtps-cpp is being built
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* using AUTOREV causes undeterministic builds when it might start failing
even when nothing was changed in the metadata
* it also forces bitbake to run git ls-remote on the github repo every
single time when the recipe is parsed and fails to build when doing builds
without network access (from pre-populated premirror)
* hydro-devel branch wasn't updated for last 3 years and there are only 73
commits in it, so AUTOREV wasn't really useful anyway
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
| checking for bison... no
| configure: error: You need to install bison
| NOTE: The following config.log files may provide further information.
| NOTE: /data/cibot/deleteme/build/tmp-glibc/work/i586-oe-linux/sphinxbase/0.8-r0/build/config.log
* needed since oe-core change:
http://git.openembedded.org/openembedded-core/commit/?id=b7edc20cc2dd82989bd9561f860cb25478a40f69
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* meta-ros is compatible with Yocto 2.4 Rocko without any special
handling needed to integrate it, mark it as compatible
* LAYERSERIES_COMPAT variables are used only since 2.4 Rocko, so with
even older Yocto releases this isn't an issue, but with 2.4 it was
failing with:
bitbake -e zlib | tee env.zlib
ERROR: Unable to start bitbake server
which isn't really useful, bitbake-cookerdaemon.log shows better
explanation:
Traceback (most recent call last):
File "build-rocko/bitbake/lib/bb/cookerdata.py", line 285, in parseBaseConfiguration
self.data = self.parseConfigurationFiles(self.prefiles, self.postfiles)
File "build-rocko/bitbake/lib/bb/cookerdata.py", line 399, in parseConfigurationFiles
% (c, " ".join(layerseries), " ".join(compat)))
File "build-rocko/bitbake/lib/bb/__init__.py", line 104, in fatal
raise BBHandledException()
bb.BBHandledException
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "build-rocko/bitbake/lib/bb/daemonize.py", line 77, in createDaemon
function()
File "build-rocko/bitbake/lib/bb/server/process.py", line 433, in _startServer
self.cooker = bb.cooker.BBCooker(self.configuration, self.featureset)
File "build-rocko/bitbake/lib/bb/cooker.py", line 197, in __init__
self.initConfigurationData()
File "build-rocko/bitbake/lib/bb/cooker.py", line 356, in initConfigurationData
self.databuilder.parseBaseConfiguration()
File "build-rocko/bitbake/lib/bb/cookerdata.py", line 318, in parseBaseConfiguration
raise bb.BBHandledException
bb.BBHandledException
ERROR: Layer ros-layer is not compatible with the core layer which only supports these series: rocko (layer is compatible with sumo)
* and it's a bit complicated to override LAYERSERIES_COMPAT_ros-layer
from local build without meta-ros modification, changing it in some
other (own) layer, which is parsed after meta-ros works, but you might
not have suitable layer for this.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
rospkg is necessary to generate dreconf files. dynamic-reconfigure was not
providing proper build-time depencency to packages that use it.
This patch series adds ${PYTHON_PN}-roskpg to DEPENDS of dynamic-reconfigure.bb
and removes unnecessary reference to it in all recipes that are using dynamic-reconfigure.
There were a fix for theora-image-transport with missing libvorbis as well.
[modified commit message header.]
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
The initial commit from Johannes Schrimpf provided the geographiclib
recipe in recipes-ros. The general policy is to only have ROS
packages in recipes-ros, i.e., packages that are tracked and updated
in the rosdistro/distribution.yaml file.
Hence, I then moved the geographiclib recipe to recipes-extended,
as it is a supporting library, not a ROS package.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
* fixes:
ERROR: moveit-ros-planning-0.7.13-r0 do_package_qa: QA Issue: /opt/ros/indigo/lib/libmoveit_planning_scene_monitor.so.0.7.3 contained in package moveit-ros-planning requires libtf_conversions.so()(64bit), but no providers found in RDEPENDS_moveit-ros-planning? [file-rdeps]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
[lukas.bulwahn@gmail.com: include reference to meta-ros issue tracker]
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
This commit also drops a patch for socketcan-interface that is now
included in the updated version.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Andre Goddard Rosa