By default the toolchain file for the SDK is placed in nativesdk-cmake-dev;
however, the installed environment hook (which depends on the toolchain
file) is placed in nativesdk-cmake. Therefore, this patch overwrites
the default filter from cmake.bbclass such that all files are located in
nativesdk-cmake.
* fixes:
WARNING: socketcan-interface-0.6.8-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-find-and-link-the-thread-library-properly.patch
patching file CMakeLists.txt
Hunk #2 succeeded at 45 with fuzz 1.
Now at patch 0001-find-and-link-the-thread-library-properly.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
WARNING: roslaunch-1.11.21-r1 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-increase-rosmaster-timeout.patch
patching file src/roslaunch/launch.py
Hunk #1 succeeded at 59 with fuzz 2 (offset 4 lines).
Now at patch 0001-increase-rosmaster-timeout.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
WARNING: mavros-0.18.7-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-CMake-explicitly-link-the-atomic-library-797.patch
patching file CMakeLists.txt
Hunk #1 succeeded at 90 with fuzz 1 (offset -12 lines).
Now at patch 0001-CMake-explicitly-link-the-atomic-library-797.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
WARNING: kdl-parser-1.11.14-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-add-explicit-dependency-on-libeigen.patch
patching file CMakeLists.txt
Hunk #1 succeeded at 9 with fuzz 1.
Now at patch 0001-add-explicit-dependency-on-libeigen.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
http://errors.yoctoproject.org/Errors/Details/174716/
qhull/2012.1-r0/qhull-2012.1/src/testqset/testqset.c:217:9: error: format not a string literal and no format arguments [-Werror=format-security]
printf(promptstr);
^~~~~~
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
check-version.py polls the official rosdistro file and compares the
version numbers in the meta layer with the official versions.
Usage:
List all versions: ./check-versions.py list (--details)
List all versions that don't match: ./check-versions.py mismatch
(--details)
Update recipe to dist version: ./check-versions.py update <package>
(--downgrade)
Update all recipes to dist version: ./check-versions.py update-all
(--downgrade)
This commit is just a copy of the patch that Dmitry Rozhkov
submitted to openembedded-core, but it was rejected there [1].
If only python3 is installed on an image nothing provides
/usr/bin/python even though many scripts compatible with
both python2 and python3 just state `#!/usr/bin/env python`
in their shebang line.
Make python and python3 recipes provide alternatives for
/usr/bin/python and /usr/bin/python-config. By default
python2 has higher priority over python3.
In meta-ros, we need this behaviour for ROS_USE_PYTHON3 = "yes"
because ROS packages are always written to be python2 and python3
compatible.
[1] https://patchwork.openembedded.org/patch/139143/
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
In commit openembedded/openembedded-core@54ac820b8a, the packaging of
python3 base libraries changed. Amongst others, the packages,
python3-argparse, python3-subprocess and python3-textutils, are merged
into the python3 package.
Hence, this commit adjusts the runtime dependencies in the meta-ros
recipes accordingly.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Commit openembedded/openembedded-core@0391fca ("classes/utils: remove
compatibility functions") forces us to update to the proper oe.utils
functions.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Lukas Bulwahn