p71924506
/
meta-ros
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
meta-ros/recipes-ros/catkin/catkin.inc

32 lines
1.1 KiB
PHP
Raw Normal View History

catkin: split up catkin in order to reduce runtime dependencies The catkin package has got a runtime dependency to cmake, make, gcc and other build utilities. These dependencies, however, are only needed if it is desired to build with catkin on the target board. If we do not want to build on the target board, i.e., if we just want to use ros tools like roslaunch, only a small part of catkin (i.e., the corresponding python packages) is required to be deployed on the target board. Therefore, we introduce a new package called catkin-runtime. It installs only the python packages that are required for the ros tools to run. The roslib package now depends on catkin-runtime (previously: catkin). I also tried an alternative approach which just modifies catkin.bb: - add a catkin-runtime package - move PYTHON_SITEPACKAGES_DIR from FILES_catkin to FILES_CATKIN_RUNTIME - make catkin_runtime RDEPEND on the python stuff - make catkin RDEPEND on the cmake, binutils, ..., + catkin-runtime With this setup, for some reason, bitbake thinks that catkin-runtime still RDEPENDS on binutils. Therefore, I split up the catkin recipe into two different recipes. Here, the RDEPENDS are managed correctly. If we want to deploy catkin as a build tool on the board, we can simply add a runtime dependency to catkin. However, this should not be the default setup. Special thanks go to Tobias Henkel (tobias.henkel@bmw-carit.de) who deserves most of the credits for this patch. Signed-off-by: Andreas Baak <andreas.baak@bmw-carit.de>
2015-03-02 19:59:52 +08:00
DESCRIPTION = "Low-level build system macros and infrastructure for ROS"
SECTION = "devel"
LICENSE = "BSD"
LIC_FILES_CHKSUM = "file://package.xml;beginline=7;endline=7;md5=d566ef916e9dedc494f5f793a6690ba5"
catkin: drop python-catkin-pkg from catkin-runtime's build deps Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
2017-04-07 19:49:58 +08:00
DEPENDS = "cmake python-empy-native python-catkin-pkg-native"
catkin: split up catkin in order to reduce runtime dependencies The catkin package has got a runtime dependency to cmake, make, gcc and other build utilities. These dependencies, however, are only needed if it is desired to build with catkin on the target board. If we do not want to build on the target board, i.e., if we just want to use ros tools like roslaunch, only a small part of catkin (i.e., the corresponding python packages) is required to be deployed on the target board. Therefore, we introduce a new package called catkin-runtime. It installs only the python packages that are required for the ros tools to run. The roslib package now depends on catkin-runtime (previously: catkin). I also tried an alternative approach which just modifies catkin.bb: - add a catkin-runtime package - move PYTHON_SITEPACKAGES_DIR from FILES_catkin to FILES_CATKIN_RUNTIME - make catkin_runtime RDEPEND on the python stuff - make catkin RDEPEND on the cmake, binutils, ..., + catkin-runtime With this setup, for some reason, bitbake thinks that catkin-runtime still RDEPENDS on binutils. Therefore, I split up the catkin recipe into two different recipes. Here, the RDEPENDS are managed correctly. If we want to deploy catkin as a build tool on the board, we can simply add a runtime dependency to catkin. However, this should not be the default setup. Special thanks go to Tobias Henkel (tobias.henkel@bmw-carit.de) who deserves most of the credits for this patch. Signed-off-by: Andreas Baak <andreas.baak@bmw-carit.de>
2015-03-02 19:59:52 +08:00
SRC_URI = "https://github.com/ros/${ROS_SPN}/archive/${PV}.tar.gz;downloadfilename=${ROS_SP}.tar.gz"
catkin: updating to 0.6.19
2017-03-19 22:08:20 +08:00
SRC_URI[md5sum] = "d58460cc9112812d8c4e6ecf98bbcc85"
SRC_URI[sha256sum] = "90a639d67db7f9039487af555e432a5b4b6e339f22892d75d03b823b3f38c947"
catkin: split up catkin in order to reduce runtime dependencies The catkin package has got a runtime dependency to cmake, make, gcc and other build utilities. These dependencies, however, are only needed if it is desired to build with catkin on the target board. If we do not want to build on the target board, i.e., if we just want to use ros tools like roslaunch, only a small part of catkin (i.e., the corresponding python packages) is required to be deployed on the target board. Therefore, we introduce a new package called catkin-runtime. It installs only the python packages that are required for the ros tools to run. The roslib package now depends on catkin-runtime (previously: catkin). I also tried an alternative approach which just modifies catkin.bb: - add a catkin-runtime package - move PYTHON_SITEPACKAGES_DIR from FILES_catkin to FILES_CATKIN_RUNTIME - make catkin_runtime RDEPEND on the python stuff - make catkin RDEPEND on the cmake, binutils, ..., + catkin-runtime With this setup, for some reason, bitbake thinks that catkin-runtime still RDEPENDS on binutils. Therefore, I split up the catkin recipe into two different recipes. Here, the RDEPENDS are managed correctly. If we want to deploy catkin as a build tool on the board, we can simply add a runtime dependency to catkin. However, this should not be the default setup. Special thanks go to Tobias Henkel (tobias.henkel@bmw-carit.de) who deserves most of the credits for this patch. Signed-off-by: Andreas Baak <andreas.baak@bmw-carit.de>
2015-03-02 19:59:52 +08:00
catkin: patch _setup_util.py.in to address #384 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] https://github.com/ros/catkin/commit/bf12b40c2a93b11c3666619a474d35bcfea20837 [2] https://github.com/bmwcarit/meta-ros/issues/384 Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
2016-06-01 17:31:20 +08:00
SRC_URI += "\
file://0001-CATKIN_WORKSPACES-Don-t-require-.catkin-file.patch \
file://0001-use-python-provided-by-environment-instead-of-the-ge.patch \
catkin: avoid leaking host environment to sysroot when searching for libs Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
2017-02-08 17:56:53 +08:00
file://0001-avoid-using-host-s-paths-when-cross-compiling.patch \
catkin: relocate dependency's headers to current sysroot If a package (A) depends on another package (B) and the package B depends on Boost then it might happen that B produces BConfig.cmake file where absolute paths to Boost's headers are put (because CMake's standard FindBoost.cmake module reports absolute paths). In case of Yocto it means that BConfig.cmake will contain something like /path/to/build/tmp-glibc/work/i586/package_B/0.0.1/recipe-sysroot/usr/include. The path may not exist at the moment when the package A is being built. And that leads to the failure of the check this patch switches off. The problem has been reported to catkin's issue tracker: https://github.com/ros/catkin/issues/851 This patch "relocates" required headers from dependencies' sysroots to the current sysroot by removing sysroot prefix from include dirs in *Config.cmake files at the moment the files get created and by prepending the include dirs again with the current sysroot prefix. Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
2017-02-08 18:03:05 +08:00
file://0001-relocate-dependency-s-headers-to-current-sysroot.patch \
catkin: patch _setup_util.py.in to address #384 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] https://github.com/ros/catkin/commit/bf12b40c2a93b11c3666619a474d35bcfea20837 [2] https://github.com/bmwcarit/meta-ros/issues/384 Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
2016-06-01 17:31:20 +08:00
"
catkin: split up catkin in order to reduce runtime dependencies The catkin package has got a runtime dependency to cmake, make, gcc and other build utilities. These dependencies, however, are only needed if it is desired to build with catkin on the target board. If we do not want to build on the target board, i.e., if we just want to use ros tools like roslaunch, only a small part of catkin (i.e., the corresponding python packages) is required to be deployed on the target board. Therefore, we introduce a new package called catkin-runtime. It installs only the python packages that are required for the ros tools to run. The roslib package now depends on catkin-runtime (previously: catkin). I also tried an alternative approach which just modifies catkin.bb: - add a catkin-runtime package - move PYTHON_SITEPACKAGES_DIR from FILES_catkin to FILES_CATKIN_RUNTIME - make catkin_runtime RDEPEND on the python stuff - make catkin RDEPEND on the cmake, binutils, ..., + catkin-runtime With this setup, for some reason, bitbake thinks that catkin-runtime still RDEPENDS on binutils. Therefore, I split up the catkin recipe into two different recipes. Here, the RDEPENDS are managed correctly. If we want to deploy catkin as a build tool on the board, we can simply add a runtime dependency to catkin. However, this should not be the default setup. Special thanks go to Tobias Henkel (tobias.henkel@bmw-carit.de) who deserves most of the credits for this patch. Signed-off-by: Andreas Baak <andreas.baak@bmw-carit.de>
2015-03-02 19:59:52 +08:00
inherit catkin
FILES_${PN}-dev += "\
${ros_datadir}/eigen/cmake \
${ros_datadir}/ros/cmake \
${ros_datadir}/.catkin \
${ros_prefix}/.catkin \
${ros_prefix}/.rosinstall \
${ros_prefix}/_setup_util.py \
${ros_prefix}/env.sh \
${ros_prefix}/setup.* \
"