From 5ae3d5a145b4e941220ea423d9262684de0f38fa Mon Sep 17 00:00:00 2001 From: Herb Kuta Date: Fri, 24 May 2019 21:49:13 -0700 Subject: [PATCH] README.md: Add "under construction" notice --- README.md | 72 +++++++++++++++++++++++++++++++++---------------------- 1 file changed, 43 insertions(+), 29 deletions(-) diff --git a/README.md b/README.md index b51f804..d8f68c8 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,19 @@ +# UNDER CONSTRUCTION! + +The original implementation of `meta-ros` for ROS 1 Indigo Igloo +( was transferred here on 2019-06-25. It +is in the process of being upgraded to be able to build current ROS 1 and ROS 2 +distros (Crystal Clemmys, Dashing Diademata, and eventually Melodic Morenia and +Bouncy Bolson) from recipes generated by +[superflore](https://github.com/ros-infrastructure/superflore/) and might not be +usable for a little while. Please see this +[wiki page](https://github.com/ros/meta-ros/wiki/Superflore-OE-Recipe-Generation-Scheme) +for details of what is being done. + +# Contents of Previous README + This is a layer to provide ROS Indigo Igloo in an OpenEmbedded Linux system. -It provides a stable cross-compilation build system for many common ROS packages. +It provides a stable cross-compilation build system for many common ROS packages. Currently, this layer is still under continuous development. ## IMPORTANT RESOURCES ## @@ -64,29 +78,29 @@ resolved in the past. This layer depends on: - **openembedded-core** - URI: git://git.openembedded.org/openembedded-core - subdirectory: meta - branch: master - revision: HEAD + **openembedded-core** + URI: git://git.openembedded.org/openembedded-core + subdirectory: meta + branch: master + revision: HEAD - **meta-openembedded (meta-oe)** - URI: git://git.openembedded.org/meta-openembedded - subdirectory: meta-oe - branch: master - revision: HEAD + **meta-openembedded (meta-oe)** + URI: git://git.openembedded.org/meta-openembedded + subdirectory: meta-oe + branch: master + revision: HEAD - **meta-python** (since a6d7ba92645a112af358efd94ff3aa0c74985a51@meta-openembedded) - URI: git://git.openembedded.org/meta-openembedded - subdirectory: meta-python - branch: master - revision: HEAD - - **meta-multimedia** (since fe44ac167a2a76531af3519f3889fce92024567b@meta-openembedded) - URI: git://git.openembedded.org/meta-openembedded - subdirectory: meta-multimedia - branch: master - revision: HEAD + **meta-python** (since a6d7ba92645a112af358efd94ff3aa0c74985a51@meta-openembedded) + URI: git://git.openembedded.org/meta-openembedded + subdirectory: meta-python + branch: master + revision: HEAD + + **meta-multimedia** (since fe44ac167a2a76531af3519f3889fce92024567b@meta-openembedded) + URI: git://git.openembedded.org/meta-openembedded + subdirectory: meta-multimedia + branch: master + revision: HEAD **meta-intel-realsense** (since 4a5ba0f20094dd3d07c0a0c1dede2ba40e9d6abf) URI: https://github.com/IntelRealSense/meta-intel-realsense @@ -172,7 +186,7 @@ resolved in the past. source oe-init-build-env - Add the required layers (see **DEPENDENCIES**) by modifying ``./conf/bblayers.conf`` (adjust ``/home/me/devel`` as necessary): + Add the required layers (see **DEPENDENCIES**) by modifying ``./conf/bblayers.conf`` (adjust ``/home/me/devel`` as necessary): BBLAYERS ?= " \ /home/me/devel/openembedded-core/meta \ @@ -201,9 +215,9 @@ resolved in the past. Then for example, you start this system in the qemu virtual machine with runqemu core-image-ros-roscore - + On the Linux system, ensure that the own host's name in resolved by adding - + 127.0.0.1 .localdomain to the /etc/hosts file, and set up the environment with @@ -238,16 +252,16 @@ resolved in the past. ## CROSS-COMPILING ALL ROS PACKAGES IN meta-ros - + The meta-ros layers only includes a subset of the officially released ROS packages, available from packages.ros.org. The here provided ROS packages are mainly driven by the current users' needs. - + For ROS packages that depend on cv-bridge, the commercial license flag must be whitelisted, as cv-bridge depends on opencv, and opencv by default depends on libav that has special terms and conditions when used commercially. - This can be done by adding to the local.conf the line: + This can be done by adding to the local.conf the line: LICENSE_FLAGS_WHITELIST = "commercial" @@ -261,7 +275,7 @@ resolved in the past. in tree for individual recipes is under the LICENSE stated in each recipe (.bb file) unless otherwise stated. The descriptions in the recipes of ROS packages have been extracted from - the ROS wiki (http://www.ros.org/wiki/) and are licensed under + the ROS wiki (http://www.ros.org/wiki/) and are licensed under Creative Commons Attribution 3.0 (http://creativecommons.org/licenses/by/3.0/) unless otherwise noted.