As ar-track-alvar has been repaired, we can add this recipe back
to packagegroup-ros-world.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
ar_track_alvar 0.5.x only support opencv2, whereas meta-oe provides
opencv3. The ar_track_alvar kinectic versions 0.6.x also support
opencv3, as pointed out in the comment of commit e82747c4 [1].
Therefore, this commit updates ar-track-alvar to version 0.6.1
to resolve#397.
[1] e82747c42d.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
bitbake diagnostic-aggregrator failed due to missing build
dependencies with:
```
| -- Could not find the required component 'bondcpp'. The following CMake error indicates that you either need to install the package with the same name or change your environment so that it can be found.
| CMake Error at /home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/sysroots/qemux86/opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:83 (find_package):
| Could not find a package configuration file provided by "bondcpp" with any
| of the following names:
|
| bondcppConfig.cmake
| bondcpp-config.cmake
|
| Add the installation prefix of "bondcpp" to CMAKE_PREFIX_PATH or set
| "bondcpp_DIR" to a directory containing one of the above files. If
| "bondcpp" provides a separate development package or SDK, be sure it has
| been installed.
| Call Stack (most recent call first):
| CMakeLists.txt:6 (find_package)
|
|
| -- Configuring incomplete, errors occurred!
```
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
Compiling rosconsole failed with:
```
[...]/ros_comm-1.11.20/tools/rosconsole/include/ros/console.h:121:14: error: 'vector' in namespace 'std' does not name a template type
typedef std::vector<TokenPtr> V_Token;
```
The console.h assumed that vector is included already by one of its
dependencies. This bold assumption has been uncovered by the update
of the boost library to version 1.62.0 [1, 2] in openembedded-core
repository.
Coincidently, this issue was also noticed by ROS users on Gentoo and
Arch Linux, which probably also use the latest boost library and gcc6,
and they opened pull requests on the indigo and kinetic branches [3, 4, 5]
with commits to address the issue. The patch in the kinetic branch has
been merged, the others to the indigo branch have been rejected as the
ros-comm maintainers intend to simply backport the patch from the
kinetic branch for the next release.
This commit applies the patch merged in the kinetic branch in our
recipe for the current indigo release version.
[1] http://cgit.openembedded.org/openembedded-core/commit/?id=c31030d87cd1741a4186d711325b8eab9c70b327
[2] http://cgit.openembedded.org/openembedded-core/commit/?id=42b4fa2f923244bc047874752d2e0381ff6f0a25
[3] https://github.com/ros/ros_comm/pull/911
[4] https://github.com/ros/ros_comm/pull/930
[5] https://github.com/ros/ros_comm/pull/939
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
This commit removes the patch that has been accepted upstream
and has been included in the version 1.5.45.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
In 2014, the update of the diagnostics recipes from 1.8.3 to 1.8.4
failed due to reasons that seem not to be relevant anymore in the
current version 1.8.10. As the diagnostic-aggregator recipe failed
with gcc6 (cf. https://github.com/bmwcarit/meta-ros/issues/392),
I revisited the diagnostics recipes and this commit updates them.
The current diagnostics recipes in version 1.8.10 do not fail with
gcc6, and is one step forward to build meta-ros with gcc6.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
The recent versions of the rosbridge_library package does not depend
on python-pytz anymore. So, this commit removes the dependency in
the recipe file and removes the now unneeded python-pytz recipe.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
Bitbake gives a dependency error when IMAGE_FEATURES += " dev-pkgs" is set.
This is because the urdfdom-headers package contains headers only, as a
result bitbake packages them into urdfdom-headers-dev and leaves
urdfdom-headers empty.
Since there are no files to be packaged into urdfdom-headers bitbake
doesn't create the package. urdfdom-headers is a dependency
of urdfdom-headers-dev by default so bitbake errors when building an image
with dev-pkgs enabled.
ALLOW_EMPTY tells bitbake to create a package even when nothing is in it.
This resolves the dependency issue of urdfdom-headers-dev
http://www.embeddedlinux.org.cn/OEManual/recipes_packages.html
While testing the version updates, I noticed that the
camera-calibration-parsers were missing the roscpp dependencies,
and hence do_configure failed with:
```
| Could not find a package configuration file provided by "roscpp" with any
| of the following names:
|
| roscppConfig.cmake
| roscpp-config.cmake
|
| Add the installation prefix of "roscpp" to CMAKE_PREFIX_PATH or set
| "roscpp_DIR" to a directory containing one of the above files. If "roscpp"
| provides a separate development package or SDK, be sure it has been
| installed.
| Call Stack (most recent call first):
| CMakeLists.txt:4 (find_package)
|
|
| -- Configuring incomplete, errors occurred!
```
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
This patch fixes the continuous integration test by dropping
the sound-play recipe from ros-world, as it would fail with
the master branches (addresses issue #388).
https://github.com/bmwcarit/meta-ros/issues/388
In _setup_util.py.in, we use python provided by environment instead of
the generated one, as the generated python path can be arbitrarily long
(depending on the location of the build directory), and hence reaches
the shebang line limit, causing the script to fail at start-up.
The catkin developers changed the cmake-generated template _setup_util.py
to use @PYTHON_EXECUTABLE@ instead of /usr/bin/env python in changeset
bf12b40c2 [1]. We revert this change here to address the issue #384 [2].
[1] bf12b40c2a
[2] https://github.com/bmwcarit/meta-ros/issues/384
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
This commit adds recipes for rosbridge_suite and its dependencies.
Its main content is based on the commits of pull request #364 by
Christoph Schultz.
As maintainer, Lukas Bulwahn just included the contributions
with a proper commit message, added the new packages to the
packagegroup-ros-world, and slightly improved the line breaking.
The internal CI build detected that bitbake robot-state-publisher
fails after the recent version update. Hence, this commit adjusts
the dependencies to those dependencies stated in the package.xml.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
Some of the gst-plugins-good modules were missing to setup a cam for some basic scenarios/tutorials. I added it so they'll be added to the default build set.
The openslam_gmapping commit
07b0c7ef62
corrects the license information of that package, and hence, we
adjust the recipe in meta-ros accordingly.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
This commit drops all patches as they have been merged upstream
since 0.9.1. Furthermore, this commit completes the dependencies
of the velocity_controllers and the forward_command_controller
package.
The ROS packages, rosgraph_msgs and std_srvs, previously
in the ros_comm repository, have been moved into a separate
ros-comm-msgs repository for the ROS indigo distribution.
This commit:
- removes std-srvs and rosgraph-msgs recipes, as their sources
now are located in the ros_comm_msgs repository.
- adds a recipe for the new roslz4 package, which rosbag-storage
depends on.
- removes the patch that has been merged upstream.
The resource_retriever package's source was moved into
its own repository, and needs now python-urlgrabber.
Hence, this commit provides the recipe for python-urlgrabber, moves
the resource-retriever to its own location, and updates all other
packages in the robot_model repository.
KristofRobot